linux-kernel - Re: [patch 2/8] genirq/generic_pending: Do not lose pending affinity update

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <74a8cfe1-56e4-6082-1d53-a76faf5105eb@cn.fujitsu.com>
Date:   Tue, 5 Jun 2018 19:20:35 +0800
From:   Dou Liyang <douly.fnst@...fujitsu.com>
To:     Thomas Gleixner <tglx@...utronix.de>,
        LKML <linux-kernel@...r.kernel.org>
CC:     Ingo Molnar <mingo@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        Borislav Petkov <bp@...en8.de>,
        Dmitry Safonov <0x7f454c46@...il.com>,
        Tariq Toukan <tariqt@...lanox.com>,
        Song Liu <liu.song.a23@...il.com>,
        Joerg Roedel <jroedel@...e.de>,
        Mike Travis <mike.travis@....com>, <stable@...r.kernel.org>
Subject: Re: [patch 2/8] genirq/generic_pending: Do not lose pending affinity
 update

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@...utronix.de>
> Cc:stable@...r.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