Re: [PATCH 31/32] kvm: Use private inode list instead of i_private_list

On Wed 04-03-26 14:40:33, Christian Brauner wrote:
> On Tue, Mar 03, 2026 at 11:34:20AM +0100, Jan Kara wrote:
> > Instead of using mapping->i_private_list use a list in private part of
> > the inode.
> > 
> > Signed-off-by: Jan Kara <[email protected]>
> > ---
> >  virt/kvm/guest_memfd.c | 12 +++++++-----
> >  1 file changed, 7 insertions(+), 5 deletions(-)
> > 
> > diff --git a/virt/kvm/guest_memfd.c b/virt/kvm/guest_memfd.c
> > index 017d84a7adf3..6d36a7827870 100644
> > --- a/virt/kvm/guest_memfd.c
> > +++ b/virt/kvm/guest_memfd.c
> > @@ -30,6 +30,7 @@ struct gmem_file {
> >  struct gmem_inode {
> >  	struct shared_policy policy;
> >  	struct inode vfs_inode;
> > +	struct list_head gem_file_list;
> 
> I think that needs to be gMem_file_list not, gem_file_list.

Right, fixed. Thanks!

								Honza

-- 
Jan Kara <[email protected]>
SUSE Labs, CR

--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to [email protected].  For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"[email protected]">[email protected]</a>