[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180116083739.irw62va5kpc62cvr@gmail.com>
Date: Tue, 16 Jan 2018 09:37:39 +0100
From: Ingo Molnar <mingo@...nel.org>
To: Dave Hansen <dave.hansen@...ux.intel.com>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
the arch/x86 maintainers <x86@...nel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Michal Hocko <mhocko@...nel.org>
Subject: Re: [mm 4.15-rc8] Random oopses under memory pressure.
* Dave Hansen <dave.hansen@...ux.intel.com> wrote:
> Did anyone else notice the
>
> [ 31.068198] ? vmalloc_sync_all+0x150/0x150
>
> present in a bunch of the stack traces? That should be pretty uncommon.
I thikn that's pretty unusual:
> Is it just part of the normal do_page_fault() stack and the stack
> dumper picks up on it?
No, it should only be called by register_die_notifier(), which is not part of the
regular stack dump, AFAICS.
Thanks,
Ingo
Powered by blists - more mailing lists