From: Eric Biggers <ebiggers@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>
Cc: linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com,
Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: support dynamic include/exclude for device aliasing
Date: Sat, 6 Jun 2026 00:32:40 +0000 [thread overview]
Message-ID: <20260606003240.GB2312230@google.com> (raw)
In-Reply-To: <CACOAw_xrMij0pXjFkS4gY0kt5buvfZ0gmzbcP+zx4-ox7n+_3Q@mail.gmail.com>
On Fri, Jun 05, 2026 at 04:51:34PM -0700, Daeho Jeong wrote:
> - Access Control: The F2FS_IOC_EXCLUDE_DEV_ALIAS ioctl strictly
> requires CAP_SYS_ADMIN. Unprivileged users cannot trigger this
> transition.
No, it doesn't.
How much of this been reviewed by a human?
- Eric
WARNING: multiple messages have this Message-ID (diff)
From: Eric Biggers via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: Daeho Jeong <daeho43@gmail.com>
Cc: Daeho Jeong <daehojeong@google.com>,
kernel-team@android.com, linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH v2] f2fs: support dynamic include/exclude for device aliasing
Date: Sat, 6 Jun 2026 00:32:40 +0000 [thread overview]
Message-ID: <20260606003240.GB2312230@google.com> (raw)
In-Reply-To: <CACOAw_xrMij0pXjFkS4gY0kt5buvfZ0gmzbcP+zx4-ox7n+_3Q@mail.gmail.com>
On Fri, Jun 05, 2026 at 04:51:34PM -0700, Daeho Jeong wrote:
> - Access Control: The F2FS_IOC_EXCLUDE_DEV_ALIAS ioctl strictly
> requires CAP_SYS_ADMIN. Unprivileged users cannot trigger this
> transition.
No, it doesn't.
How much of this been reviewed by a human?
- Eric
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2026-06-06 0:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 21:25 [PATCH v2] f2fs: support dynamic include/exclude for device aliasing Daeho Jeong
2026-06-05 21:25 ` [f2fs-dev] " Daeho Jeong
2026-06-05 22:10 ` Eric Biggers via Linux-f2fs-devel
2026-06-05 22:10 ` Eric Biggers
2026-06-05 23:51 ` Daeho Jeong
2026-06-05 23:51 ` Daeho Jeong
2026-06-06 0:32 ` Eric Biggers [this message]
2026-06-06 0:32 ` Eric Biggers via Linux-f2fs-devel
2026-06-06 1:04 ` Daeho Jeong
2026-06-06 1:04 ` Daeho Jeong
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=20260606003240.GB2312230@google.com \
--to=ebiggers@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.