linux-kernel - Re: [PATCH] spi: spi-nxp-fspi: fix fspi panic by unexpected interrupts

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: <160614636910.30914.5128110420712253812.b4-ty@kernel.org>
Date:   Mon, 23 Nov 2020 15:46:09 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Ashish Kumar <ashish.kumar@....com>,
        Yogesh Gaur <yogeshgaur.83@...il.com>, Han Xu <han.xu@....com>,
        Ran Wang <ran.wang_1@....com>
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: spi-nxp-fspi: fix fspi panic by unexpected interrupts

On Mon, 23 Nov 2020 10:57:15 +0800, Ran Wang wrote:
> Given the case that bootloader(such as UEFI)'s FSPI driver might not
> handle all interrupts before loading kernel, those legacy interrupts
> would assert immidiately once kernel's FSPI driver enable them. Further,
> if it was FSPI_INTR_IPCMDDONE, the irq handler nxp_fspi_irq_handler()
> would call complete(&f->c) to notify others. However, f->c might not be
> initialized yet at that time, then cause kernel panic.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-nxp-fspi: fix fspi panic by unexpected interrupts
      commit: 71d80563b0760a411cd90a3680536f5d887fff6b

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