linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Theodore Tso <tytso@mit.edu>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext4: don't update s_rev_level if not required
Date: Mon, 14 Jan 2019 11:25:06 +0100	[thread overview]
Message-ID: <CAMuHMdX+vHL5ZTq-PJFLSy+wW6y5fgtJR30Tdy6BtabeMMVyjg@mail.gmail.com> (raw)
In-Reply-To: <1547339800-50257-1-git-send-email-adilger@dilger.ca>

Hi Andreas,

On Sun, Jan 13, 2019 at 1:36 AM Andreas Dilger <adilger@dilger.ca> wrote:
> Don't update the superblock s_rev_level during mount if it isn't
> actually necessary, only if superblock features are being set by
> the kernel.  This was originally added for ext3 since it always
> set the INCOMPAT_RECOVER and HAS_JOURNAL features during mount,
> but this is not needed since no journal mode was added to ext4.
>
> That will allow Geert to mount his 20-year-old ext2 rev 0.0 m68k
> filesystem, as a testament of the backward compatibility of ext4.
>
> Fixes: 0390131ba84f ("ext4: Allow ext4 to run without a journal")
> Signed-off-by: Andreas Dilger <adilger@dilger.ca>

Thanks for your patch!

> --- a/fs/ext4/ext4.h
> +++ b/fs/ext4/ext4.h
> @@ -1670,6 +1670,7 @@ static inline void ext4_clear_state_flags(struct ext4_inode_info *ei)
>  } \
>  static inline void ext4_set_feature_##name(struct super_block *sb) \
>  { \
> +       ext4_update_dynamic_rev(sb); \

This doesn't compile, as ext4_update_dynamic_rev() is used before its
declaration:

In file included from fs/ext4/bitmap.c:12:0:
fs/ext4/ext4.h: In function ‘ext4_set_feature_dir_prealloc’:
fs/ext4/ext4.h:1673:2: error: implicit declaration of function
‘ext4_update_dynamic_rev’ [-Werror=implicit-function-declaration]
  ext4_update_dynamic_rev(sb); \
  ^
fs/ext4/ext4.h:1719:1: note: in expansion of macro ‘EXT4_FEATURE_COMPAT_FUNCS’
 EXT4_FEATURE_COMPAT_FUNCS(dir_prealloc,  DIR_PREALLOC)
 ^~~~~~~~~~~~~~~~~~~~~~~~~
fs/ext4/ext4.h: At top level:
fs/ext4/ext4.h:2678:13: warning: conflicting types for ‘ext4_update_dynamic_rev’
 extern void ext4_update_dynamic_rev(struct super_block *sb);
             ^~~~~~~~~~~~~~~~~~~~~~~
fs/ext4/ext4.h:1673:2: note: previous implicit declaration of
‘ext4_update_dynamic_rev’ was here
  ext4_update_dynamic_rev(sb); \
  ^
fs/ext4/ext4.h:1719:1: note: in expansion of macro ‘EXT4_FEATURE_COMPAT_FUNCS’
 EXT4_FEATURE_COMPAT_FUNCS(dir_prealloc,  DIR_PREALLOC)
 ^~~~~~~~~~~~~~~~~~~~~~~~~

Moving the declaration up fixes that.

Hence with that fixed:
Tested-by: Geert Uytterhoeven <geert@linux-m68k.org>

Thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2019-01-14 10:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-12  9:43 Preserving a rev 0.0 ext2 filesystem Geert Uytterhoeven
2019-01-13  0:20 ` Andreas Dilger
2019-01-14 10:23   ` Geert Uytterhoeven
2019-01-14 12:50     ` Jan Kara
2019-01-13  0:36 ` [PATCH] ext4: don't update s_rev_level if not required Andreas Dilger
2019-01-14 10:25   ` Geert Uytterhoeven [this message]
2019-02-15  2:10   ` Theodore Y. 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=CAMuHMdX+vHL5ZTq-PJFLSy+wW6y5fgtJR30Tdy6BtabeMMVyjg@mail.gmail.com \
    --to=geert@linux-m68k.org \
    --cc=adilger@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).