[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86plt1lw2h.wl-maz@kernel.org>
Date: Fri, 31 May 2024 18:39:50 +0100
From: Marc Zyngier <maz@...nel.org>
To: Hagar Hemdan <hagarhem@...zon.com>,
Thomas Gleixner <tglx@...utronix.de>
Cc: Maximilian Heyne <mheyne@...zon.de>,
Norbert Manthey <nmanthey@...zon.de>,
Eric Auger <eric.auger@...hat.com>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4] irqchip/gic-v3-its: Fix potential race condition in its_vlpi_prop_update()
On Fri, 31 May 2024 17:21:44 +0100,
Hagar Hemdan <hagarhem@...zon.com> wrote:
>
> its_vlpi_prop_update() calls lpi_write_config() which obtains the
> mapping information for a VLPI without lock held. So it could race
> with its_vlpi_unmap().
> Since all calls from its_irq_set_vcpu_affinity() require the same
> lock to be held. So instead of peppering the locking all over the
> place, we hoist the locking into its_irq_set_vcpu_affinity().
This looks odd. Maybe something along the lines of:
"Since all calls from its_irq_set_vcpu_affinity() require the same
lock to be held, hoist the locking there instead of peppering it over
the place."
>
> This bug was discovered using Coverity Static Analysis
> Security Testing (SAST) by Synopsys, Inc.
>
> Fixes: 015ec0386ab6 ("irqchip/gic-v3-its: Add VLPI configuration handling")
> Suggested-by: Marc Zyngier <maz@...nel.org>
> Signed-off-by: Hagar Hemdan <hagarhem@...zon.com>
With the above addressed,
Reviewed-by: Marc Zyngier <maz@...nel.org>
Cc: stable@...r.kernel.org
Thomas, can you please queue it at your earliest convenience?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists