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: <20251109075331.GA376289@unreal>
Date: Sun, 9 Nov 2025 09:53:31 +0200
From: Leon Romanovsky <leon@...nel.org>
To: Jens Axboe <axboe@...nel.dk>, Keith Busch <kbusch@...nel.org>,
	Christoph Hellwig <hch@....de>, Sagi Grimberg <sagi@...mberg.me>
Cc: linux-block@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-nvme@...ts.infradead.org
Subject: Re: [PATCH v3 0/2] block: Enable proper MMIO memory handling for P2P
 DMA

On Mon, Oct 27, 2025 at 09:30:19AM +0200, Leon Romanovsky wrote:

<...>

> ----------------------------------------------------------------------
> 
> This patch series improves block layer and NVMe driver support for MMIO
> memory regions, particularly for peer-to-peer (P2P) DMA transfers that
> go through the host bridge.
> 
> The series addresses a critical gap where P2P transfers through the host
> bridge (PCI_P2PDMA_MAP_THRU_HOST_BRIDGE) were not properly marked as
> MMIO memory, leading to potential issues with:
> 
> - Inappropriate CPU cache synchronization operations on MMIO regions
> - Incorrect DMA mapping/unmapping that doesn't respect MMIO semantics  
> - Missing IOMMU configuration for MMIO memory handling
> 
> This work is extracted from the larger DMA physical API improvement
> series [1] and focuses specifically on block layer and NVMe requirements
> for MMIO memory support.
> 
> Thanks
> 
> [1] https://lore.kernel.org/all/cover.1757423202.git.leonro@nvidia.com/
> 
> Leon Romanovsky (2):
>       nvme-pci: migrate to dma_map_phys instead of map_page
>       block-dma: properly take MMIO path

Hi,

Kind reminder.

Thanks

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ