From: Eric Biggers <ebiggers3@gmail.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: remove timebomb in ext4_decode_extra_time()
Date: Tue, 27 Jun 2017 11:35:43 -0700 [thread overview]
Message-ID: <20170627183543.GA39374@gmail.com> (raw)
In-Reply-To: <20170627140326.GA25210@lst.de>
On Tue, Jun 27, 2017 at 04:03:26PM +0200, Christoph Hellwig wrote:
> ping?
>
> On Wed, Jun 14, 2017 at 01:22:38PM +0200, Christoph Hellwig wrote:
> > Changing behavior based on the version code is a timebomb waiting to
> > happen, and not easily bisectable. Drop it and leave any removal
> > to explicit developer action. (And I don't think file system
> > should _ever_ remove backwards compatibility that has no explicit
> > flag, but I'll leave that to the ext4 folks).
> >
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > ---
> > fs/ext4/ext4.h | 12 +++---------
> > 1 file changed, 3 insertions(+), 9 deletions(-)
> >
> > diff --git a/fs/ext4/ext4.h b/fs/ext4/ext4.h
> > index 32191548abed..d35749e7cf9f 100644
> > --- a/fs/ext4/ext4.h
> > +++ b/fs/ext4/ext4.h
> > @@ -838,21 +838,15 @@ static inline void ext4_decode_extra_time(struct timespec *time, __le32 extra)
> > {
> > if (unlikely(sizeof(time->tv_sec) > 4 &&
> > (extra & cpu_to_le32(EXT4_EPOCH_MASK)))) {
> > -#if LINUX_VERSION_CODE < KERNEL_VERSION(4,20,0)
> > +
> > /* Handle legacy encoding of pre-1970 dates with epoch
> > - * bits 1,1. We assume that by kernel version 4.20,
> > - * everyone will have run fsck over the affected
> > - * filesystems to correct the problem. (This
> > - * backwards compatibility may be removed before this
> > - * time, at the discretion of the ext4 developers.)
> > + * bits 1,1. (This backwards compatibility may be removed
> > + * at the discretion of the ext4 developers.)
> > */
> > u64 extra_bits = le32_to_cpu(extra) & EXT4_EPOCH_MASK;
> > if (extra_bits == 3 && ((time->tv_sec) & 0x80000000) != 0)
> > extra_bits = 0;
> > time->tv_sec += extra_bits << 32;
> > -#else
> > - time->tv_sec += (u64)(le32_to_cpu(extra) & EXT4_EPOCH_MASK) << 32;
> > -#endif
> > }
> > time->tv_nsec = (le32_to_cpu(extra) & EXT4_NSEC_MASK) >> EXT4_EPOCH_BITS;
> > }
Looks good --- I agree that timebombs are a very bad idea.
Reviewed-by: Eric Biggers <ebiggers@google.com>
- Eric
next prev parent reply other threads:[~2017-06-27 18:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 11:22 [PATCH] ext4: remove timebomb in ext4_decode_extra_time() Christoph Hellwig
2017-06-27 14:03 ` Christoph Hellwig
2017-06-27 18:35 ` Eric Biggers [this message]
2017-07-18 16:18 ` Christoph Hellwig
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=20170627183543.GA39374@gmail.com \
--to=ebiggers3@gmail.com \
--cc=hch@lst.de \
--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;
as well as URLs for NNTP newsgroup(s).