linux-f2fs-devel.lists.sourceforge.net archive mirror
 help / color / mirror / Atom feed
From: Patrick Doyle <wpdster@gmail.com>
To: yuchao0@huawei.com
Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: Are there limitation to the number of named pipes/FIFO's supported by F2FS?
Date: Thu, 6 Sep 2018 09:14:05 -0400	[thread overview]
Message-ID: <CAF_dkJDCi4Jb0dZ1rNo97ru7idTucxLy3DXUDgBjs8rxumYLHQ@mail.gmail.com> (raw)
In-Reply-To: <8778e118-1b5f-8a11-7cd7-4fe663c9da3a@huawei.com>

On Wed, Sep 5, 2018 at 9:51 PM Chao Yu <yuchao0@huawei.com> wrote:
> On 2018/9/6 0:11, Patrick Doyle wrote:
> > I think it would also be worthwhile also to submit patches to the LTS
> > kernels that would check for an inhibit mounting of F2FS filesystems
> > that have features unsupported by the kernel.  If that is already in
> > place, then I shouldn't have been able to mount my f2fs partition if
> > it had the "Large nat bitmap feature" enabled.
>
> Agreed, but I tracked LTS version in Linux upstream and kernel version in
> LTS of ubuntu:
...
> And not sure that other distribution of linux will use above version
> kernel, in order to fix all version, we have to:
>
> 1. find all linux distributions LTS kernel version.
> 2. make and send the right fixing patch to all distribution's kernel
> maintainers.
>
> Thoughts?
My original recommendation was to patch the F2FS kernel driver so that
it refuses to mount filesystems with incompatible, or unknown,
options.  (I freely admit, I don't know what's involved in such a
patch, but I feel that there should be some way to validate the
features and format of the superblock to ensure that they are
compatible with the features expected by that particular version of
the kernel driver.)  I would expect that you should only need to
submit that patch against the kernel LTS versions (listed at
kernel.org) and let the distribution maintainers take it from there.

--wpd

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

  reply	other threads:[~2018-09-06 13:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 16:28 Are there limitation to the number of named pipes/FIFO's supported by F2FS? Patrick Doyle
2018-09-05  1:55 ` Chao Yu
2018-09-05  4:12   ` Jaegeuk Kim
2018-09-05 13:35     ` Patrick Doyle
2018-09-05 15:57       ` Chao Yu
2018-09-05 16:11         ` Patrick Doyle
2018-09-05 17:30           ` Jaegeuk Kim
2018-09-06  1:51           ` Chao Yu
2018-09-06 13:14             ` Patrick Doyle [this message]
2018-09-06 13:29               ` Chao Yu
2018-09-06  2:03           ` Chao Yu
2018-09-06 12:44             ` Chao Yu
2018-09-06 13:31             ` Patrick Doyle
2018-09-05 17:16         ` Jaegeuk Kim

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=CAF_dkJDCi4Jb0dZ1rNo97ru7idTucxLy3DXUDgBjs8rxumYLHQ@mail.gmail.com \
    --to=wpdster@gmail.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --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).