linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ju Hyung Park <qkrwngud825@gmail.com>
To: Chao Yu <yuchao0@huawei.com>
Cc: Jaegeuk Kim <jaegeuk@kernel.org>,
	linux-kernel@vger.kernel.org,
	linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix to do sanity with enabled features in image
Date: Tue, 30 Apr 2019 05:54:02 +0900	[thread overview]
Message-ID: <CAD14+f2nDurQ2mTp-temk92zhWQkKNaBA8CwpWJhOZEmzLw=VA@mail.gmail.com> (raw)
In-Reply-To: <20190424094850.118323-1-yuchao0@huawei.com>

Hi Chao and Jaegeuk,

On Wed, Apr 24, 2019 at 6:49 PM Chao Yu <yuchao0@huawei.com> wrote:
>
> This patch fixes to do sanity with enabled features in image, if
> there are features kernel can not recognize, just fail the mount.
>

Surprised to see that this wasn't implemented yet.
I was actually about to suggest this method to prevent mounting of the
new extended bitmap layout images altogether for older kernels(by
renaming the new, fixed layout to v2 or something), but looks like
that isn't an option. :(

Also, something similar should be also done with fsck, if not already.
The results from using older fsck with images with newer features
would be disastrous.

I'm still very busy currently with my other projects.
Sorry for the delays in testing new patchsets for layout fixes.

And I apologize in advance in case I miss the Linux 5.2 merge window
deadline, but I'd like to see it being fixed properly before shipping
those patches to production.

> +       /* check whether kernel supports all features */
> +       if (le32_to_cpu(raw_super->feature) & (~F2FS_ALL_FEATURES)) {
> +               f2fs_msg(sb, KERN_INFO,
> +                       "Unsupported feature:%u: supported:%u",
> +                       le32_to_cpu(raw_super->feature),
> +                       F2FS_ALL_FEATURES);
> +               return 1;
> +       }

This should probably be a KERN_ERR instead of KERN_INFO.

Thanks.

      parent reply	other threads:[~2019-04-29 20:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24  9:48 [PATCH] f2fs: fix to do sanity with enabled features in image Chao Yu
2019-04-28 13:38 ` Jaegeuk Kim
2019-04-29 13:57   ` Chao Yu
2019-05-01  3:22     ` Jaegeuk Kim
2019-05-05  2:51       ` Chao Yu
2019-05-09  1:15         ` [f2fs-dev] " Chao Yu
2019-07-16 10:02           ` Chao Yu
2019-07-23  1:35             ` Jaegeuk Kim
2019-07-23  7:01               ` Chao Yu
2019-07-29  5:47                 ` Jaegeuk Kim
2019-07-29  7:09                   ` Chao Yu
2019-04-29 20:54 ` Ju Hyung Park [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='CAD14+f2nDurQ2mTp-temk92zhWQkKNaBA8CwpWJhOZEmzLw=VA@mail.gmail.com' \
    --to=qkrwngud825@gmail.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuchao0@huawei.com \
    /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).