From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Thomas Gleixner <tglx@linutronix.de>,
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>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [patch 1/4] hotplug: Prevent alloc/free of irq descriptors during cpu up/down
Date: Tue, 14 Jul 2015 10:39:12 -0400 [thread overview]
Message-ID: <55A51F10.7010407@oracle.com> (raw)
In-Reply-To: <20150705171102.063519515@linutronix.de>
On 07/05/2015 01:12 PM, Thomas Gleixner wrote:
> When a cpu goes up some architectures (e.g. x86) have to walk the irq
> space to set up the vector space for the cpu. While this needs extra
> protection at the architecture level we can avoid a few race
> conditions by preventing the concurrent allocation/free of irq
> descriptors and the associated data.
>
> When a cpu goes down it moves the interrupts which are targeted to
> this cpu away by reassigning the affinities. While this happens
> interrupts can be allocated and freed, which opens a can of race
> conditions in the code which reassignes the affinities because
> interrupt descriptors might be freed underneath.
>
> Example:
>
> CPU1 CPU2
> cpu_up/down
> irq_desc = irq_to_desc(irq);
> remove_from_radix_tree(desc);
> raw_spin_lock(&desc->lock);
> free(desc);
>
> We could protect the irq descriptors with RCU, but that would require
> a full tree change of all accesses to interrupt descriptors. But
> fortunately these kind of race conditions are rather limited to a few
> things like cpu hotplug. The normal setup/teardown is very well
> serialized. So the simpler and obvious solution is:
>
> Prevent allocation and freeing of interrupt descriptors accross cpu
> hotplug.
This breaks Xen guests that allocate interrupt descriptors in .cpu_up().
Any chance this locking can be moved into arch code? Otherwise we will
need to have something like arch_post_cpu_up() after the lock is released.
(The patch doesn't appear to have any side effects for the down path
since Xen guests deallocate descriptors in __cpu_die()).
-boris
>
> Signed-off-by: Thomas Gleixner<tglx@linutronix.de>
> ---
> include/linux/irqdesc.h | 7 ++++++-
> kernel/cpu.c | 21 ++++++++++++++++++++-
> kernel/irq/internals.h | 4 ----
> 3 files changed, 26 insertions(+), 6 deletions(-)
>
> Index: tip/include/linux/irqdesc.h
> ===================================================================
> --- tip.orig/include/linux/irqdesc.h
> +++ tip/include/linux/irqdesc.h
> @@ -90,7 +90,12 @@ struct irq_desc {
> const char *name;
> } ____cacheline_internodealigned_in_smp;
>
> -#ifndef CONFIG_SPARSE_IRQ
> +#ifdef CONFIG_SPARSE_IRQ
> +extern void irq_lock_sparse(void);
> +extern void irq_unlock_sparse(void);
> +#else
> +static inline void irq_lock_sparse(void) { }
> +static inline void irq_unlock_sparse(void) { }
> extern struct irq_desc irq_desc[NR_IRQS];
> #endif
>
> Index: tip/kernel/cpu.c
> ===================================================================
> --- tip.orig/kernel/cpu.c
> +++ tip/kernel/cpu.c
> @@ -392,13 +392,19 @@ static int __ref _cpu_down(unsigned int
> smpboot_park_threads(cpu);
>
> /*
> - * So now all preempt/rcu users must observe !cpu_active().
> + * Prevent irq alloc/free while the dying cpu reorganizes the
> + * interrupt affinities.
> */
> + irq_lock_sparse();
>
> + /*
> + * So now all preempt/rcu users must observe !cpu_active().
> + */
> err = __stop_machine(take_cpu_down, &tcd_param, cpumask_of(cpu));
> if (err) {
> /* CPU didn't die: tell everyone. Can't complain. */
> cpu_notify_nofail(CPU_DOWN_FAILED | mod, hcpu);
> + irq_unlock_sparse();
> goto out_release;
> }
> BUG_ON(cpu_online(cpu));
> @@ -415,6 +421,9 @@ static int __ref _cpu_down(unsigned int
> smp_mb(); /* Read from cpu_dead_idle before __cpu_die(). */
> per_cpu(cpu_dead_idle, cpu) = false;
>
> + /* Interrupts are moved away from the dying cpu, reenable alloc/free */
> + irq_unlock_sparse();
> +
> hotplug_cpu__broadcast_tick_pull(cpu);
> /* This actually kills the CPU. */
> __cpu_die(cpu);
> @@ -517,8 +526,18 @@ static int _cpu_up(unsigned int cpu, int
> goto out_notify;
> }
>
> + /*
> + * Some architectures have to walk the irq descriptors to
> + * setup the vector space for the cpu which comes online.
> + * Prevent irq alloc/free across the bringup.
> + */
> + irq_lock_sparse();
> +
> /* Arch-specific enabling code. */
> ret = __cpu_up(cpu, idle);
> +
> + irq_unlock_sparse();
> +
> if (ret != 0)
> goto out_notify;
> BUG_ON(!cpu_online(cpu));
> Index: tip/kernel/irq/internals.h
> ===================================================================
> --- tip.orig/kernel/irq/internals.h
> +++ tip/kernel/irq/internals.h
> @@ -76,12 +76,8 @@ extern void unmask_threaded_irq(struct i
>
> #ifdef CONFIG_SPARSE_IRQ
> static inline void irq_mark_irq(unsigned int irq) { }
> -extern void irq_lock_sparse(void);
> -extern void irq_unlock_sparse(void);
> #else
> extern void irq_mark_irq(unsigned int irq);
> -static inline void irq_lock_sparse(void) { }
> -static inline void irq_unlock_sparse(void) { }
> #endif
>
> extern void init_kstat_irqs(struct irq_desc *desc, int node, int nr);
>
>
> --
next prev parent reply other threads:[~2015-07-14 14:40 UTC|newest]
Thread overview: 20+ 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 ` Boris Ostrovsky [this message]
2015-07-14 15:44 ` [patch 1/4] hotplug: Prevent alloc/free " 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=55A51F10.7010407@oracle.com \
--to=boris.ostrovsky@oracle.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=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=xen-devel@lists.xenproject.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;
as well as URLs for NNTP newsgroup(s).