From: David Hildenbrand <david@redhat.com>
To: "Garg, Shivank" <shivankg@amd.com>,
Sean Christopherson <seanjc@google.com>,
Ackerley Tng <ackerleytng@google.com>
Cc: willy@infradead.org, akpm@linux-foundation.org,
pbonzini@redhat.com, shuah@kernel.org, vbabka@suse.cz,
brauner@kernel.org, viro@zeniv.linux.org.uk, dsterba@suse.com,
xiang@kernel.org, chao@kernel.org, jaegeuk@kernel.org,
clm@fb.com, josef@toxicpanda.com, kent.overstreet@linux.dev,
zbestahu@gmail.com, jefflexu@linux.alibaba.com,
dhavale@google.com, lihongbo22@huawei.com,
lorenzo.stoakes@oracle.com, Liam.Howlett@oracle.com,
rppt@kernel.org, surenb@google.com, mhocko@suse.com,
ziy@nvidia.com, matthew.brost@intel.com, joshua.hahnjy@gmail.com,
rakie.kim@sk.com, byungchul@sk.com, gourry@gourry.net,
ying.huang@linux.alibaba.com, apopple@nvidia.com,
tabba@google.com, paul@paul-moore.com, jmorris@namei.org,
serge@hallyn.com, pvorel@suse.cz, bfoster@redhat.com,
vannapurve@google.com, chao.gao@intel.com, bharata@amd.com,
nikunj@amd.com, michael.day@amd.com, shdhiman@amd.com,
yan.y.zhao@intel.com, Neeraj.Upadhyay@amd.com,
thomas.lendacky@amd.com, michael.roth@amd.com, aik@amd.com,
jgg@nvidia.com, kalyazin@amazon.com, peterx@redhat.com,
jack@suse.cz, hch@infradead.org, cgzones@googlemail.com,
ira.weiny@intel.com, rientjes@google.com, roypat@amazon.co.uk,
chao.p.peng@intel.com, amit@infradead.org, ddutile@redhat.com,
dan.j.williams@intel.com, ashish.kalra@amd.com, gshan@redhat.com,
jgowans@amazon.com, pankaj.gupta@amd.com, papaluri@amd.com,
yuzhao@google.com, suzuki.poulose@arm.com,
quic_eberman@quicinc.com, linux-bcachefs@vger.kernel.org,
linux-btrfs@vger.kernel.org, linux-erofs@lists.ozlabs.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, kvm@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-coco@lists.linux.dev
Subject: Re: [PATCH kvm-next V11 4/7] KVM: guest_memfd: Use guest mem inodes instead of anonymous inodes
Date: Thu, 25 Sep 2025 13:55:26 +0200 [thread overview]
Message-ID: <b67dd7cd-2c1c-4566-badf-32082d8cd952@redhat.com> (raw)
In-Reply-To: <dc6eb85f-87b6-43a1-b1f7-4727c0b834cc@amd.com>
On 25.09.25 13:44, Garg, Shivank wrote:
>
>
> On 9/25/2025 8:20 AM, Sean Christopherson wrote:
>> My apologies for the super late feedback. None of this is critical (mechanical
>> things that can be cleaned up after the fact), so if there's any urgency to
>> getting this series into 6.18, just ignore it.
>>
>> On Wed, Aug 27, 2025, Ackerley Tng wrote:
>>> Shivank Garg <shivankg@amd.com> writes:
>>> @@ -463,11 +502,70 @@ bool __weak kvm_arch_supports_gmem_mmap(struct kvm *kvm)
>>> return true;
>>> }
>>>
>>> +static struct inode *kvm_gmem_inode_create(const char *name, loff_t size,
>>> + u64 flags)
>>> +{
>>> + struct inode *inode;
>>> +
>>> + inode = anon_inode_make_secure_inode(kvm_gmem_mnt->mnt_sb, name, NULL);
>>> + if (IS_ERR(inode))
>>> + return inode;
>>> +
>>> + inode->i_private = (void *)(unsigned long)flags;
>>> + inode->i_op = &kvm_gmem_iops;
>>> + inode->i_mapping->a_ops = &kvm_gmem_aops;
>>> + inode->i_mode |= S_IFREG;
>>> + inode->i_size = size;
>>> + mapping_set_gfp_mask(inode->i_mapping, GFP_HIGHUSER);
>>> + mapping_set_inaccessible(inode->i_mapping);
>>> + /* Unmovable mappings are supposed to be marked unevictable as well. */
>>> + WARN_ON_ONCE(!mapping_unevictable(inode->i_mapping));
>>> +
>>> + return inode;
>>> +}
>>> +
>>> +static struct file *kvm_gmem_inode_create_getfile(void *priv, loff_t size,
>>> + u64 flags)
>>> +{
>>> + static const char *name = "[kvm-gmem]";
>>> + struct inode *inode;
>>> + struct file *file;
>>> + int err;
>>> +
>>> + err = -ENOENT;
>>> + /* __fput() will take care of fops_put(). */
>>> + if (!fops_get(&kvm_gmem_fops))
>>> + goto err;
>>> +
>>> + inode = kvm_gmem_inode_create(name, size, flags);
>>> + if (IS_ERR(inode)) {
>>> + err = PTR_ERR(inode);
>>> + goto err_fops_put;
>>> + }
>>> +
>>> + file = alloc_file_pseudo(inode, kvm_gmem_mnt, name, O_RDWR,
>>> + &kvm_gmem_fops);
>>> + if (IS_ERR(file)) {
>>> + err = PTR_ERR(file);
>>> + goto err_put_inode;
>>> + }
>>> +
>>> + file->f_flags |= O_LARGEFILE;
>>> + file->private_data = priv;
>>> +
>>> + return file;
>>> +
>>> +err_put_inode:
>>> + iput(inode);
>>> +err_fops_put:
>>> + fops_put(&kvm_gmem_fops);
>>> +err:
>>> + return ERR_PTR(err);
>>> +}
>>
>> I don't see any reason to add two helpers. It requires quite a bit more lines
>> of code due to adding more error paths and local variables, and IMO doesn't make
>> the code any easier to read.
>>
>> Passing in "gmem" as @priv is especially ridiculous, as it adds code and
>> obfuscates what file->private_data is set to.
>>
>> I get the sense that the code was written to be a "replacement" for common APIs,
>> but that is nonsensical (no pun intended).
>>
>>> static int __kvm_gmem_create(struct kvm *kvm, loff_t size, u64 flags)
>>> {
>>> - const char *anon_name = "[kvm-gmem]";
>>> struct kvm_gmem *gmem;
>>> - struct inode *inode;
>>> struct file *file;
>>> int fd, err;
>>>
>>> @@ -481,32 +579,16 @@ static int __kvm_gmem_create(struct kvm *kvm, loff_t size, u64 flags)
>>> goto err_fd;
>>> }
>>>
>>> - file = anon_inode_create_getfile(anon_name, &kvm_gmem_fops, gmem,
>>> - O_RDWR, NULL);
>>> + file = kvm_gmem_inode_create_getfile(gmem, size, flags);
>>> if (IS_ERR(file)) {
>>> err = PTR_ERR(file);
>>> goto err_gmem;
>>> }
>>>
>>> - file->f_flags |= O_LARGEFILE;
>>> -
>>> - inode = file->f_inode;
>>> - WARN_ON(file->f_mapping != inode->i_mapping);
>>> -
>>> - inode->i_private = (void *)(unsigned long)flags;
>>> - inode->i_op = &kvm_gmem_iops;
>>> - inode->i_mapping->a_ops = &kvm_gmem_aops;
>>> - inode->i_mode |= S_IFREG;
>>> - inode->i_size = size;
>>> - mapping_set_gfp_mask(inode->i_mapping, GFP_HIGHUSER);
>>> - mapping_set_inaccessible(inode->i_mapping);
>>> - /* Unmovable mappings are supposed to be marked unevictable as well. */
>>> - WARN_ON_ONCE(!mapping_unevictable(inode->i_mapping));
>>> -
>>> kvm_get_kvm(kvm);
>>> gmem->kvm = kvm;
>>> xa_init(&gmem->bindings);
>>> - list_add(&gmem->entry, &inode->i_mapping->i_private_list);
>>> + list_add(&gmem->entry, &file_inode(file)->i_mapping->i_private_list);
>>
>> I don't understand this change? Isn't file_inode(file) == inode?
>>
>> Compile tested only, and again not critical, but it's -40 LoC...
>>
>>
>
> Thanks.
> I did functional testing and it works fine.
I can queue this instead. I guess I can reuse the patch description and
add Sean as author + add his SOB (if he agrees).
Let me take a look at the patch later in more detail.
--
Cheers
David / dhildenb
next prev parent reply other threads:[~2025-09-25 11:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 17:52 [PATCH kvm-next V11 0/7] Add NUMA mempolicy support for KVM guest-memfd Shivank Garg
2025-08-27 17:52 ` [PATCH kvm-next V11 1/7] mm/filemap: Add NUMA mempolicy support to filemap_alloc_folio() Shivank Garg
2025-08-27 17:52 ` [PATCH kvm-next V11 2/7] mm/filemap: Extend __filemap_get_folio() to support NUMA memory policies Shivank Garg
2025-08-27 17:52 ` [PATCH kvm-next V11 3/7] mm/mempolicy: Export memory policy symbols Shivank Garg
2025-08-27 17:52 ` [PATCH kvm-next V11 4/7] KVM: guest_memfd: Use guest mem inodes instead of anonymous inodes Shivank Garg
2025-08-27 22:43 ` Ackerley Tng
2025-08-28 5:49 ` Garg, Shivank
2025-08-28 10:06 ` David Hildenbrand
2025-09-25 2:50 ` Sean Christopherson
2025-09-25 11:44 ` Garg, Shivank
2025-09-25 11:55 ` David Hildenbrand [this message]
2025-09-25 13:41 ` Sean Christopherson
2025-09-25 13:44 ` Fuad Tabba
2025-09-25 14:26 ` David Hildenbrand
2025-09-25 15:06 ` Sean Christopherson
2025-08-27 17:52 ` [PATCH kvm-next V11 5/7] KVM: guest_memfd: Add slab-allocated inode cache Shivank Garg
2025-09-25 14:05 ` Sean Christopherson
2025-09-25 14:17 ` Sean Christopherson
2025-08-27 17:52 ` [PATCH kvm-next V11 6/7] KVM: guest_memfd: Enforce NUMA mempolicy using shared policy Shivank Garg
2025-09-25 14:22 ` Sean Christopherson
2025-09-26 19:36 ` Sean Christopherson
2025-08-27 17:52 ` [PATCH kvm-next V11 7/7] KVM: guest_memfd: selftests: Add tests for mmap and NUMA policy support Shivank Garg
2025-09-25 21:35 ` Sean Christopherson
2025-09-25 23:03 ` Sean Christopherson
2025-09-25 23:04 ` Jason Gunthorpe
2025-09-25 23:12 ` Sean Christopherson
2025-09-26 7:32 ` David Hildenbrand
2025-09-26 7:31 ` David Hildenbrand
2025-09-26 7:37 ` Garg, Shivank
2025-08-28 12:44 ` [PATCH kvm-next V11 0/7] Add NUMA mempolicy support for KVM guest-memfd David Hildenbrand
2025-09-24 18:19 ` David Hildenbrand
2025-09-24 20:35 ` Kalra, Ashish
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b67dd7cd-2c1c-4566-badf-32082d8cd952@redhat.com \
--to=david@redhat.com \
--cc=Liam.Howlett@oracle.com \
--cc=Neeraj.Upadhyay@amd.com \
--cc=ackerleytng@google.com \
--cc=aik@amd.com \
--cc=akpm@linux-foundation.org \
--cc=amit@infradead.org \
--cc=apopple@nvidia.com \
--cc=ashish.kalra@amd.com \
--cc=bfoster@redhat.com \
--cc=bharata@amd.com \
--cc=brauner@kernel.org \
--cc=byungchul@sk.com \
--cc=cgzones@googlemail.com \
--cc=chao.gao@intel.com \
--cc=chao.p.peng@intel.com \
--cc=chao@kernel.org \
--cc=clm@fb.com \
--cc=dan.j.williams@intel.com \
--cc=ddutile@redhat.com \
--cc=dhavale@google.com \
--cc=dsterba@suse.com \
--cc=gourry@gourry.net \
--cc=gshan@redhat.com \
--cc=hch@infradead.org \
--cc=ira.weiny@intel.com \
--cc=jack@suse.cz \
--cc=jaegeuk@kernel.org \
--cc=jefflexu@linux.alibaba.com \
--cc=jgg@nvidia.com \
--cc=jgowans@amazon.com \
--cc=jmorris@namei.org \
--cc=josef@toxicpanda.com \
--cc=joshua.hahnjy@gmail.com \
--cc=kalyazin@amazon.com \
--cc=kent.overstreet@linux.dev \
--cc=kvm@vger.kernel.org \
--cc=lihongbo22@huawei.com \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=matthew.brost@intel.com \
--cc=mhocko@suse.com \
--cc=michael.day@amd.com \
--cc=michael.roth@amd.com \
--cc=nikunj@amd.com \
--cc=pankaj.gupta@amd.com \
--cc=papaluri@amd.com \
--cc=paul@paul-moore.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=pvorel@suse.cz \
--cc=quic_eberman@quicinc.com \
--cc=rakie.kim@sk.com \
--cc=rientjes@google.com \
--cc=roypat@amazon.co.uk \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=serge@hallyn.com \
--cc=shdhiman@amd.com \
--cc=shivankg@amd.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=thomas.lendacky@amd.com \
--cc=vannapurve@google.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=xiang@kernel.org \
--cc=yan.y.zhao@intel.com \
--cc=ying.huang@linux.alibaba.com \
--cc=yuzhao@google.com \
--cc=zbestahu@gmail.com \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).