linux-kernel - Re: [PATCH v6 5/6] vfio/nvgrace-gpu: Inform devmem unmapped after reset

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: <20251125215404.14c969be@shazbot.org>
Date: Tue, 25 Nov 2025 21:54:04 -0700
From: Alex Williamson <alex@...zbot.org>
To: Ankit Agrawal <ankita@...dia.com>
Cc: "jgg@...pe.ca" <jgg@...pe.ca>, Yishai Hadas <yishaih@...dia.com>,
 Shameer Kolothum <skolothumtho@...dia.com>,
 "kevin.tian@...el.com" <kevin.tian@...el.com>,
 Aniket Agashe <aniketa@...dia.com>, Vikram Sethi <vsethi@...dia.com>,
 Matt Ochs <mochs@...dia.com>,
 "Yunxiang.Li@....com" <Yunxiang.Li@....com>,
 "yi.l.liu@...el.com" <yi.l.liu@...el.com>,
 "zhangdongdong@...incomputing.com" <zhangdongdong@...incomputing.com>,
 Avihai Horon <avihaih@...dia.com>,
 "bhelgaas@...gle.com" <bhelgaas@...gle.com>,
 "peterx@...hat.com" <peterx@...hat.com>,
 "pstanner@...hat.com" <pstanner@...hat.com>,
 Alistair Popple <apopple@...dia.com>,
 "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
 "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
 Neo Jia <cjia@...dia.com>, Kirti Wankhede <kwankhede@...dia.com>,
 "Tarun Gupta (SW-GPU)" <targupta@...dia.com>, Zhi Wang <zhiw@...dia.com>,
 Dan Williams <danw@...dia.com>, Dheeraj Nigam <dnigam@...dia.com>,
 Krishnakant Jaju <kjaju@...dia.com>
Subject: Re: [PATCH v6 5/6] vfio/nvgrace-gpu: Inform devmem unmapped after
 reset

On Wed, 26 Nov 2025 03:26:54 +0000
Ankit Agrawal <ankita@...dia.com> wrote:

> >>  MODULE_DEVICE_TABLE(pci, nvgrace_gpu_vfio_pci_table);
> >>  
> > /*
> >  * Comment explaining why this can't use lockdep_assert_held_write but
> >  * in vfio use cases relies on this for serialization against faults and
> >  * read/write.
> >  */
> >  
> 
> In this patch or the next where we actually do the serialization with
> memory_lock?

When the interaction is added would make more sense.  Thanks,

Alex