From: tip-bot for Thomas Gleixner <tipbot@zytor.com>
To: linux-tip-commits@vger.kernel.org
Cc: bp@suse.de, linux-kernel@vger.kernel.org,
yanmin_zhang@linux.intel.com, peterz@infradead.org,
mingo@kernel.org, jroedel@suse.de, jin.xiao@intel.com,
tglx@linutronix.de, hpa@zytor.com
Subject: [tip:x86/urgent] x86/irq: Retrieve irq data after locking irq_desc
Date: Tue, 7 Jul 2015 02:58:14 -0700 [thread overview]
Message-ID: <tip-09cf92b784fae6109450c5d64f9908066d605249@git.kernel.org> (raw)
In-Reply-To: <20150705171102.331320612@linutronix.de>
Commit-ID: 09cf92b784fae6109450c5d64f9908066d605249
Gitweb: http://git.kernel.org/tip/09cf92b784fae6109450c5d64f9908066d605249
Author: Thomas Gleixner <tglx@linutronix.de>
AuthorDate: Sun, 5 Jul 2015 17:12:35 +0000
Committer: Thomas Gleixner <tglx@linutronix.de>
CommitDate: Tue, 7 Jul 2015 11:54:04 +0200
x86/irq: Retrieve irq data after locking irq_desc
irq_data is protected by irq_desc->lock, so retrieving the irq chip
from irq_data outside the lock is racy vs. an concurrent update. Move
it into the lock held region.
While at it add a comment why the vector walk does not require
vector_lock.
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: xiao jin <jin.xiao@intel.com>
Cc: Joerg Roedel <jroedel@suse.de>
Cc: Borislav Petkov <bp@suse.de>
Cc: Yanmin Zhang <yanmin_zhang@linux.intel.com>
Link: http://lkml.kernel.org/r/20150705171102.331320612@linutronix.de
---
arch/x86/kernel/irq.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/arch/x86/kernel/irq.c b/arch/x86/kernel/irq.c
index 85ca76e..c7dfe1b 100644
--- a/arch/x86/kernel/irq.c
+++ b/arch/x86/kernel/irq.c
@@ -497,6 +497,11 @@ void fixup_irqs(void)
*/
mdelay(1);
+ /*
+ * We can walk the vector array of this cpu without holding
+ * vector_lock because the cpu is already marked !online, so
+ * nothing else will touch it.
+ */
for (vector = FIRST_EXTERNAL_VECTOR; vector < NR_VECTORS; vector++) {
unsigned int irr;
@@ -508,9 +513,9 @@ void fixup_irqs(void)
irq = __this_cpu_read(vector_irq[vector]);
desc = irq_to_desc(irq);
+ raw_spin_lock(&desc->lock);
data = irq_desc_get_irq_data(desc);
chip = irq_data_get_irq_chip(data);
- raw_spin_lock(&desc->lock);
if (chip->irq_retrigger) {
chip->irq_retrigger(data);
__this_cpu_write(vector_irq[vector], VECTOR_RETRIGGERED);
prev parent reply other threads:[~2015-07-07 9:58 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-05 17:12 [patch 0/4] x86/irq: Plug a couple of cpu hotplug races Thomas Gleixner
2015-07-05 17:12 ` [patch 1/4] hotplug: Prevent alloc/free of irq descriptors during cpu up/down Thomas Gleixner
2015-07-07 9:48 ` [tip:irq/urgent] hotplug: Prevent alloc/ free " tip-bot for Thomas Gleixner
2015-07-07 20:06 ` tip-bot for Thomas Gleixner
2015-07-08 9:37 ` tip-bot for Thomas Gleixner
2015-07-14 14:39 ` [patch 1/4] hotplug: Prevent alloc/free " Boris Ostrovsky
2015-07-14 14:39 ` Boris Ostrovsky
2015-07-14 15:44 ` Thomas Gleixner
2015-07-14 15:44 ` Thomas Gleixner
2015-07-14 16:03 ` Boris Ostrovsky
2015-07-14 16:03 ` Boris Ostrovsky
2015-07-14 17:32 ` Thomas Gleixner
2015-07-14 20:04 ` Boris Ostrovsky
2015-07-14 20:04 ` [Xen-devel] " Boris Ostrovsky
2015-07-14 20:15 ` Thomas Gleixner
2015-07-14 20:15 ` [Xen-devel] " Thomas Gleixner
2015-07-14 21:07 ` Boris Ostrovsky
2016-03-12 9:19 ` Thomas Gleixner
2016-03-12 9:19 ` [Xen-devel] " Thomas Gleixner
2016-03-14 13:12 ` Boris Ostrovsky
2016-03-14 13:12 ` Boris Ostrovsky
2015-07-14 21:07 ` Boris Ostrovsky
2015-07-14 17:32 ` Thomas Gleixner
2015-07-05 17:12 ` [patch 2/4] x86: Plug irq vector hotplug race Thomas Gleixner
2015-07-07 9:57 ` [tip:x86/urgent] x86/irq: " tip-bot for Thomas Gleixner
2015-07-05 17:12 ` [patch 3/4] x86/irq: Use proper locking in check_irq_vectors_for_cpu_disable() Thomas Gleixner
2015-07-07 9:57 ` [tip:x86/urgent] " tip-bot for Thomas Gleixner
2015-07-05 17:12 ` [patch 4/4] x86/irq: Retrieve irq data after locking irq_desc Thomas Gleixner
2015-07-07 9:58 ` tip-bot for Thomas Gleixner [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=tip-09cf92b784fae6109450c5d64f9908066d605249@git.kernel.org \
--to=tipbot@zytor.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jin.xiao@intel.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=yanmin_zhang@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.