From: marc.zyngier@arm.com (Marc Zyngier)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] irqchip, gicv3: Fix out-of-range cpumask access reported by cpumask_check()
Date: Tue, 20 Sep 2016 12:58:13 +0100 [thread overview]
Message-ID: <57E12455.8000507@arm.com> (raw)
In-Reply-To: <20160920113858.GA5140@leverpostej>
On 20/09/16 12:39, Mark Rutland wrote:
> On Tue, Sep 20, 2016 at 01:34:19PM +0200, Robert Richter wrote:
>> Booting a kernel with DEBUG_PER_CPU_MAPS enabled triggers the follwing
>> warning:
>>
>> WARNING: CPU: 1 PID: 0 at ./include/linux/cpumask.h:121 gic_raise_softirq+0x298/0x308
>
> James posted a patch for this [1], which we were hoping Thomas would
> pick up [2].
It is already in tip/irq/urgent (727653d).
Thanks,
M.
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2016-09-20 11:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-20 11:34 [PATCH] irqchip, gicv3: Fix out-of-range cpumask access reported by cpumask_check() Robert Richter
2016-09-20 11:39 ` Mark Rutland
2016-09-20 11:58 ` 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=57E12455.8000507@arm.com \
--to=marc.zyngier@arm.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).