From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: chao@kernel.org, Daeho Jeong <daehojeong@google.com>,
stable@vger.kernel.org, Wenjie Qi <qiwenjie@xiaomi.com>
Subject: Re: [f2fs-dev] [PATCH] mkfs.f2fs: enforce alias_filename to match device name
Date: Mon, 7 Sep 2026 02:20:33 +0000 [thread overview]
Message-ID: <d2e1b8bd-f575-4f83-a64e-2afef5f1ce2c@kernel.org> (raw)
In-Reply-To: <20260826181121.3825702-1-daeho43@gmail.com>
On 8/26/26 18:11, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> The kernel expects the device alias file in the root directory to match
> the device basename (strrchr(path, '/') + 1) to identify the target device
> both during mount in f2fs_restore_device_alias() and during reserve in
> f2fs_ioc_reserve_dev_alias().
>
> If a custom alias filename that differs from the device name is used,
> the kernel fails to match the alias file at mount time (leaving
> FDEV(i).has_alias unset and allowing pinned files to allocate in that
> range) and subsequently fails to reserve the device range when requested.
>
> Enforce that if an alias filename is specified, it must match the device
> name. Also allow specifying just '-c <device>@' as a shorthand so users
> do not have to redundantly type the device basename twice.
Do we need to add a sanity check in kernel side as well, show warning info
if device name doesn't match device alias file name?
>
> Reported-by: Wenjie Qi <qiwenjie@xiaomi.com>
> Fixes: 8cc4e257ec20 ("mkfs.f2fs: add device aliasing feature")
> Cc: stable@vger.kernel.org
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2026-09-07 2:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 18:11 Daeho Jeong
2026-09-07 2:20 ` Chao Yu [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=d2e1b8bd-f575-4f83-a64e-2afef5f1ce2c@kernel.org \
--to=chao@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 \
--cc=qiwenjie@xiaomi.com \
--cc=stable@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 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®