linux-kernel - Re: [PATCH kvm-next V11 4/7] KVM: guest_memfd: Use guest mem inodes instead of anonymous inodes

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: <aNVahJkpJVVTVEkK@google.com>
Date: Thu, 25 Sep 2025 08:06:44 -0700
From: Sean Christopherson <seanjc@...gle.com>
To: David Hildenbrand <david@...hat.com>
Cc: Shivank Garg <shivankg@....com>, Ackerley Tng <ackerleytng@...gle.com>, willy@...radead.org, 
	akpm@...ux-foundation.org, pbonzini@...hat.com, shuah@...nel.org, 
	vbabka@...e.cz, brauner@...nel.org, viro@...iv.linux.org.uk, dsterba@...e.com, 
	xiang@...nel.org, chao@...nel.org, jaegeuk@...nel.org, clm@...com, 
	josef@...icpanda.com, kent.overstreet@...ux.dev, zbestahu@...il.com, 
	jefflexu@...ux.alibaba.com, dhavale@...gle.com, lihongbo22@...wei.com, 
	lorenzo.stoakes@...cle.com, Liam.Howlett@...cle.com, rppt@...nel.org, 
	surenb@...gle.com, mhocko@...e.com, ziy@...dia.com, matthew.brost@...el.com, 
	joshua.hahnjy@...il.com, rakie.kim@...com, byungchul@...com, 
	gourry@...rry.net, ying.huang@...ux.alibaba.com, apopple@...dia.com, 
	tabba@...gle.com, paul@...l-moore.com, jmorris@...ei.org, serge@...lyn.com, 
	pvorel@...e.cz, bfoster@...hat.com, vannapurve@...gle.com, chao.gao@...el.com, 
	bharata@....com, nikunj@....com, michael.day@....com, shdhiman@....com, 
	yan.y.zhao@...el.com, Neeraj.Upadhyay@....com, thomas.lendacky@....com, 
	michael.roth@....com, aik@....com, jgg@...dia.com, kalyazin@...zon.com, 
	peterx@...hat.com, jack@...e.cz, hch@...radead.org, cgzones@...glemail.com, 
	ira.weiny@...el.com, rientjes@...gle.com, roypat@...zon.co.uk, 
	chao.p.peng@...el.com, amit@...radead.org, ddutile@...hat.com, 
	dan.j.williams@...el.com, ashish.kalra@....com, gshan@...hat.com, 
	jgowans@...zon.com, pankaj.gupta@....com, papaluri@....com, yuzhao@...gle.com, 
	suzuki.poulose@....com, quic_eberman@...cinc.com, 
	linux-bcachefs@...r.kernel.org, linux-btrfs@...r.kernel.org, 
	linux-erofs@...ts.ozlabs.org, linux-f2fs-devel@...ts.sourceforge.net, 
	linux-fsdevel@...r.kernel.org, linux-mm@...ck.org, 
	linux-kernel@...r.kernel.org, linux-security-module@...r.kernel.org, 
	kvm@...r.kernel.org, linux-kselftest@...r.kernel.org, 
	linux-coco@...ts.linux.dev
Subject: Re: [PATCH kvm-next V11 4/7] KVM: guest_memfd: Use guest mem inodes
 instead of anonymous inodes

On Thu, Sep 25, 2025, David Hildenbrand wrote:
> On 25.09.25 15:41, Sean Christopherson wrote:
> > Regarding timing, how much do people care about getting this into 6.18 in
> > particular?
> 
> I think it will be beneficial if we start getting stuff upstream. But
> waiting a bit longer probably doesn't hurt.
> 
> > AFAICT, this hasn't gotten any coverage in -next, which makes me a
> > little nervous.
> 
> Right.
> 
> If we agree, then Shivank can just respin a new version after the merge
> window.

Actually, if Shivank is ok with it, I'd be happy to post the next version(s).
I'll be focusing on the in-place conversion support for the next 1-2 weeks, and
have some (half-baked) refactoring changes to better leverage the inode support
from this series.

I can also plop the first three patches (the non-KVM changes) in a topic branch
straightaway, but not feed it into -next until the merge window closes.  The 0-day
bots scrapes kvm-x86, so that'd get us some early build-bot exposure, and we can
stop bugging the non-KVM folks.  Then when the dust settles on the KVM changes,
I can throw them into the same topic branch.