Re: [console_unlock] BUG: KASAN: use-after-scope in console_unlock+0x9cd/0xd10

2018-04-19 Thread Dmitry Vyukov
On Thu, Apr 19, 2018 at 8:55 AM, Fengguang Wu wrote: > On Thu, Apr 19, 2018 at 03:20:50PM +0900, Sergey Senozhatsky wrote: >> >> On (04/19/18 08:04), Dmitry Vyukov wrote: >> [..] >>> >>> We could also make them mutually exclusive in config to prevent people >>> from hitting these false positives a

Re: [console_unlock] BUG: KASAN: use-after-scope in console_unlock+0x9cd/0xd10

2018-04-18 Thread Fengguang Wu
On Thu, Apr 19, 2018 at 03:20:50PM +0900, Sergey Senozhatsky wrote: On (04/19/18 08:04), Dmitry Vyukov wrote: [..] We could also make them mutually exclusive in config to prevent people from hitting these false positives again and again. Let's do it. Ard and Kees agreed on making them mutually

Re: [console_unlock] BUG: KASAN: use-after-scope in console_unlock+0x9cd/0xd10

2018-04-18 Thread Sergey Senozhatsky
On (04/19/18 08:04), Dmitry Vyukov wrote: [..] > We could also make them mutually exclusive in config to prevent people > from hitting these false positives again and again. Let's do it. Ard and Kees agreed on making them mutually exclusive [1][2]. Dmitry, could send out a patch? [1] lkml.kernel

Re: [console_unlock] BUG: KASAN: use-after-scope in console_unlock+0x9cd/0xd10

2018-04-18 Thread Dmitry Vyukov
On Thu, Apr 19, 2018 at 4:17 AM, Fengguang Wu wrote: > Hello, > > FYI this happens in mainline kernel 4.17.0-rc1. > It at least dates back to v4.15-rc1 . > > The regression was reported before > > https://lkml.org/lkml/2017/11/30/33 > > Where the last message from Dmitry mentions that use