linux-kernel - Re: [PATCH] spi: stm32: clear only asserted irq flags on interrupt

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] [day] [month] [year] [list]

Message-Id: <159664291990.49398.7013081287878568700.b4-ty@kernel.org>
Date:   Wed, 05 Aug 2020 16:55:19 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Maxime Coquelin <mcoquelin.stm32@...il.com>,
        Alexandre Torgue <alexandre.torgue@...com>,
        Tobias Schramm <t.schramm@...jaro.org>
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: stm32: clear only asserted irq flags on interrupt

On Tue, 4 Aug 2020 21:51:36 +0200, Tobias Schramm wrote:
> Previously the stm32h7 interrupt thread cleared all non-masked interrupts.
> If an interrupt was to occur during the handling of another interrupt its
> flag would be unset, resulting in a lost interrupt.
> This patches fixes the issue by clearing only the currently set interrupt
> flags.

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next

Thanks!

[1/1] spi: stm32: clear only asserted irq flags on interrupt
      commit: ae1ba50f1e706dfd7ce402ac52c1f1f10becad68

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark