From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-erofs@lists.ozlabs.org, LKML <linux-kernel@vger.kernel.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH v2 1/4] erofs: add file-backed mount support
Date: Wed, 2 Oct 2024 19:25:12 +0800 [thread overview]
Message-ID: <7cde8511-9d56-4366-aac4-29dfbd8c76b1@linux.alibaba.com> (raw)
In-Reply-To: <20241002-burgfrieden-nahen-079f64e243ad@brauner>
On 2024/10/2 14:12, Christian Brauner wrote:
> On Mon, Sep 30, 2024 at 04:18:19PM GMT, Jan Kara wrote:
..
>>>>
>>>> diff --git a/fs/erofs/Kconfig b/fs/erofs/Kconfig
>>>> index 7dcdce660cac..1428d0530e1c 100644
>>>> --- a/fs/erofs/Kconfig
>>>> +++ b/fs/erofs/Kconfig
>>>> @@ -74,6 +74,23 @@ config EROFS_FS_SECURITY
>>>>
>>>> If you are not using a security module, say N.
>>>>
>>>> +config EROFS_FS_BACKED_BY_FILE
>>>> + bool "File-backed EROFS filesystem support"
>>>> + depends on EROFS_FS
>>>> + default y
>>>
>>> I am a bit reluctant to have this default to y, without an ack from
>>> the VFS maintainers.
>>
>> Well, we generally let filesystems do whatever they decide to do unless it
>> is a affecting stability / security / maintainability of the whole system.
>> In this case I don't see anything that would be substantially different
>> than if we go through a loop device. So although the feature looks somewhat
>> unusual I don't see a reason to nack it or otherwise interfere with
>> whatever the fs maintainer wants to do. Are you concerned about a
>> particular problem?
>
> I see no reason to nak it either.
Thanks all for taking time on writing down these!
Unfortunately, fanotify pre-content hooks was't landed in 6.12 cycle
(which I think will be used in a lot of scenarios)..
I do hope it could be landed in the next cycle so I could clean up
the codebase then.
Thanks,
Gao Xiang
prev parent reply other threads:[~2024-10-02 11:30 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 3:28 Gao Xiang
2024-08-30 3:28 ` [PATCH v2 2/4] erofs: support unencoded inodes for fileio Gao Xiang
2024-08-31 0:19 ` Sandeep Dhavale
2024-08-31 2:54 ` Gao Xiang
2024-08-31 4:25 ` Sandeep Dhavale
2024-08-31 7:54 ` Gao Xiang
2024-09-01 20:47 ` Sandeep Dhavale
2024-09-04 6:56 ` Gao Xiang
2024-09-05 9:01 ` Chao Yu
2024-09-05 9:13 ` Gao Xiang
2024-08-30 3:28 ` [PATCH v2 3/4] erofs: support compressed " Gao Xiang
2024-09-01 20:47 ` Sandeep Dhavale
2024-09-05 9:01 ` Chao Yu
2024-09-05 9:14 ` Gao Xiang
2024-09-05 9:46 ` Chao Yu
2024-08-30 3:28 ` [PATCH v2 4/4] erofs: mark experimental fscache backend deprecated Gao Xiang
2024-09-01 20:48 ` Sandeep Dhavale
2024-09-05 9:03 ` Chao Yu
2024-08-31 0:30 ` [PATCH v2 1/4] erofs: add file-backed mount support Sandeep Dhavale
2024-08-31 3:00 ` Gao Xiang
2024-09-01 20:46 ` Sandeep Dhavale
2024-09-05 8:22 ` Chao Yu
2024-09-05 9:30 ` [PATCH v3 2/4] erofs: support unencoded inodes for fileio Gao Xiang
2024-09-05 9:44 ` Chao Yu
2024-09-24 9:21 ` [PATCH v2 1/4] erofs: add file-backed mount support Geert Uytterhoeven
2024-09-24 9:29 ` Gao Xiang
2024-09-30 14:18 ` Jan Kara
2024-09-30 14:22 ` Geert Uytterhoeven
2024-10-02 6:12 ` Christian Brauner
2024-10-02 11:25 ` Gao Xiang [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=7cde8511-9d56-4366-aac4-29dfbd8c76b1@linux.alibaba.com \
--to=hsiangkao@linux.alibaba.com \
--cc=brauner@kernel.org \
--cc=geert@linux-m68k.org \
--cc=jack@suse.cz \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®