linux-kernel - Re: [PATCH v1 0/2] soi: Don't call DMA sync API when not needed

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

Message-Id: <171647977136.55224.8875410677372985509.b4-ty@kernel.org>
Date: Thu, 23 May 2024 16:56:11 +0100
From: Mark Brown <broonie@...nel.org>
To: linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org, 
 Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [PATCH v1 0/2] soi: Don't call DMA sync API when not needed

On Wed, 22 May 2024 20:09:48 +0300, Andy Shevchenko wrote:
> A couple of fixes to avoid calling DMA sync API when it's not needed.
> This doesn't stop from discussing if IOMMU code is doing the right thing,
> i.e. dereferences SG list when orig_nents == 0, but this is a separate
> story.
> 
> Andy Shevchenko (2):
>   spi: Don't mark message DMA mapped when no transfer in it is
>   spi: Check if transfer is mapped before calling DMA sync APIs
> 
> [...]

Applied to

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

Thanks!

[1/2] spi: Don't mark message DMA mapped when no transfer in it is
      commit: 9f788ba457b45b0ce422943fcec9fa35c4587764
[2/2] spi: Check if transfer is mapped before calling DMA sync APIs
      commit: da560097c05612f8d360f86528f6213629b9c395

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