[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <8f00216a-cf11-4866-ba69-1d398e35f929@amd.com>
Date: Sun, 29 Jun 2025 23:55:13 +0530
From: Shivank Garg <shivankg@....com>
To: "Huang, Ying" <ying.huang@...ux.alibaba.com>
Cc: seanjc@...gle.com, david@...hat.com, vbabka@...e.cz, willy@...radead.org,
akpm@...ux-foundation.org, shuah@...nel.org, pbonzini@...hat.com,
brauner@...nel.org, viro@...iv.linux.org.uk, ackerleytng@...gle.com,
paul@...l-moore.com, jmorris@...ei.org, serge@...lyn.com, pvorel@...e.cz,
bfoster@...hat.com, tabba@...gle.com, vannapurve@...gle.com,
chao.gao@...el.com, bharata@....com, nikunj@....com, michael.day@....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, rppt@...nel.org, hch@...radead.org,
cgzones@...glemail.com, ira.weiny@...el.com, rientjes@...gle.com,
roypat@...zon.co.uk, ziy@...dia.com, matthew.brost@...el.com,
joshua.hahnjy@...il.com, rakie.kim@...com, byungchul@...com,
gourry@...rry.net, kent.overstreet@...ux.dev, apopple@...dia.com,
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,
aneeshkumar.kizhakeveetil@....com, 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: [RFC PATCH v8 5/7] KVM: guest_memfd: Add slab-allocated inode
cache
On 6/24/2025 9:46 AM, Huang, Ying wrote:
> Shivank Garg <shivankg@....com> writes:
>
>> +static void kvm_gmem_init_inodecache(void)
>> +{
>> + kvm_gmem_inode_cachep = kmem_cache_create("kvm_gmem_inode_cache",
>> + sizeof(struct kvm_gmem_inode_info),
>> + 0, SLAB_ACCOUNT,
>> + kvm_gmem_init_inode);
>
> Check the return value?
>
> And, I'm not a big fan of (logically) one line function encapsulation.
>
>> +}
>> +
>> int kvm_gmem_init(struct module *module)
>> {
>> kvm_gmem_fops.owner = module;
>>
>> + kvm_gmem_init_inodecache();
>> return kvm_gmem_init_mount();
>
> kmem_cache_destroy(kvm_gmem_inode_cachep) if kvm_gmem_init_mount()
> return with error?
>
Thanks for the feedback, Ying.
Good catch on the leak!
Regarding the missing error check, I noticed while looking at examples that
kernel code is sometimes inconsistent with kmem_cache_create() error handling,
but you're right about checking for failures, So I'll handle them properly.
diff --git a/virt/kvm/guest_memfd.c b/virt/kvm/guest_memfd.c
index 7b8c548986d4..8cb83692f7a0 100644
--- a/virt/kvm/guest_memfd.c
+++ b/virt/kvm/guest_memfd.c
@@ -530,20 +530,23 @@ static void kvm_gmem_init_inode(void *foo)
inode_init_once(&info->vfs_inode);
}
-static void kvm_gmem_init_inodecache(void)
+int kvm_gmem_init(struct module *module)
{
+ int ret;
+
+ kvm_gmem_fops.owner = module;
kvm_gmem_inode_cachep = kmem_cache_create("kvm_gmem_inode_cache",
sizeof(struct kvm_gmem_inode_info),
0, SLAB_ACCOUNT,
kvm_gmem_init_inode);
-}
-
-int kvm_gmem_init(struct module *module)
-{
- kvm_gmem_fops.owner = module;
-
- kvm_gmem_init_inodecache();
- return kvm_gmem_init_mount();
+ if (!kvm_gmem_inode_cachep)
+ return -ENOMEM;
+ ret = kvm_gmem_init_mount();
+ if (ret) {
+ kmem_cache_destroy(kvm_gmem_inode_cachep);
+ return ret;
+ }
+ return 0;
}
Best Regards,
Shivank
Powered by blists - more mailing lists