linux-kernel - Re: [PATCH v3 00/17] Provide a new two step DMA mapping API

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: <20241114170247.GA5813@lst.de>
Date: Thu, 14 Nov 2024 18:02:47 +0100
From: Christoph Hellwig <hch@....de>
To: Leon Romanovsky <leon@...nel.org>
Cc: Christoph Hellwig <hch@....de>, Robin Murphy <robin.murphy@....com>,
	Jens Axboe <axboe@...nel.dk>, Jason Gunthorpe <jgg@...pe.ca>,
	Joerg Roedel <joro@...tes.org>, ill Deacon <will@...nel.org>,
	Sagi Grimberg <sagi@...mberg.me>, Keith Busch <kbusch@...nel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Logan Gunthorpe <logang@...tatee.com>,
	Yishai Hadas <yishaih@...dia.com>,
	Shameer Kolothum <shameerali.kolothum.thodi@...wei.com>,
	Kevin Tian <kevin.tian@...el.com>,
	Alex Williamson <alex.williamson@...hat.com>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Jérôme Glisse <jglisse@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Jonathan Corbet <corbet@....net>, linux-doc@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-block@...r.kernel.org,
	linux-rdma@...r.kernel.org, iommu@...ts.linux.dev,
	linux-nvme@...ts.infradead.org, linux-pci@...r.kernel.org,
	kvm@...r.kernel.org, linux-mm@...ck.org,
	Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [PATCH v3 00/17] Provide a new two step DMA mapping API

On Thu, Nov 14, 2024 at 06:48:23PM +0200, Leon Romanovsky wrote:
> It is fine, but as a bare minimum, I would expect some sort of response,
> so I won't sit and wait for unknown date when this API will be acknowledged/NACKed.
> 
> I would like to start to work on next step, e.g removing SG from RDMA,
> and I need to know if this foundation is stable to do so.
> 
> > 
> > No changs to dma-iommu.c are going to get merged without an explicit
> > ACK from Robin, and while there is no 100% for the core dma-mapping
> > code I will also not merge anything that hasn't been resolved with
> > my most trusted reviewer first, not even code I wrote myself.
> 
> And do you know what is not resolved here? I don't.
> All technical questions/issues were handled.

Let's just wait a little bit, we're all overworked can't instantly
context switch.