From: Dmitry Vyukov <dvyukov@google.com>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Andrey Ryabinin <aryabinin@virtuozzo.com>,
Pavel Tatashin <pasha.tatashin@oracle.com>,
Petr Mladek <pmladek@suse.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Nicolas Pitre <nicolas.pitre@linaro.org>,
Nikitas Angelinas <nikitas.angelinas@gmail.com>,
Matt Redfearn <matt.redfearn@mips.com>,
LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>,
Steven Sistare <steven.sistare@oracle.com>,
Daniel Jordan <daniel.m.jordan@oracle.com>,
Bob Picco <bob.picco@oracle.com>,
Linux Memory Management List <linux-mm@kvack.org>,
kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: [console_unlock] BUG: KASAN: use-after-scope in console_unlock+0x9cd/0xd10
Date: Thu, 19 Apr 2018 11:50:20 +0200 [thread overview]
Message-ID: <CACT4Y+ZL_xY-HJwgU+XQ-onqe+coxbNGOBno6HrPHwYuPdHRFA@mail.gmail.com> (raw)
In-Reply-To: <20180419065531.l6kblbziddplgcwi@wfg-t540p.sh.intel.com>
On Thu, Apr 19, 2018 at 8:55 AM, Fengguang Wu <fengguang.wu@intel.com> 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 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.org/r/CAKv+Gu8HN-t2om8sCfjxCWbsgSir54fZw222dsed0Xwqph2aNg@mail.gmail.com
>> [2]
>> lkml.kernel.org/r/CAGXu5j+mcfo4aB3PM1We6O62bFBJcMFX-9obJE4jFU1Dp=gNwg@mail.gmail.com
>
>
> That'd be great, thank you very much!
Just mailed "KASAN: prohibit KASAN+STRUCTLEAK combination":
https://groups.google.com/d/msg/kasan-dev/Y1TEh7ZlHTQ/wR36C8uMCgAJ
WARNING: multiple messages have this Message-ID (diff)
From: Dmitry Vyukov <dvyukov@google.com>
To: lkp@lists.01.org
Subject: Re: [console_unlock] BUG: KASAN: use-after-scope in console_unlock+0x9cd/0xd10
Date: Thu, 19 Apr 2018 11:50:20 +0200 [thread overview]
Message-ID: <CACT4Y+ZL_xY-HJwgU+XQ-onqe+coxbNGOBno6HrPHwYuPdHRFA@mail.gmail.com> (raw)
In-Reply-To: <20180419065531.l6kblbziddplgcwi@wfg-t540p.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 852 bytes --]
On Thu, Apr 19, 2018 at 8:55 AM, Fengguang Wu <fengguang.wu@intel.com> 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 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.org/r/CAKv+Gu8HN-t2om8sCfjxCWbsgSir54fZw222dsed0Xwqph2aNg(a)mail.gmail.com
>> [2]
>> lkml.kernel.org/r/CAGXu5j+mcfo4aB3PM1We6O62bFBJcMFX-9obJE4jFU1Dp=gNwg(a)mail.gmail.com
>
>
> That'd be great, thank you very much!
Just mailed "KASAN: prohibit KASAN+STRUCTLEAK combination":
https://groups.google.com/d/msg/kasan-dev/Y1TEh7ZlHTQ/wR36C8uMCgAJ
next prev parent reply other threads:[~2018-04-19 9:50 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 2:17 [console_unlock] BUG: KASAN: use-after-scope in console_unlock+0x9cd/0xd10 Fengguang Wu
2018-04-19 2:17 ` Fengguang Wu
2018-04-19 2:21 ` a4a3ede213 ("mm: zero reserved and unavailable struct pages"): [ 0.010000] BUG: KASAN: use-after-scope in console_unlock Fengguang Wu
2018-04-19 2:21 ` Fengguang Wu
2018-04-19 2:26 ` d17a1d97dc ("x86/mm/kasan: don't use vmemmap_populate() to initialize shadow"): [ 0.001000] " Fengguang Wu
2018-04-19 2:26 ` Fengguang Wu
2018-04-19 6:04 ` [console_unlock] BUG: KASAN: use-after-scope in console_unlock+0x9cd/0xd10 Dmitry Vyukov
2018-04-19 6:04 ` Dmitry Vyukov
2018-04-19 6:20 ` Sergey Senozhatsky
2018-04-19 6:20 ` Sergey Senozhatsky
2018-04-19 6:55 ` Fengguang Wu
2018-04-19 6:55 ` Fengguang Wu
2018-04-19 9:50 ` Dmitry Vyukov [this message]
2018-04-19 9:50 ` Dmitry Vyukov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CACT4Y+ZL_xY-HJwgU+XQ-onqe+coxbNGOBno6HrPHwYuPdHRFA@mail.gmail.com \
--to=dvyukov@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=bob.picco@oracle.com \
--cc=daniel.m.jordan@oracle.com \
--cc=fengguang.wu@intel.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@01.org \
--cc=matt.redfearn@mips.com \
--cc=nicolas.pitre@linaro.org \
--cc=nikitas.angelinas@gmail.com \
--cc=pasha.tatashin@oracle.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=steven.sistare@oracle.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.