From: Jeff Layton <jlayton@kernel.org>
To: Jan Kara <jack@suse.cz>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>,
Christoph Hellwig <hch@lst.de>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] vfs: remove externs from fs.h on functions modified by i_ino widening
Date: Mon, 09 Mar 2026 07:53:51 -0400 [thread overview]
Message-ID: <c73452245cd85a75bbfc12b31b940641352fb979.camel@kernel.org> (raw)
In-Reply-To: <urwtj2zfmxfhksormxkzb2z26a7nt5vesbkuwtow47fflf4u2l@x7cbae5dv7tr>
On Mon, 2026-03-09 at 11:02 +0100, Jan Kara wrote:
> On Sat 07-03-26 14:54:31, Jeff Layton wrote:
> > Christoph says, in response to one of the patches in the i_ino widening
> > series, which changes the prototype of several functions in fs.h:
> >
> > "Can you please drop all these pointless externs while you're at it?"
> >
> > Remove extern keyword from functions touched by that patch (and a few
> > that happened to be nearby). Also add missing argument names to
> > declarations that lacked them.
> >
> > Suggested-by: Christoph Hellwig <hch@lst.de>
> > Reviewed-by: Christoph Hellwig <hch@lst.de>
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ...
> > -extern void inode_init_once(struct inode *);
> > -extern void address_space_init_once(struct address_space *mapping);
> > -extern struct inode * igrab(struct inode *);
> > -extern ino_t iunique(struct super_block *, ino_t);
> > -extern int inode_needs_sync(struct inode *inode);
> > -extern int inode_just_drop(struct inode *inode);
> > +void inode_init_once(struct inode *inode);
> > +void address_space_init_once(struct address_space *mapping);
> > +struct inode *igrab(struct inode *inode);
> > +ino_t iunique(struct super_block *sb, ino_t max_reserved);
>
> I've just noticed that we probably forgot to convert iunique() to use u64
> for inode numbers... Although the iunique() number allocator might prefer
> to stay within 32 bits, the interfaces should IMO still use u64 for
> consistency.
>
I went back and forth on that one, but I left iunique() changes off
since they weren't strictly required. Most filesystems that use it
won't have more than 2^32 inodes anyway.
If they worked before with iunique() limited to 32-bit values, they
should still after this. After the i_ino widening we could certainly
change it to return a u64 though.
> Otherwise I like the changes in this patch so feel free to add:
>
> Reviewed-by: Jan Kara <jack@suse.cz>
>
Thanks!
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2026-03-09 11:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-07 19:54 Jeff Layton
2026-03-09 10:02 ` Jan Kara
2026-03-09 11:53 ` Jeff Layton [this message]
2026-03-09 12:27 ` Jan Kara
2026-03-09 13:27 ` Jeff Layton
2026-03-09 14:46 ` Jan Kara
2026-03-09 14:56 ` Jeff Layton
2026-03-09 15:21 ` Jan Kara
2026-03-09 10:28 ` Christian Brauner
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=c73452245cd85a75bbfc12b31b940641352fb979.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®