From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chao Yu Subject: Re: Are there limitation to the number of named pipes/FIFO's supported by F2FS? Date: Thu, 6 Sep 2018 21:29:57 +0800 Message-ID: <73dd29bd-1686-e77b-89dd-58703debd395@kernel.org> References: <20180905041210.GB15147@jaegeuk-macbookpro.roam.corp.google.com> <8ffaeb7c-972e-f1d2-277d-0b02407f58ff@kernel.org> <8778e118-1b5f-8a11-7cd7-4fe663c9da3a@huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from [172.30.20.202] (helo=mx.sourceforge.net) by sfs-ml-2.v29.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) (envelope-from ) id 1fxuNL-0005VQ-2Z for linux-f2fs-devel@lists.sourceforge.net; Thu, 06 Sep 2018 13:31:11 +0000 Received: from mail.kernel.org ([198.145.29.99]) by sfi-mx-3.v28.lw.sourceforge.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.90_1) id 1fxuNG-00A8Hl-3L for linux-f2fs-devel@lists.sourceforge.net; Thu, 06 Sep 2018 13:31:10 +0000 In-Reply-To: Content-Language: en-US List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-f2fs-devel-bounces@lists.sourceforge.net To: Patrick Doyle , yuchao0@huawei.com Cc: jaegeuk@kernel.org, linux-f2fs-devel@lists.sourceforge.net On 2018/9/6 21:14, Patrick Doyle wrote: > On Wed, Sep 5, 2018 at 9:51 PM Chao Yu 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 Below info is picked from kernel.org, you can see longterm version is 4.4/4.9/4.14 Linux Kernel Release Status KERNEL VERSION mainline: 4.19-rc2 stable: 4.18.6 stable: 4.17.19 [EOL] longterm: 4.14.68 longterm: 4.9.125 longterm: 4.4.154 > kernel.org) and let the distribution maintainers take it from there. But, for example, ubuntu use below version kernel as underlying OS 16.04 4.13 18.04 4.15 So you can see, it's not possible to let distribution maintainers take related patch from kernel.org, since they are maintaining different LTS kernel version. Thanks, > > --wpd > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot