linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: dsterba@suse.cz
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 9/9] btrfs: enable experimental bs > ps support
Date: Mon, 22 Sep 2025 20:21:53 +0930	[thread overview]
Message-ID: <7598271d-18c8-41d6-80c8-87d645882a05@suse.com> (raw)
In-Reply-To: <20250922104224.GN5333@twin.jikos.cz>



在 2025/9/22 20:12, David Sterba 写道:
> On Mon, Sep 22, 2025 at 07:57:40PM +0930, Qu Wenruo wrote:
>>
>>
>> 在 2025/9/22 19:51, David Sterba 写道:
>>> On Mon, Sep 22, 2025 at 08:10:51AM +0930, Qu Wenruo wrote:
>>>> +	if (fs_info->sectorsize > PAGE_SIZE) {
>>>> +		ret = -ENOTTY;
>>>
>>> I did a minor fixup of the error code to -EOPNOTSUPP,
>>
>> Please don't.
>>
>> The error code is to co-operate with btrfs-progs, which doesn't check
>> EOPNOTSUPP.
> 
> Well then we should fix btrfs-progs because this breaks the informal
> error code protocol

It's the egg-and-chicken compatibility problem.

> 
>> And the encoded receive only falls back to regular one when got a ENOTTY.
> 
> But this is still only for the bs > ps case, right? So it may be
> temporarily broken until we sync the kernel code and progs but would not
> otherwise break the other cases.

I'd prefer to remove those exceptions when the sub-block handling is 
added, and keep the compatibility so that I don't need to run tests with 
a special version of btrfs-progs.

The fix of btrfs-progs will take time to reach end users.

And that full bs > ps support will not be that far away, considering how 
many cycles (in fact, just two cycles, some preparation in v6.17, then 
v6.18) we spent to reach the current state (full fstests run, 6 known 
failures, all in btrfs group), the removal of those checks should be 
pretty close.

Especially I already have an idea on how to support sub-block checksum 
handling.

Thanks,
Qu

  reply	other threads:[~2025-09-22 10:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-21 22:40 [PATCH v2 0/9] btrfs: initial bs > ps support Qu Wenruo
2025-09-21 22:40 ` [PATCH v2 1/9] btrfs: fix the incorrect @max_bytes value for find_lock_delalloc_range() Qu Wenruo
2025-09-21 22:46   ` Qu Wenruo
2025-09-21 22:40 ` [PATCH v2 2/9] btrfs: prepare compression folio alloc/free for bs > ps cases Qu Wenruo
2025-09-21 22:40 ` [PATCH v2 3/9] btrfs: prepare zstd to support " Qu Wenruo
2025-09-21 22:40 ` [PATCH v2 4/9] btrfs: prepare lzo " Qu Wenruo
2025-09-21 22:40 ` [PATCH v2 5/9] btrfs: prepare zlib " Qu Wenruo
2025-09-21 22:40 ` [PATCH v2 6/9] btrfs: prepare scrub " Qu Wenruo
2025-09-21 22:40 ` [PATCH v2 7/9] btrfs: fix symbolic link reading when bs > ps Qu Wenruo
2025-09-21 22:40 ` [PATCH v2 8/9] btrfs: add extra ASSERT()s to catch unaligned bios Qu Wenruo
2025-09-21 22:40 ` [PATCH v2 9/9] btrfs: enable experimental bs > ps support Qu Wenruo
2025-09-22 10:21   ` David Sterba
2025-09-22 10:27     ` Qu Wenruo
2025-09-22 10:42       ` David Sterba
2025-09-22 10:51         ` Qu Wenruo [this message]
2025-09-22  9:12 ` [PATCH v2 0/9] btrfs: initial " David Sterba

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=7598271d-18c8-41d6-80c8-87d645882a05@suse.com \
    --to=wqu@suse.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).