linux-kernel - Re: [PATCH] spi: dw: Set transfer handler before unmasking the IRQs

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: <160565269952.23908.7875361978634320011.b4-ty@kernel.org>
Date:   Tue, 17 Nov 2020 22:38:19 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Serge Semin <Sergey.Semin@...kalelectronics.ru>,
        Serge Semin <fancer.lancer@...il.com>
Cc:     linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
        Pavel Parkhomenko <Pavel.Parkhomenko@...kalelectronics.ru>,
        Alexey Malahov <Alexey.Malahov@...kalelectronics.ru>,
        Ramil Zaripov <Ramil.Zaripov@...kalelectronics.ru>
Subject: Re: [PATCH] spi: dw: Set transfer handler before unmasking the IRQs

On Tue, 17 Nov 2020 12:40:54 +0300, Serge Semin wrote:
> It turns out the IRQs most like can be unmasked before the controller is
> enabled with no problematic consequences. The manual doesn't explicitly
> state that, but the examples perform the controller initialization
> procedure in that order. So the commit da8f58909e7e ("spi: dw: Unmask IRQs
> after enabling the chip") hasn't been that required as I thought. But
> anyway setting the IRQs up after the chip enabling still worth adding
> since it has simplified the code a bit. The problem is that it has
> introduced a potential bug. The transfer handler pointer is now
> initialized after the IRQs are enabled. That may and eventually will cause
> an invalid or uninitialized callback invocation. Fix that just by
> performing the callback initialization before the IRQ unmask procedure.

Applied to

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

Thanks!

[1/1] spi: dw: Set transfer handler before unmasking the IRQs
      commit: a41b0ad07bfa081584218431cb0cd7e7ecc71210

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