From: Dmitry Vyukov <dvyukov@google.com>
To: Vegard Nossum <vegard.nossum@oracle.com>
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>,
Alexander Potapenko <glider@google.com>,
kasan-dev <kasan-dev@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>,
Linux MM <linux-mm@kvack.org>
Subject: Re: kernel BUG at mm/mempolicy.c:1699!
Date: Fri, 29 Jul 2016 21:16:29 +0200 [thread overview]
Message-ID: <CACT4Y+aZLFP47uOvxZgXH0PHs=oipa_zO6eipRxnKuw82Y2Kpg@mail.gmail.com> (raw)
In-Reply-To: <579BAA1F.6000704@oracle.com>
On Fri, Jul 29, 2016 at 9:10 PM, Vegard Nossum <vegard.nossum@oracle.com> wrote:
> On 07/29/2016 08:05 PM, Dmitry Vyukov wrote:
>>
>> On Fri, Jul 29, 2016 at 7:57 PM, Vegard Nossum <vegard.nossum@oracle.com>
>> wrote:
>>>
>>> ------------[ cut here ]------------
>>> kernel BUG at mm/mempolicy.c:1699!
>
> [...]
>>>
>>> In particular, it's interesting that the kernel/exit.c line is
>>>
>>> mpol_put(tsk->mempolicy);
>>>
>>> and alloc_pages_current() does (potentially):
>>>
>>> pol = get_task_policy(current);.
>>>
>>> The bug seems very new or very rare or both.
>>
>>
>> This is https://github.com/google/kasan/issues/35
>> It is introduced with stackdepot.
>
>
> Ah, cool.
>
> Would it be enough to set __GFP_THISNODE in depot_save_stack() so it
> uses &default_policy instead of current->mempolicy?
I don't have deep understanding of that code. But looks at the code,
using &default_policy should help.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-07-29 19:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-29 17:57 Vegard Nossum
2016-07-29 18:05 ` Dmitry Vyukov
2016-07-29 19:10 ` Vegard Nossum
2016-07-29 19:16 ` Dmitry Vyukov [this message]
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+aZLFP47uOvxZgXH0PHs=oipa_zO6eipRxnKuw82Y2Kpg@mail.gmail.com' \
--to=dvyukov@google.com \
--cc=aryabinin@virtuozzo.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vegard.nossum@oracle.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox