From: Marc Zyngier <maz@kernel.org>
To: tglx@linutronix.de, Joakim Zhang <qiangqing.zhang@nxp.com>,
shawnguo@kernel.org, s.hauer@pengutronix.de,
jason@lakedaemon.net, linux-kernel@vger.kernel.org,
Zenghui Yu <yuzenghui@huawei.com>
Cc: kernel@pengutronix.de, linux-imx@nxp.com, festevam@gmail.com,
wangjingyi11@huawei.com, wanghaibin.wang@huawei.com,
kuhn.chenqun@huawei.com
Subject: Re: [PATCH] irqchip/gic-v4.1: Use GFP_ATOMIC flag in allocate_vpe_l1_table()
Date: Mon, 27 Jul 2020 09:14:49 +0100 [thread overview]
Message-ID: <159583764131.244522.1925786531384349855.b4-ty@kernel.org> (raw)
In-Reply-To: <20200630133746.816-1-yuzenghui@huawei.com>
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.
prev parent reply other threads:[~2020-07-27 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 13:37 Zenghui Yu
2020-07-27 3:50 ` Zenghui Yu
2020-07-27 7:57 ` Marc Zyngier
2020-07-27 8:14 ` Marc Zyngier [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=159583764131.244522.1925786531384349855.b4-ty@kernel.org \
--to=maz@kernel.org \
--cc=festevam@gmail.com \
--cc=jason@lakedaemon.net \
--cc=kernel@pengutronix.de \
--cc=kuhn.chenqun@huawei.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qiangqing.zhang@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tglx@linutronix.de \
--cc=wanghaibin.wang@huawei.com \
--cc=wangjingyi11@huawei.com \
--cc=yuzenghui@huawei.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
all inboxes | Powered by JetHome®