From: Qu Wenruo <wqu@suse.com>
To: Calvin Owens <calvin@wbinvd.org>, Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-kernel@vger.kernel.org, linux-btrfs@vger.kernel.org,
Daniel Vacek <neelx@suse.com>, David Sterba <dsterba@suse.com>,
Josef Bacik <josef@toxicpanda.com>, Chris Mason <clm@fb.com>
Subject: Re: [PATCH] btrfs: Accept and ignore compression level for lzo
Date: Fri, 22 Aug 2025 19:48:16 +0930 [thread overview]
Message-ID: <9bdb2726-de7b-4ef0-9ad5-7050d214a85f@suse.com> (raw)
In-Reply-To: <aKg4PcgUCvXblVCY@mozart.vkv.me>
在 2025/8/22 18:58, Calvin Owens 写道:
> On Friday 08/22 at 17:57 +0930, Qu Wenruo wrote:
>> 在 2025/8/22 17:15, Calvin Owens 写道:
>>> The compression level is meaningless for lzo, but before commit
>>> 3f093ccb95f30 ("btrfs: harden parsing of compression mount options"),
>>> it was silently ignored if passed.
>>
>> Since LZO doesn't support compression level, why providing a level parameter
>> in the first place?
>
> Interpreting "no level" as "level is always one" doesn't seem that
> unreasonable to me, especially since it has worked forever.
No means no, period.
>
>> I think it's time for those users to properly update their mount options.
>
> It's a user visable regression, and fixing it has zero possible
> downside. I think you should take my patch :)
I do not want to encourage such usage.
Sanity overrides "regression". If it shouldn't work in the first place,
it's not a regression.
>
> Thanks,
> Calvin
>
>>>
>>> After that commit, passing a level with lzo fails to mount:
>>>
>>> BTRFS error: unrecognized compression value lzo:1
>>>
>>> Restore the old behavior, in case any users were relying on it.
>>>
>>> Fixes: 3f093ccb95f30 ("btrfs: harden parsing of compression mount options")
>>> Signed-off-by: Calvin Owens <calvin@wbinvd.org>
>>> ---
>>> fs/btrfs/super.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/fs/btrfs/super.c b/fs/btrfs/super.c
>>> index a262b494a89f..7ee35038c7fb 100644
>>> --- a/fs/btrfs/super.c
>>> +++ b/fs/btrfs/super.c
>>> @@ -299,7 +299,7 @@ static int btrfs_parse_compress(struct btrfs_fs_context *ctx,
>>> btrfs_set_opt(ctx->mount_opt, COMPRESS);
>>> btrfs_clear_opt(ctx->mount_opt, NODATACOW);
>>> btrfs_clear_opt(ctx->mount_opt, NODATASUM);
>>> - } else if (btrfs_match_compress_type(string, "lzo", false)) {
>>> + } else if (btrfs_match_compress_type(string, "lzo", true)) {
>>> ctx->compress_type = BTRFS_COMPRESS_LZO;
>>> ctx->compress_level = 0;
>>> btrfs_set_opt(ctx->mount_opt, COMPRESS);
>>
>
next prev parent reply other threads:[~2025-08-22 10:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 7:45 Calvin Owens
2025-08-22 8:27 ` Qu Wenruo
2025-08-22 9:28 ` Calvin Owens
2025-08-22 10:18 ` Qu Wenruo [this message]
2025-08-22 18:45 ` David Sterba
2025-08-22 21:42 ` Calvin Owens
2025-08-22 10:20 ` Sun YangKai
2025-08-22 10:23 ` Qu Wenruo
2025-08-22 15:54 ` Calvin Owens
2025-08-22 18:57 ` David Sterba
2025-08-22 21:44 ` Qu Wenruo
2025-08-22 23:24 ` Calvin Owens
2025-08-22 23:39 ` Qu Wenruo
2025-08-24 15:58 ` Calvin Owens
2025-08-24 21:40 ` Qu Wenruo
2025-08-25 8:51 ` Daniel Vacek
2025-08-25 9:03 ` Qu Wenruo
2025-08-25 11:37 ` Filipe Manana
2025-08-22 18:42 ` Calvin Owens
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=9bdb2726-de7b-4ef0-9ad5-7050d214a85f@suse.com \
--to=wqu@suse.com \
--cc=calvin@wbinvd.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neelx@suse.com \
--cc=quwenruo.btrfs@gmx.com \
/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®