linux-kernel - Re: [PATCH v3 0/4] btrfs: RAID stripe tree updates

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <25ad10f2-14a9-497f-acc4-7b8b37981582@wdc.com>
Date:   Wed, 4 Oct 2023 08:36:50 +0000
From:   Johannes Thumshirn <Johannes.Thumshirn@....com>
To:     Qu Wenruo <quwenruo.btrfs@....com>, Chris Mason <clm@...com>,
        Josef Bacik <josef@...icpanda.com>,
        David Sterba <dsterba@...e.com>
CC:     Qu Wenru <wqu@...e.com>, Damien Le Moal <dlemoal@...nel.org>,
        Naohiro Aota <Naohiro.Aota@....com>,
        "linux-btrfs@...r.kernel.org" <linux-btrfs@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 0/4] btrfs: RAID stripe tree updates

On 04.10.23 10:26, Qu Wenruo wrote:
> 
> 
> On 2023/10/4 18:26, Johannes Thumshirn wrote:
>> This batch of RST updates contains the on-disk format changes Qu
>> suggested. It drastically simplifies the write and path, especially for
>> RAID10.
>>
>> Instead of recording all strides of a striped RAID into one stripe tree
>> entry, we create multiple entries per stride. This allows us to remove the
>> length in the stride as we can use the length from the key. Using this
>> method RAID10 becomes RAID1 and RAID0 becomes single from the point of
>> view of the stripe tree.
> 
> Great the idea can simplify the code.
> So I'm very glad I can provide some help on RST.
> 
> Although one concern is about the compatibility, but I guess since rst
> is still covered under experimental flags for progs, we can more or less
> ignore the compatibility for now?

They're only in misc-next by now so I hope we can.

> The other concern is, how would those patches be merged, would David
> just fold them, and we can check the misc-next, or there would be
> another branch for us to view the code?

I was under the impression, David is going to fold them in.