LKML Archive on lore.kernel.org
 help / Atom feed
From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Borislav Petkov <bp@alien8.de>,
	Dmitry Safonov <0x7f454c46@gmail.com>,
	Tariq Toukan <tariqt@mellanox.com>,
	Song Liu <liu.song.a23@gmail.com>, Joerg Roedel <jroedel@suse.de>,
	Mike Travis <mike.travis@hpe.com>, <stable@vger.kernel.org>
Subject: Re: [patch 2/8] genirq/generic_pending: Do not lose pending affinity update
Date: Tue, 5 Jun 2018 19:20:35 +0800
Message-ID: <74a8cfe1-56e4-6082-1d53-a76faf5105eb@cn.fujitsu.com> (raw)
In-Reply-To: <20180604162224.386544292@linutronix.de>

Hi Thomas,

At 06/04/2018 11:33 PM, Thomas Gleixner wrote:
> The generic pending interrupt mechanism moves interrupts from the interrupt
> handler on the original target CPU to the new destination CPU. This is
> required for x86 and ia64 due to the way the interrupt delivery and
> acknowledge works if the interrupts are not remapped.
> 
> However that update can fail for various reasons. Some of them are valid
> reasons to discard the pending update, but the case, when the previous move
> has not been fully cleaned up is not a legit reason to fail.
> 
> Check the return value of irq_do_set_affinity() for -EBUSY, which indicates
> a pending cleanup, and rearm the pending move in the irq dexcriptor so it's

s/dexcriptor/descriptor

> tried again when the next interrupt arrives.
> 
> Fixes: 996c591227d9 ("x86/irq: Plug vector cleanup race")
> Signed-off-by: Thomas Gleixner<tglx@linutronix.de>
> Cc:stable@vger.kernel.org
> ---
>   kernel/irq/migration.c |   24 ++++++++++++++++++------
>   1 file changed, 18 insertions(+), 6 deletions(-)
> 
> --- a/kernel/irq/migration.c
> +++ b/kernel/irq/migration.c
> @@ -38,17 +38,18 @@ bool irq_fixup_move_pending(struct irq_d
>   void irq_move_masked_irq(struct irq_data *idata)
>   {
>   	struct irq_desc *desc = irq_data_to_desc(idata);
> -	struct irq_chip *chip = desc->irq_data.chip;
> +	struct irq_data *data = &desc->irq_data;
> +	struct irq_chip *chip = data->chip;
>   
> -	if (likely(!irqd_is_setaffinity_pending(&desc->irq_data)))
> +	if (likely(!irqd_is_setaffinity_pending(data)))
>   		return;
>   
> -	irqd_clr_move_pending(&desc->irq_data);
> +	irqd_clr_move_pending(data);
>   
>   	/*
>   	 * Paranoia: cpu-local interrupts shouldn't be calling in here anyway.
>   	 */
> -	if (irqd_is_per_cpu(&desc->irq_data)) {
> +	if (irqd_is_per_cpu(data)) {
>   		WARN_ON(1);
>   		return;
>   	}
> @@ -73,9 +74,20 @@ void irq_move_masked_irq(struct irq_data
>   	 * For correct operation this depends on the caller
>   	 * masking the irqs.
>   	 */
> -	if (cpumask_any_and(desc->pending_mask, cpu_online_mask) < nr_cpu_ids)
> -		irq_do_set_affinity(&desc->irq_data, desc->pending_mask, false);
> +	if (cpumask_any_and(desc->pending_mask, cpu_online_mask) < nr_cpu_ids) {
> +		int ret;
>   
> +		ret = irq_do_set_affinity(data, desc->pending_mask, false);
> +		/*
> +		 * If the there is a cleanup pending in the underlying

s/If the there is/If there is/

Thanks,
	dou

  parent reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-04 15:33 Thomas Gleixner
2018-06-05  7:07 ` Song Liu
2018-06-05 11:20 ` Dou Liyang [this message]
2018-06-06 13:31 ` [tip:x86/urgent] " tip-bot for Thomas Gleixner

Reply instructions:

You may reply publically 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=74a8cfe1-56e4-6082-1d53-a76faf5105eb@cn.fujitsu.com \
    --to=douly.fnst@cn.fujitsu.com \
    --cc=0x7f454c46@gmail.com \
    --cc=bp@alien8.de \
    --cc=jroedel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liu.song.a23@gmail.com \
    --cc=mike.travis@hpe.com \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=stable@vger.kernel.org \
    --cc=tariqt@mellanox.com \
    --cc=tglx@linutronix.de \
    /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

LKML Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/lkml/0 lkml/git/0.git
	git clone --mirror https://lore.kernel.org/lkml/1 lkml/git/1.git
	git clone --mirror https://lore.kernel.org/lkml/2 lkml/git/2.git
	git clone --mirror https://lore.kernel.org/lkml/3 lkml/git/3.git
	git clone --mirror https://lore.kernel.org/lkml/4 lkml/git/4.git
	git clone --mirror https://lore.kernel.org/lkml/5 lkml/git/5.git
	git clone --mirror https://lore.kernel.org/lkml/6 lkml/git/6.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 lkml lkml/ https://lore.kernel.org/lkml \
		linux-kernel@vger.kernel.org linux-kernel@archiver.kernel.org
	public-inbox-index lkml


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-kernel


AGPL code for this site: git clone https://public-inbox.org/ public-inbox