From: Jens Axboe <axboe@kernel.dk>
To: Philipp Reisner <philipp.reisner@linbit.com>,
Christoph Hellwig <hch@lst.de>
Cc: Lars Ellenberg <lars.ellenberg@linbit.com>,
drbd-dev@lists.linbit.com, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: state of drbd in mainline
Date: Tue, 29 Mar 2022 06:29:40 -0600 [thread overview]
Message-ID: <f9d89282-3a67-ad97-149f-52325e23607c@kernel.dk> (raw)
In-Reply-To: <CADGDV=U5jwe0CZ12174cMahfD_h-GsBswWaA1VOJbHaC1nsrUw@mail.gmail.com>
On 3/29/22 1:50 AM, Philipp Reisner wrote:
>> 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..
>>
>
> FYI, feature-wise the in-tree DRBD is frozen. Maintenance only. Users,
> seeking advanced
> features switch to the out-of-tree DRBD and use other means of communication:
> Github issues, linbit's community slack channel, last not least
> linbit's ticketing system.
>
> That is why you see virtually no activity.
I've been thinking the same thing. Even if most users are out-of-tree, you'd
still expect to see at least some reports on the list. A few followup
questions:
- Why aren't the drbd maintainers responding to posted patches? They seem
to simply be ignored, and I'm left to pickup the trivial ones that look
fine to me. In-kernel drbd appears largely unmaintained, and has been for
years.
- Even if out-of-band communication is used for in-kernel users of drbd,
that doesn't result in any patches or fixes that should go upstream?
- If there's zero activity for in-kernel drbd, all users are using the
out-of-tree version?
As far as I can tell, drbd upstream is stone cold dead, and has been for
years. Why shouldn't it just get removed? Is it just bait to get people
to use an out-of-tree version?
--
Jens Axboe
next prev parent reply other threads:[~2022-03-29 12:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 7:06 state of drbd in mainline Christoph Hellwig
2022-03-29 7:24 ` Philipp Reisner
[not found] ` <CADGDV=UgjZAbmAN-2bO1nyDvA=XCC9Lf2dxWHZ0BwxF12nnztQ@mail.gmail.com>
2022-03-29 7:32 ` Christoph Hellwig
2022-03-29 7:50 ` Philipp Reisner
2022-03-29 12:29 ` Jens Axboe [this message]
2022-03-29 15:44 ` Philipp Reisner
2022-03-29 15:52 ` Jens Axboe
2022-03-30 15:23 ` Philipp Reisner
2022-03-30 18:06 ` Mike Snitzer
2022-03-30 18:24 ` Jens Axboe
2022-03-30 19:31 ` [Drbd-dev] " Kiselev, Oleg
2022-03-30 20:21 ` Jens Axboe
2022-03-29 20:01 ` Wolfgang Walter
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=f9d89282-3a67-ad97-149f-52325e23607c@kernel.dk \
--to=axboe@kernel.dk \
--cc=drbd-dev@lists.linbit.com \
--cc=hch@lst.de \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=philipp.reisner@linbit.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