From: Chao Yu <chao@kernel.org>
To: Hengyu Liang <hengyul@cs.unc.edu>, jaegeuk@kernel.org
Cc: chao@kernel.org, linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, daehojeong@google.com,
joannechien@google.com, stable@vger.kernel.org
Subject: Re: [PATCH] f2fs: allow empty strings for journaled quota options
Date: Sun, 11 Oct 2026 18:38:27 +0800 [thread overview]
Message-ID: <2682e98c-826a-4fc5-8184-bf9b8a20abb7@kernel.org> (raw)
In-Reply-To: <20261010165750.509939-1-hengyul@cs.unc.edu>
On 10/11/26 00:57, Hengyu Liang wrote:
> Commit 2a3db1e02ce0 ("f2fs: allow empty mount string for
> Opt_usr|grp|projjquota") added support for passing usrjquota,
> grpjquota and prjjquota as flags to disable journaled quotas.
>
> However, it also replaced fsparam_string_empty() with fsparam_string(),
> which rejects an empty string. As of now, mount(2) and
> fsconfig(FSCONFIG_SET_STRING) reject usrjquota=, grpjquota= and
> prjjquota= with EINVAL, although these forms are still documented in
> Documentation/filesystems/f2fs.rst.
>
> The issue can be reproduced on an F2FS device with:
>
> mount -t f2fs -o usrjquota= /dev/loop5 /mnt/f
>
> Before this commit, the command succeeds. Afterwards, it fails with
> EINVAL and logs "f2fs: Bad value for 'usrjquota'".
> The same failure occurs when remounting to clear a quota file name.
>
> This patch will restore fsparam_string_empty() for the three options
> while retaining the flag entries, so both forms are accepted.
>
> Fixes: 2a3db1e02ce0 ("f2fs: allow empty mount string for Opt_usr|grp|projjquota")
> Cc: stable@vger.kernel.org # 7.1+
> Signed-off-by: Hengyu Liang <hengyul@cs.unc.edu>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
prev parent reply other threads:[~2026-10-11 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 16:57 Hengyu Liang
2026-10-11 10:38 ` 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=2682e98c-826a-4fc5-8184-bf9b8a20abb7@kernel.org \
--to=chao@kernel.org \
--cc=daehojeong@google.com \
--cc=hengyul@cs.unc.edu \
--cc=jaegeuk@kernel.org \
--cc=joannechien@google.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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®