public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Hauke Mehrtens <hauke@hauke-m.de>
Cc: dedekind1@gmail.com, adrian.hunter@intel.com,
	linux-mtd@lists.infradead.org
Subject: Re: [PATCH] ubifs: Add option to create UBI FS version 4 on empty UBI volume
Date: Sun, 11 Mar 2018 20:25:51 +0100	[thread overview]
Message-ID: <6098386.P4OGBmHZAp@blindfold> (raw)
In-Reply-To: <20180311160451.26833-1-hauke@hauke-m.de>

Hauke,

Am Sonntag, 11. März 2018, 17:04:51 CET schrieb Hauke Mehrtens:
> Instead of creating an ubifs file system with format version 5 by
> default on empty UBI volumes add a compile option to create an older ubi
> with file system format version 4 instated. This allows it to be mount
> as a volume on kernel versions < 4.10, which does not support format
> version 5.
> We saw that some people can not access their older data when they
> downgraded from kernel 4.14 to kernel 4.9 to prevent this this option
> would help.

I agree, we should address this.

> Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
> ---
>  fs/ubifs/Kconfig | 13 +++++++++++++
>  fs/ubifs/sb.c    |  6 ++++++
>  2 files changed, 19 insertions(+)
> 
> diff --git a/fs/ubifs/Kconfig b/fs/ubifs/Kconfig
> index 83a961bf7280..a1426b865726 100644
> --- a/fs/ubifs/Kconfig
> +++ b/fs/ubifs/Kconfig
> @@ -74,3 +74,16 @@ config UBIFS_FS_SECURITY
>  	  the extended attribute support in advance.
> 
>  	  If you are not using a security module, say N.
> +
> +config UBIFS_FS_FORMAT4

A new config option is IMHO too coarse grained.
Sadly ubifs rejects unknown mount parameters, so having it as mount option is 
also not feasible since old kernels will refuse to mount then.

Please make it a module parameter. For example ubifs.default_version.

Thanks,
//richard

      reply	other threads:[~2018-03-11 19:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-11 16:04 [PATCH] ubifs: Add option to create UBI FS version 4 on empty UBI volume Hauke Mehrtens
2018-03-11 19:25 ` Richard Weinberger [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=6098386.P4OGBmHZAp@blindfold \
    --to=richard@nod.at \
    --cc=adrian.hunter@intel.com \
    --cc=dedekind1@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-mtd@lists.infradead.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