From: Chao Yu via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Jaegeuk Kim <jaegeuk@kernel.org>, linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] mkfs.f2fs: remove IMMUTABLE bit
Date: Mon, 18 Nov 2024 09:24:45 +0800 [thread overview]
Message-ID: <91143593-ed9b-45ae-a63f-643ac6daa889@kernel.org> (raw)
In-Reply-To: <20241111030456.2572093-1-jaegeuk@kernel.org>
On 2024/11/11 11:04, Jaegeuk Kim via Linux-f2fs-devel wrote:
> The immutable bit disallows selinux permission which gives no way to clear it.
>
> Fixes: 8cc4e257ec20 ("mkfs.f2fs: add device aliasing feature")
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2024-11-18 1:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 3:04 [f2fs-dev] [PATCH] mkfs.f2fs: remove IMMUTABLE bit Jaegeuk Kim via Linux-f2fs-devel
2024-11-11 17:07 ` Daeho Jeong
2024-11-18 1:24 ` Chao Yu via Linux-f2fs-devel [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=91143593-ed9b-45ae-a63f-643ac6daa889@kernel.org \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.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;
as well as URLs for NNTP newsgroup(s).