Re: [PATCH v2] kasan: report only the first error by default

2017-03-23 Thread Mark Rutland
On Thu, Mar 23, 2017 at 04:06:59PM +0300, Andrey Ryabinin wrote: > On 03/23/2017 03:41 PM, Mark Rutland wrote: > > Rather than trying to pick an arbitrarily large number, how about we use > > separate flags to determine whether we're in multi-shot mode, and > > whether a (oneshot) report has been

Re: [PATCH v2] kasan: report only the first error by default

2017-03-23 Thread Mark Rutland
On Thu, Mar 23, 2017 at 04:06:59PM +0300, Andrey Ryabinin wrote: > On 03/23/2017 03:41 PM, Mark Rutland wrote: > > Rather than trying to pick an arbitrarily large number, how about we use > > separate flags to determine whether we're in multi-shot mode, and > > whether a (oneshot) report has been

Re: [PATCH v2] kasan: report only the first error by default

2017-03-23 Thread Andrey Ryabinin
On 03/23/2017 03:41 PM, Mark Rutland wrote: > On Thu, Mar 23, 2017 at 02:49:16PM +0300, Andrey Ryabinin wrote: >> +kasan_multi_shot >> +[KNL] Enforce KASAN (Kernel Address Sanitizer) to print >> +report on every invalid memory access. Without this >> +

Re: [PATCH v2] kasan: report only the first error by default

2017-03-23 Thread Andrey Ryabinin
On 03/23/2017 03:41 PM, Mark Rutland wrote: > On Thu, Mar 23, 2017 at 02:49:16PM +0300, Andrey Ryabinin wrote: >> +kasan_multi_shot >> +[KNL] Enforce KASAN (Kernel Address Sanitizer) to print >> +report on every invalid memory access. Without this >> +

Re: [PATCH v2] kasan: report only the first error by default

2017-03-23 Thread Mark Rutland
On Thu, Mar 23, 2017 at 02:49:16PM +0300, Andrey Ryabinin wrote: > + kasan_multi_shot > + [KNL] Enforce KASAN (Kernel Address Sanitizer) to print > + report on every invalid memory access. Without this > + parameter KASAN will print

Re: [PATCH v2] kasan: report only the first error by default

2017-03-23 Thread Mark Rutland
On Thu, Mar 23, 2017 at 02:49:16PM +0300, Andrey Ryabinin wrote: > + kasan_multi_shot > + [KNL] Enforce KASAN (Kernel Address Sanitizer) to print > + report on every invalid memory access. Without this > + parameter KASAN will print

[PATCH v2] kasan: report only the first error by default

2017-03-23 Thread Andrey Ryabinin
Disable kasan after the first report. There are several reasons for this: * Single bug quite often has multiple invalid memory accesses causing storm in the dmesg. * Write OOB access might corrupt metadata so the next report will print bogus alloc/free stacktraces. * Reports after the

[PATCH v2] kasan: report only the first error by default

2017-03-23 Thread Andrey Ryabinin
Disable kasan after the first report. There are several reasons for this: * Single bug quite often has multiple invalid memory accesses causing storm in the dmesg. * Write OOB access might corrupt metadata so the next report will print bogus alloc/free stacktraces. * Reports after the