| 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
| ||
|
Message-ID: <ff5bc3eb8fa27845cefa2f96e5241972@stwm.de>
Date: Tue, 29 Mar 2022 22:01:15 +0200
From: Wolfgang Walter <linux@...m.de>
To: Christoph Hellwig <hch@....de>
Cc: Philipp Reisner <philipp.reisner@...bit.com>,
Jens Axboe <axboe@...nel.dk>, linux-kernel@...r.kernel.org,
linux-block@...r.kernel.org,
Lars Ellenberg <lars.ellenberg@...bit.com>,
drbd-dev@...ts.linbit.com
Subject: Re: [Drbd-dev] state of drbd in mainline
Am 2022-03-29 09:32, schrieb Christoph Hellwig:
> On Tue, Mar 29, 2022 at 09:22:26AM +0200, Philipp Reisner wrote:
>> Hi Christoph,
>>
>> what do you expect for the DRBD changes? Usually, they fall into the
>> category: yes, obviously. When you are changing the block layer in
>> this
>> way, then that is necessary for the in-tree DRBD code.
>>
>> Regarding users: Yes, there are users of the in-tree DRBD code. Very
>> big
>> corporations. And, yes, we see pressure building up that we get our
>> act
>> together and re-sync the in-tree DRBD with the out-of tree DRBD.
>
> The complete lack of bug reports and maintainer interaction usually
> suggests low to no use and heavy bitrot. If that is not the case
> here that's fine, just asking..
>
> _______________________________________________
> drbd-dev mailing list
> drbd-dev@...ts.linbit.com
> https://lists.linbit.com/mailman/listinfo/drbd-dev
We use the in-tree DRBD with LTS (actually 5.15.32 and 5.4.188) and
depend on it. It just works. We never had any issues in the last 5
years.
Regards
--
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts
Powered by blists - more mailing lists