From: Michal Hocko <mhocko@kernel.org>
To: Dmitry Vyukov <dvyukov@google.com>
Cc: Andrey Ryabinin <aryabinin@virtuozzo.com>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
kasan-dev <kasan-dev@googlegroups.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: strange allocation failures
Date: Mon, 13 Mar 2017 11:59:03 +0100 [thread overview]
Message-ID: <20170313105903.GM31518@dhcp22.suse.cz> (raw)
In-Reply-To: <CACT4Y+Z0wwf3=mxUuZqn3M9qPBVhM6nRWi3hveeV2JPoubLAwA@mail.gmail.com>
On Mon 13-03-17 11:45:01, Dmitry Vyukov wrote:
> On Mon, Mar 13, 2017 at 11:37 AM, Dmitry Vyukov <dvyukov@google.com> wrote:
[...]
> > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> > index 6cbde310abed..418c80a76b4a 100644
> > --- a/mm/page_alloc.c
> > +++ b/mm/page_alloc.c
> > @@ -3073,6 +3073,11 @@ static inline bool should_suppress_show_mem(void)
> > #if NODES_SHIFT > 8
> > ret = in_interrupt();
>
> /\/\/\/\/\/\/\/\
> As a side note, looking at this line.
> Can vmalloc be called from an interrupt? If so, won't we fail all
> vmalloc's in an unlucky interrupt that hit a task with
> fatal_signal_pending?
__get_vm_area_node has a BUG_ON so I do not think this is allowed.
--
Michal Hocko
SUSE Labs
--
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>
next prev parent reply other threads:[~2017-03-13 10:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CACT4Y+ZVWUYda9zr74QOmcXzd0S7P714LhzrVu7wRO0oDM0P2w@mail.gmail.com>
[not found] ` <d849e961-7120-2ba5-1d58-df81d0ae3293@virtuozzo.com>
[not found] ` <CACT4Y+Y=Pz6wFN66BGdPkTPJWrnbxCL2GX-R0q5_jr5kwjF+zA@mail.gmail.com>
[not found] ` <CACT4Y+bD0S9CY0ahvZ=pOpXqHAkH6P0OTHPTeBi-Pb2Nw6ph4w@mail.gmail.com>
2017-03-13 10:31 ` Andrey Ryabinin
2017-03-13 10:37 ` Dmitry Vyukov
2017-03-13 10:45 ` Dmitry Vyukov
2017-03-13 10:59 ` Michal Hocko [this message]
2017-03-13 10:51 ` Michal Hocko
2017-03-13 10:37 ` Michal Hocko
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=20170313105903.GM31518@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=aryabinin@virtuozzo.com \
--cc=dvyukov@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox