From: Thomas Gleixner <tglx@linutronix.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Peter Anvin <hpa@zytor.com>, xiao jin <jin.xiao@intel.com>,
Joerg Roedel <jroedel@suse.de>, Borislav Petkov <bp@suse.de>,
Yanmin Zhang <yanmin_zhang@linux.intel.com>
Subject: [patch 0/4] x86/irq: Plug a couple of cpu hotplug races
Date: Sun, 05 Jul 2015 17:12:28 -0000 [thread overview]
Message-ID: <20150705170530.849428850@linutronix.de> (raw)
Jin debugged a subtle race in the cpu hotplug code which caused my to
look deeper into this. So I unearthed quite a few racy constructs.
Aside of the x86 specific problems I discovered a generic issue which
needs to be addressed in the cpu hotplug code.
Thanks,
tglx
next reply other threads:[~2015-07-05 17:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-05 17:12 Thomas Gleixner [this message]
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 15:44 ` Thomas Gleixner
2015-07-14 16:03 ` Boris Ostrovsky
2015-07-14 17:32 ` Thomas Gleixner
2015-07-14 20:04 ` [Xen-devel] " Boris Ostrovsky
2015-07-14 20:15 ` Thomas Gleixner
2015-07-14 21:07 ` Boris Ostrovsky
2016-03-12 9:19 ` Thomas Gleixner
2016-03-14 13:12 ` Boris Ostrovsky
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:x86/urgent] " tip-bot for Thomas Gleixner
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=20150705170530.849428850@linutronix.de \
--to=tglx@linutronix.de \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jin.xiao@intel.com \
--cc=jroedel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox