linux-kernel - Re: [PATCH 2/3] dma-mapping: don't return errors from dma_set_seg

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: <20240801133353.GA1846@lst.de>
Date: Thu, 1 Aug 2024 15:33:53 +0200
From: Christoph Hellwig <hch@....de>
To: Robin Murphy <robin.murphy@....com>
Cc: Marek Szyprowski <m.szyprowski@...sung.com>,
	Christoph Hellwig <hch@....de>, iommu@...ts.linux.dev,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] dma-mapping: don't return errors from
 dma_set_seg_boundary

On Thu, Aug 01, 2024 at 01:36:01PM +0100, Robin Murphy wrote:
> I guess I assumed that the old block layer bodges in this area had been 
> cleaned up already - perhaps it *is* high time for whatever's left to grow 
> a proper understanding of whether a block device actually does its own DMA 
> or not.

Can you point to a discussion on that?  The concepts here don't make
quite sense to me.