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
| ||
|
Date: Wed, 29 Jun 2022 08:48:54 +0200 From: Christoph Hellwig <hch@....de> To: Logan Gunthorpe <logang@...tatee.com> Cc: linux-kernel@...r.kernel.org, linux-nvme@...ts.infradead.org, linux-block@...r.kernel.org, linux-pci@...r.kernel.org, linux-mm@...ck.org, iommu@...ts.linux-foundation.org, Stephen Bates <sbates@...thlin.com>, Christoph Hellwig <hch@....de>, Dan Williams <dan.j.williams@...el.com>, Jason Gunthorpe <jgg@...pe.ca>, Christian König <christian.koenig@....com>, John Hubbard <jhubbard@...dia.com>, Don Dutile <ddutile@...hat.com>, Matthew Wilcox <willy@...radead.org>, Daniel Vetter <daniel.vetter@...ll.ch>, Minturn Dave B <dave.b.minturn@...el.com>, Jason Ekstrand <jason@...kstrand.net>, Dave Hansen <dave.hansen@...ux.intel.com>, Xiong Jianxin <jianxin.xiong@...el.com>, Bjorn Helgaas <helgaas@...nel.org>, Ira Weiny <ira.weiny@...el.com>, Robin Murphy <robin.murphy@....com>, Martin Oliveira <martin.oliveira@...eticom.com>, Chaitanya Kulkarni <ckulkarnilinux@...il.com>, Ralph Campbell <rcampbell@...dia.com>, Bjorn Helgaas <bhelgaas@...gle.com> Subject: Re: [PATCH v7 20/21] PCI/P2PDMA: Introduce pci_mmap_p2pmem() On Wed, Jun 15, 2022 at 10:12:32AM -0600, Logan Gunthorpe wrote: > A pseudo mount is used to allocate an inode for each PCI device. The > inode's address_space is used in the file doing the mmap so that all > VMAs are collected and can be unmapped if the PCI device is unbound. > After unmapping, the VMAs are iterated through and their pages are > put so the device can continue to be unbound. An active flag is used > to signal to VMAs not to allocate any further P2P memory once the > removal process starts. The flag is synchronized with concurrent > access with an RCU lock. Can't we come up with a way of doing this without all the pseudo-fs garbagage? I really hate all the overhead for that in the next nvme patch as well.
Powered by blists - more mailing lists