linux-kernel - Re: [PATCH v1 1/1] spi: topcliff-pch: Prevent usage of potentially stale DMA device

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 for Android: free password hash cracker in your pocket

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

Message-Id: <164676009024.54618.554477208922214231.b4-ty@kernel.org>
Date:   Tue, 08 Mar 2022 17:21:30 +0000
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        linux-spi@...r.kernel.org
Cc:     Wang Qing <wangqing@...o.com>,
        Christophe JAILLET <christophe.jaillet@...adoo.fr>
Subject: Re: [PATCH v1 1/1] spi: topcliff-pch: Prevent usage of potentially stale DMA device

On Mon, 7 Mar 2022 19:37:40 +0200, Andy Shevchenko wrote:
> DMA device is expected to be available while SPI transfer is ongoing.
> 
> Prevent usage of potentially stale DMA device by keeping reference
> count till the end of the transfer.
> 
> 

Applied to

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

Thanks!

[1/1] spi: topcliff-pch: Prevent usage of potentially stale DMA device
      commit: 80ab9012bbf1011f57c06b3c6e4ac3816c4a86f5

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