From: Jeff Layton <jlayton@kernel.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>, tahsin@google.com
Cc: adilger.kernel@dilger.ca, tytso@mit.edu,
linux-ext4@vger.kernel.org, dhowells@redhat.com
Subject: Re: [RFC PATCH] ext4: don't split xattr inode refcounts across i_ctime and i_version fields
Date: Tue, 09 Jan 2018 14:05:31 -0500 [thread overview]
Message-ID: <1515524731.3571.16.camel@kernel.org> (raw)
In-Reply-To: <20180109185249.GA5594@magnolia>
On Tue, 2018-01-09 at 10:52 -0800, Darrick J. Wong wrote:
> On Tue, Jan 09, 2018 at 09:47:01AM -0500, Jeff Layton wrote:
> > From: Jeff Layton <jlayton@redhat.com>
> >
> > This patch is based on top of the i_version rework that I'm flogging
> > upstream. It's just a cleanup of some nastiness I noticed while in there.
> >
> > This code uses the i_ctime and i_version fields to each store half of
> > a refcount. I suspect it was done this way long ago when the i_version
>
> Way long ago == 2017-06-22 :)
>
(cc'ing Tahsin)
Hah, ok. I was thinking this was legacy code, but I guess not! I should
have probably done some git archaeology first.
> The new 64k xattr value feature in ext4 uses hidden inodes to store attr
> values that don't fit in a single block. Since the inode can be shared
> by multiple xattr keys and isn't exported via NFS (I hope...), they use
> a 64-bit refcount mashed into i_ctime and i_version. That's what this
> gobbledygook is for.
>
> https://ext4.wiki.kernel.org/index.php/Ext4_Disk_Layout#Large_Extended_Attribute_Values
>
> --D
>
Ahh, many thanks...
My main question was: why split the refcount across fields like this? If
it's necessary now for backward compatibility then so be it, but it's
weird and not 100% clear why it's being done that way.
> > field was a 32 bits, and was never changed when the field was converted
> > to a 64 bit value.
> >
> > Change the code to just store the refcount in the i_version field rather
> > than splitting it across both fields.
> >
> > Cc: David Howells <dhowells@redhat.com>
> > Signed-off-by: Jeff Layton <jlayton@redhat.com>
> > ---
> > fs/ext4/xattr.c | 6 ++----
> > 1 file changed, 2 insertions(+), 4 deletions(-)
> >
> > diff --git a/fs/ext4/xattr.c b/fs/ext4/xattr.c
> > index 63656dbafdc4..6ea78dd367ca 100644
> > --- a/fs/ext4/xattr.c
> > +++ b/fs/ext4/xattr.c
> > @@ -294,14 +294,12 @@ ext4_xattr_inode_hash(struct ext4_sb_info *sbi, const void *buffer, size_t size)
> >
> > static u64 ext4_xattr_inode_get_ref(struct inode *ea_inode)
> > {
> > - return ((u64)ea_inode->i_ctime.tv_sec << 32) |
> > - (u32) inode_peek_iversion_raw(ea_inode);
> > + return inode_peek_iversion_raw(ea_inode);
> > }
> >
> > static void ext4_xattr_inode_set_ref(struct inode *ea_inode, u64 ref_count)
> > {
> > - ea_inode->i_ctime.tv_sec = (u32)(ref_count >> 32);
> > - inode_set_iversion_raw(ea_inode, ref_count & 0xffffffff);
> > + inode_set_iversion_raw(ea_inode, ref_count);
> > }
> >
> > static u32 ext4_xattr_inode_get_hash(struct inode *ea_inode)
> > --
> > 2.14.3
> >
--
Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2018-01-09 19:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 14:47 [RFC PATCH] ext4: don't split xattr inode refcounts across i_ctime and i_version fields Jeff Layton
2018-01-09 18:52 ` Darrick J. Wong
2018-01-09 19:05 ` Jeff Layton [this message]
2018-01-11 18:39 ` Theodore Ts'o
2018-01-11 20:09 ` Jeff Layton
2018-01-11 22:41 ` Theodore Ts'o
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=1515524731.3571.16.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=adilger.kernel@dilger.ca \
--cc=darrick.wong@oracle.com \
--cc=dhowells@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tahsin@google.com \
--cc=tytso@mit.edu \
/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