[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAPKp9uYFmkiWn9uuPjNLFADP0qrqrpArecuKjNku5X72TyJpzg@mail.gmail.com>
Date: Tue, 29 Nov 2016 17:21:19 +0000
From: Sudeep Holla <sudeep.holla@....com>
To: "Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
Cc: Boris Zhmurov <bb@...nelpanic.ru>,
Michal Hocko <mhocko@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
Johannes Weiner <hannes@...xchg.org>,
Vlastimil Babka <vbabka@...e.cz>,
LKML <linux-kernel@...r.kernel.org>, lkp@...org,
kernel test robot <xiaolong.ye@...el.com>,
Sudeep Holla <sudeep.holla@....com>
Subject: Re: [lkp] [mm] e7c1db75fe: BUG:sleeping_function_called_from_invalid_context_at_mm/page_alloc.c
On Sun, Nov 27, 2016 at 6:16 PM, kernel test robot
<xiaolong.ye@...el.com> wrote:
>
> FYI, we noticed the following commit:
>
> commit e7c1db75fed821a961ce1ca2b602b08e75de0cd8 ("mm: Prevent __alloc_pages_nodemask() RCU CPU stall warnings")
> https://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git rcu/next
>
> in testcase: boot
>
> on test machine: qemu-system-x86_64 -enable-kvm -cpu Nehalem -smp 2 -m 1G
>
> caused below changes:
>
[...]
> [ 8.953192] BUG: sleeping function called from invalid context at mm/page_alloc.c:3746
> [ 8.956353] in_atomic(): 1, irqs_disabled(): 1, pid: 0, name: swapper/0
I am observing similar BUG/backtrace even on ARM64 platform.
--
Regards,
Sudeep
Powered by blists - more mailing lists