From: Carlos Maiolino <cem@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: hughd@google.com, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org, djwong@kernel.org
Subject: Re: [PATCH V2 2/6] shmem: make shmem_get_inode() return ERR_PTR instead of NULL
Date: Thu, 20 Apr 2023 15:40:43 +0200 [thread overview]
Message-ID: <20230420134043.25rxcb4du4wm6h2f@andromeda> (raw)
In-Reply-To: <20230420132516.qbrwe4cuvhckde7b@quack3>
On Thu, Apr 20, 2023 at 03:25:16PM +0200, Jan Kara wrote:
> On Thu 20-04-23 10:03:55, cem@kernel.org wrote:
> > From: Lukas Czerner <lczerner@redhat.com>
> >
> > Make shmem_get_inode() return ERR_PTR instead of NULL on error. This will be
> > useful later when we introduce quota support.
> >
> > There should be no functional change.
> >
> > Signed-off-by: Lukas Czerner <lczerner@redhat.com>
> > Signed-off-by: Carlos Maiolino <cmaiolino@redhat.com>
>
> Looks good to me except for one problem with ramfs fallback:
>
> > @@ -4209,10 +4228,16 @@ EXPORT_SYMBOL_GPL(shmem_truncate_range);
> > #define shmem_vm_ops generic_file_vm_ops
> > #define shmem_anon_vm_ops generic_file_vm_ops
> > #define shmem_file_operations ramfs_file_operations
> > -#define shmem_get_inode(idmap, sb, dir, mode, dev, flags) ramfs_get_inode(sb, dir, mode, dev)
> > #define shmem_acct_size(flags, size) 0
> > #define shmem_unacct_size(flags, size) do {} while (0)
> >
> > +static inline struct inode *shmem_get_inode(struct mnt_idmap, struct super_block *sb, struct inode *dir,
> > + umode_t mode, dev_t dev, unsigned long flags)
>
> IMO this won't even compile - "struct mnt_idmap," does not look like valid
> C.
True, I totally overlooked at it as I've been testing with/without TMPFS_QUOTA
and QUOTA, I totally forgot to disable CONFIG_SHMEM for testing.
I'll update it on a next version once we get a few eyes on it.
Thanks for spotting it Honza!
>
> Honza
> --
> Jan Kara <jack@suse.com>
> SUSE Labs, CR
--
Carlos Maiolino
next prev parent reply other threads:[~2023-04-20 13:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 8:03 [PATCH V2 0/6] shmem: Add user and group quota support for tmpfs cem
2023-04-20 8:03 ` [PATCH V2 1/6] shmem: make shmem_inode_acct_block() return error cem
2023-04-20 13:17 ` Jan Kara
2023-04-20 8:03 ` [PATCH V2 2/6] shmem: make shmem_get_inode() return ERR_PTR instead of NULL cem
2023-04-20 13:25 ` Jan Kara
2023-04-20 13:40 ` Carlos Maiolino [this message]
2023-04-25 11:54 ` [PATCH V3 " cem
2023-04-25 12:32 ` Jan Kara
2023-04-20 8:03 ` [PATCH 3/6] quota: Check presence of quota operation structures instead of ->quota_read and ->quota_write callbacks cem
2023-04-20 8:03 ` [PATCH V2 4/6] shmem: prepare shmem quota infrastructure cem
2023-04-20 13:38 ` Jan Kara
2023-04-20 8:03 ` [PATCH V2 5/6] shmem: quota support cem
2023-04-20 14:02 ` Jan Kara
2023-04-20 8:03 ` [PATCH 6/6] Add default quota limit mount options cem
2023-04-20 14:39 ` Jan Kara
2023-04-21 10:20 ` Carlos Maiolino
2023-04-21 10:47 ` Jan Kara
2023-04-21 12:34 ` Carlos Maiolino
2023-04-25 11:57 ` [PATCH V3 " cem
2023-04-25 12:30 ` Jan Kara
2023-04-25 12:56 ` Carlos Maiolino
2023-04-25 13:21 ` Jan Kara
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=20230420134043.25rxcb4du4wm6h2f@andromeda \
--to=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=hughd@google.com \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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).