From: Theodore Ts'o <tytso@mit.edu>
To: Jeff Layton <jlayton@kernel.org>
Cc: "Darrick J. Wong" <darrick.wong@oracle.com>,
adilger.kernel@dilger.ca, 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: Thu, 11 Jan 2018 17:41:50 -0500 [thread overview]
Message-ID: <20180111224150.GK19241@thunk.org> (raw)
In-Reply-To: <1515701343.3788.19.camel@kernel.org>
On Thu, Jan 11, 2018 at 03:09:03PM -0500, Jeff Layton wrote:
>
> Wouldn't it have made more sense to just store it all in i_version field
> (like this patch makes it do)? If this breaks backward compatibility
> though, then I'm fine with just dropping the patch.
Yes, that part is there for compatibility for the deployed base
(Lustre Servers).
- Ted
prev parent reply other threads:[~2018-01-11 22:41 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
2018-01-11 18:39 ` Theodore Ts'o
2018-01-11 20:09 ` Jeff Layton
2018-01-11 22:41 ` Theodore Ts'o [this message]
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=20180111224150.GK19241@thunk.org \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=darrick.wong@oracle.com \
--cc=dhowells@redhat.com \
--cc=jlayton@kernel.org \
--cc=linux-ext4@vger.kernel.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