From: "Christoph Böhmwalder" <christoph.boehmwalder@linbit.com>
To: Arnd Bergmann <arnd@arndb.de>, Arnd Bergmann <arnd@kernel.org>,
Philipp Reisner <philipp.reisner@linbit.com>,
Lars Ellenberg <lars.ellenberg@linbit.com>,
Jens Axboe <axboe@kernel.dk>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Eric Biggers <ebiggers@google.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>,
drbd-dev@lists.linbit.com
Subject: Re: [PATCH 1/2] drbd: fix rdma dependency
Date: Wed, 18 Mar 2026 16:36:32 +0100 [thread overview]
Message-ID: <faf5b12f-03a2-4d8c-b333-7fc275ec3191@linbit.com> (raw)
In-Reply-To: <c3daa9b5-3741-4a18-9bbc-7bad1a2e0c1b@app.fastmail.com>
Am 18.03.26 um 16:31 schrieb Arnd Bergmann:
> On Wed, Mar 18, 2026, at 16:24, Christoph Böhmwalder wrote:
>> Am 18.03.26 um 11:48 schrieb Arnd Bergmann:
>>
>> Seems like we raced here, I already (supposedly?) fixed this on the
>> drbd-next branch.
>
> Ok, I assume that will be in linux-next
Correct, should land there today.
>
>> My fix is this Kconfig:
>>
>> config BLK_DEV_DRBD_RDMA
>> tristate "DRBD RDMA transport"
>> depends on BLK_DEV_DRBD && INFINIBAND_ADDR_TRANS
>> help
>>
>> RDMA transport support for DRBD. This enables DRBD replication
>> over RDMA-capable networks for lower latency and higher throughput.
>>
>> If unsure, say N.
>>
>> And then just this in the Makefile:
>>
>> obj-$(CONFIG_BLK_DEV_DRBD_RDMA) += drbd_transport_rdma.o
>>
>> That should be equivalent, right?
>
> It's close but not the same:
>
> - INFINIBAND_ADDR_TRANS is a 'bool' symbol that can still be =y
> when CONFIG_INFINIBAND=m, so you'd still fail to build
> BLK_DEV_DRBD_RDMA. You still need a dependency on INFINIBAND
> (the tristate symbol) itself, though you probably also
> need the INFINIBAND_ADDR_TRANS one that I missed
>
> - I incorrectly assumed from the earlier Makefile logic
> that the rdma transport exports symbols that are used
> by the common drbd code, but I now see that the opposite
> is the case. The difference is that for the case of
> BLK_DEV_DRBD=y, CONFIG_INFINIBAND=m, my version force-disabled
> the RDMA transport, while it should be in a loadable module.
>
> It seems both versions are wrong then, but just adding
> 'depends on INFINIBAND' on top of yours should fix it.
Yes, ADDR_TRANS is needed because we need the infiniband "cm"
infrastructure (for rdma_connect et al).
Right, I did not catch that we need CONFIG_INFINIBAND separately as
well, but that seems logical.
I applied the combined fix now.
Thanks,
Christoph
--
Christoph Böhmwalder
LINBIT | Keeping the Digital World Running
DRBD HA — Disaster Recovery — Software defined Storage
prev parent reply other threads:[~2026-03-18 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-18 10:48 [PATCH 1/2] drbd: fix rdma dependency Arnd Bergmann
2026-03-18 10:48 ` [PATCH 2/2] drbd: select CONFIG_NET_HANDSHAKE Arnd Bergmann
2026-03-18 21:16 ` Christoph Böhmwalder
2026-03-18 21:20 ` Arnd Bergmann
2026-03-18 15:24 ` [PATCH 1/2] drbd: fix rdma dependency Christoph Böhmwalder
2026-03-18 15:31 ` Arnd Bergmann
2026-03-18 15:36 ` Christoph Böhmwalder [this message]
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=faf5b12f-03a2-4d8c-b333-7fc275ec3191@linbit.com \
--to=christoph.boehmwalder@linbit.com \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=axboe@kernel.dk \
--cc=drbd-dev@lists.linbit.com \
--cc=ebiggers@google.com \
--cc=lars.ellenberg@linbit.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--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