Received: by 2002:a05:6a10:2726:0:0:0:0 with SMTP id ib38csp2238598pxb; Wed, 30 Mar 2022 20:20:21 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy4AdIGbWpe96GgYLb+qZyP4jnTsOxWtsl3my1SQBMH0nL5uW++YMm1w3l9nKPDsomeBJef X-Received: by 2002:a63:e241:0:b0:375:9f87:eb1f with SMTP id y1-20020a63e241000000b003759f87eb1fmr9007837pgj.216.1648696820968; Wed, 30 Mar 2022 20:20:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1648696820; cv=none; d=google.com; s=arc-20160816; b=Kd75bPJkXpK9F2n0B0qt6F2f5WFUMdQxoM+EIoXUGJxIbJDwXg086znMdsUoMuSo/d mYoeUWuacDYF9MRN02Jhy56Rc6U7Co57/gv/ooL4BN+F8fxbUpJLUb0Q68vLPkLZq4VD bwOw5JsQmcqt37eaPoQ9avBZP4xpAm3N87XKQgSCKzXrf6Nb1C1Q9ZfuoSEI9PftEwF+ c6IXn6SEat4sq/7LRiDHLpHbr/t9dSCNjYKQ31/xjfGjeeLSf3mMmSgg/O2kpOR4G7LF CP1pSjIPbmXtbNw6wFML4KS28vfXGQpXsfDl2lfKkeF4l9A3stmBzifb+KMa89/gpElq chWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=BLYncbAZMOiJKAipKssMlulVwN4gsXJDU6wQcnVJrcI=; b=i7z8XE9Tm6aEX67FrcVvTEkTXrJKdSwOuxApV2F399lVDy69B2fAEhOPtanE9NOubk irP+r6SrPOIbal9UMdNuM08HQj0XVkafYYL5v1JyyrDmytWZHmVShNniCPhKTJhwF1F8 qrkSCbQVIKgSAPBnic19s2mFU9wnfQMvg5/asVZM2AqSTe6nDdJ6XL3lod8+57rAsBfq c4y88uu4kkosM1G3R8X9GwS/5egO+I01IOH/5l0VDtGn2oSW/0dzbwXoa+6bBvOStjsV lTtd+c8RHL9uAoUoAt/fZBAaZrmn2lKzC8sdI9rLPAJ8D9ztyoFmhvq0OeJtnKE6VYuK YcSA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linbit-com.20210112.gappssmtp.com header.s=20210112 header.b=ZXWqagMR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id lb2-20020a17090b4a4200b001bd14e01f1dsi2309624pjb.11.2022.03.30.20.20.20 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 30 Mar 2022 20:20:20 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@linbit-com.20210112.gappssmtp.com header.s=20210112 header.b=ZXWqagMR; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id AD4C6109A6C; Wed, 30 Mar 2022 19:51:36 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1348147AbiC3PZo (ORCPT + 99 others); Wed, 30 Mar 2022 11:25:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39218 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1348145AbiC3PZm (ORCPT ); Wed, 30 Mar 2022 11:25:42 -0400 Received: from mail-vk1-xa2d.google.com (mail-vk1-xa2d.google.com [IPv6:2607:f8b0:4864:20::a2d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 11CCF55BE9 for ; Wed, 30 Mar 2022 08:23:56 -0700 (PDT) Received: by mail-vk1-xa2d.google.com with SMTP id p143so11748685vkf.5 for ; Wed, 30 Mar 2022 08:23:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linbit-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BLYncbAZMOiJKAipKssMlulVwN4gsXJDU6wQcnVJrcI=; b=ZXWqagMRJZx5ZagPoe2qFheb0tGHoohxT6qiA5JHf1K4MEDSLioqew2vwYPmpw0qT0 dVl7r56RXDAQ1nV9jyghhad4bMzLfEV2w4qkrZhDAit+ZzuL/l6O9YgkNgBe7JqlwIls bINQGGfGnUL1z98DHedbHxloKuIamQP6iwtbY9vPpqIOQ1q3qv6W7OWzwImtmxMzjR1Q uTQL/JyGXmkUbs0GzRlP6HspkQA2ozIlGB5U7fbtvxicCQLGIX1wBDWFtSjGPKNb+3nZ aocqP2D3ncBkxRXq4v2V2jztFUg0K76AD4vRJSMn3JFp+5O9ZA6PNgfnRwoKs+ZFSyx3 4bRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BLYncbAZMOiJKAipKssMlulVwN4gsXJDU6wQcnVJrcI=; b=jiGpCvnjcRLSK2Weqs3QXzHQb9InqAMV3sz2b5WHsTLWt5JsKDxbTd+O4KsZ09b53v 0EnjqMU4SErFNMGQ2hjwz8xiHo1/UYaPxSKmUxealpYe6UgAcpYc7MNlF2luFGTFzps5 a2XOdP/8fJciXnfvHl8FD5CKWneKE4KVs8w3sipoc+tiXXUlZuRw6ExF+CsLLQWi2UNM XyfxNPqNyGxSeZBpgZiuBEBu5gI7w6JN2Y5q7YGmSZE7KFS599Lj0/92M3obDC14p4hu pbT2zOpDPqNwzQeYwHmF7FASZnrUl/2UfV9zRpvW4cPc7u7p7K7Nt/fmoGF07zzXa1kb T4wQ== X-Gm-Message-State: AOAM531MF/tbdvavt4W2V/5WmdMM8E4l3MF3ZsiQ9v0K2gSvMeWGV0jM m6lkd3kC4HlgsBFq+TwSR468R0UIQZ/M5lj7f4NhFA== X-Received: by 2002:a1f:6a82:0:b0:33f:7eeb:5989 with SMTP id f124-20020a1f6a82000000b0033f7eeb5989mr21102144vkc.29.1648653835147; Wed, 30 Mar 2022 08:23:55 -0700 (PDT) MIME-Version: 1.0 References: <20220329070618.GA20396@lst.de> <20220329073254.GA20691@lst.de> <3c42b1ed-7c03-64e6-409e-e92247288cac@kernel.dk> In-Reply-To: <3c42b1ed-7c03-64e6-409e-e92247288cac@kernel.dk> From: Philipp Reisner Date: Wed, 30 Mar 2022 17:23:44 +0200 Message-ID: Subject: Re: state of drbd in mainline To: Jens Axboe Cc: Christoph Hellwig , Lars Ellenberg , drbd-dev@lists.linbit.com, linux-block@vger.kernel.org, linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,RDNS_NONE, SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > Jens, my intention is to keep it in-tree, and at some point update it. > > Regarding your questions: > > That'd be great, but it's been years since there was any significant > updates to the in-kernel drbd... I would strongly suggest that the > in-kernel be brought closer to what people are mostly running, as it > stands it's basically unmaintained. The changes we worked on over many Years in the more recent drbd-9.x branches are just too fundamental to do them in small chunks, we could upstream bit by bit. We need to get that reviewed in a big series. If I started to dump them on linux-block right away, nobody would look at it seriously, since it would be too much. I intend to get people from red hat/suse assigned to do such a review. Then we will do that on linux-block, so that everyone who cares sees what happens. [...] > The main discrepancy here is that there are apparently huge numbers of > in-tree users, yet no fixes or patches at all making it to mainline. > Either drbd is bug free and doesn't require any fixes at all, which I > very much would doubt, or fixes aren't being sent upstream. It is the broad consent among the users of the drbd-8.4 branch (that is what is in-tree), is that it works for its purpose. It is for sure not bug-free, but people are not running into bugs anymore. So, call it free of relevant bugs, if you want. No new features go into that branch, on purpose. To keep it that way. Have a look at that one real bug-fix that was identified in the last Year. https://patchwork.kernel.org/project/linux-block/patch/20210426163032.3454129-1-christoph.boehmwalder@linbit.com/ When do you want to have that reposted to you? right now? Just before the next merge window opens?