[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <159583764131.244522.1925786531384349855.b4-ty@kernel.org>
Date: Mon, 27 Jul 2020 09:14:49 +0100
From: Marc Zyngier <maz@...nel.org>
To: tglx@...utronix.de, Joakim Zhang <qiangqing.zhang@....com>,
shawnguo@...nel.org, s.hauer@...gutronix.de, jason@...edaemon.net,
linux-kernel@...r.kernel.org, Zenghui Yu <yuzenghui@...wei.com>
Cc: kernel@...gutronix.de, linux-imx@....com, festevam@...il.com,
wangjingyi11@...wei.com, wanghaibin.wang@...wei.com,
kuhn.chenqun@...wei.com
Subject: Re: [PATCH] irqchip/gic-v4.1: Use GFP_ATOMIC flag in allocate_vpe_l1_table()
On Tue, 30 Jun 2020 21:37:46 +0800, Zenghui Yu wrote:
> Booting the latest kernel with DEBUG_ATOMIC_SLEEP=y on a GICv4.1 enabled
> box, I get the following kernel splat:
>
> [ 0.053766] BUG: sleeping function called from invalid context at mm/slab.h:567
> [ 0.053767] in_atomic(): 1, irqs_disabled(): 128, non_block: 0, pid: 0, name: swapper/1
> [ 0.053769] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.8.0-rc3+ #23
> [ 0.053770] Call trace:
> [ 0.053774] dump_backtrace+0x0/0x218
> [ 0.053775] show_stack+0x2c/0x38
> [ 0.053777] dump_stack+0xc4/0x10c
> [ 0.053779] ___might_sleep+0xfc/0x140
> [ 0.053780] __might_sleep+0x58/0x90
> [ 0.053782] slab_pre_alloc_hook+0x7c/0x90
> [ 0.053783] kmem_cache_alloc_trace+0x60/0x2f0
> [ 0.053785] its_cpu_init+0x6f4/0xe40
> [ 0.053786] gic_starting_cpu+0x24/0x38
> [ 0.053788] cpuhp_invoke_callback+0xa0/0x710
> [ 0.053789] notify_cpu_starting+0xcc/0xd8
> [ 0.053790] secondary_start_kernel+0x148/0x200
>
> [...]
Applied to irq/irqchip-next, thanks!
[1/1] irqchip/gic-v4.1: Use GFP_ATOMIC flag in allocate_vpe_l1_table()
commit: d1bd7e0ba533a2a6f313579ec9b504f6614c35c4
Cheers,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists