From: gthelen@google.com (Greg Thelen)
Subject: [PATCH 6/6] IB: make INFINIBAND_ADDR_TRANS configurable
Date: Thu, 26 Apr 2018 11:19:35 -0700 [thread overview]
Message-ID: <20180426181935.32977-7-gthelen@google.com> (raw)
In-Reply-To: <20180426181935.32977-1-gthelen@google.com>
Allow INFINIBAND without INFINIBAND_ADDR_TRANS because fuzzing has been
finding fair number of CM bugs. So provide option to disable it.
Signed-off-by: Greg Thelen <gthelen at google.com>
Cc: Tarick Bedeir <tarick at google.com>
---
drivers/infiniband/Kconfig | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/infiniband/Kconfig b/drivers/infiniband/Kconfig
index ee270e065ba9..2a972ed6851b 100644
--- a/drivers/infiniband/Kconfig
+++ b/drivers/infiniband/Kconfig
@@ -61,9 +61,12 @@ config INFINIBAND_ON_DEMAND_PAGING
pages on demand instead.
config INFINIBAND_ADDR_TRANS
- bool
+ bool "RDMA/CM"
depends on INFINIBAND
default y
+ ---help---
+ Support for RDMA communication manager (CM).
+ This allows for a generic connection abstraction over RDMA.
config INFINIBAND_ADDR_TRANS_CONFIGFS
bool
--
2.17.0.484.g0c8726318c-goog
next prev parent reply other threads:[~2018-04-26 18:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 18:19 [PATCH 0/6] IB: make INFINIBAND_ADDR_TRANS configurable Greg Thelen
2018-04-26 18:19 ` [PATCH 1/6] nvme: depend on INFINIBAND_ADDR_TRANS Greg Thelen
2018-04-26 18:19 ` [PATCH 2/6] nvmet-rdma: " Greg Thelen
2018-04-26 18:19 ` [PATCH 3/6] ib_srpt: " Greg Thelen
2018-04-26 18:25 ` Bart Van Assche
2018-04-26 18:19 ` [PATCH 4/6] cifs: smbd: " Greg Thelen
2018-04-26 18:19 ` [PATCH 5/6] ib_srp: " Greg Thelen
2018-04-26 18:25 ` Bart Van Assche
2018-04-26 18:19 ` Greg Thelen [this message]
2018-04-26 18:26 ` [PATCH 6/6] IB: make INFINIBAND_ADDR_TRANS configurable Bart Van Assche
2018-04-27 16:07 ` [PATCH 0/6] " Doug Ledford
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=20180426181935.32977-7-gthelen@google.com \
--to=gthelen@google.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