Re: [PATCH 00/20] DRBD 9 rework
Jens Axboe <[email protected]> Wed, 8 Apr 2026 06:58:58 -0600
| Newsgroups | dev.linux.lists.drbd-dev,org.kernel.vger.linux-block,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 4/7/26 11:17 PM, Christoph Hellwig wrote: > On Thu, Apr 02, 2026 at 07:30:35PM -0600, Jens Axboe wrote: >> On 3/27/26 4:38 PM, Christoph Böhmwalder wrote: >>> As discussed (context: [0]), here is the first version of our DRBD 9 >>> rework series, intended for for-next via for-7.1/drbd. >> >> Will you fixup the kerneldoc (nits) and the assigned-but-not-read >> issues and send out a new version? Also looks this series doesn't >> actually apply to for-7.1/block, patch 12 fails. > > Looks like all this went in without any review? Since when have we > started these grand replacements anyway, as they are known to cause > bugs and regressions? See the previous discussion, the goal is to sync the two drbd code bases. It's followed the "usual" pattern of the in-kernel driver being neglected and development and users pushed to the out-of-tree one, which is highly annoying. As per the previous thread, the intent is not to push to to mainline right now, but rather give it -next exposure without running into conflicts between the trees. for-7.x/drbd will be rebased as needed, and it's only in for-next for the stated reason. -- Jens Axboe