| commit | 6d882d61f1361dd289cdddb857622efd313671fc | [log] [tgz] |
|---|---|---|
| author | Shi Jin <sjina@amazon.com> | Thu Nov 06 18:27:00 2025 +0000 |
| committer | Nicolas Morey <nmorey@suse.com> | Fri Nov 21 13:24:36 2025 +0100 |
| tree | b0458af78c56c49190f999f2c7aec147499c590a | |
| parent | 4b63fad01dbeebc467b4d0ae3af694c12fcf7bf9 [diff] |
providers/efa: Fix the size check in efadv_create_cq
[ Upstream commit 696ed925ac4d48adf0cc97f7dd781dec6d762b8a ]
efadv_create_cq incorrectly uses sizeof(efa_attr) instead
of sizeof(*efa_attr) to calculate the size of the efa_attr struct,
as a result, the currentt inlen>sizeof(efa_attr) will always be
true as the latter will be 8 bytes always.
This bug breaks the backward compatibility when a library is built
with an older rdma-core that has smaller efa_attr struct, but
run with newer rdma-core that has larger efa_attr, as the later called
`is_ext_clear` check is to make sure when application
input a inlen larger than size of efa_attr,
the extra space are all zero-ed, and it will fail when the inlen
is smaller than the actual size of efa_attr.
However when inlen is <= than size of the efa_attr struct,
such is_ext_clear check shouldn't happen.
Fixes: a00b600 ("efa: Introduce EFA DV CQ")
Signed-off-by: Shi Jin <sjina@amazon.com>
Signed-off-by: Nicolas Morey <nmorey@suse.com>
This is the userspace components for the Linux Kernel's drivers/infiniband subsystem. Specifically this contains the userspace libraries for the following device nodes:
The userspace component of the libibverbs RDMA kernel drivers are included under the providers/ directory. Support for the following Kernel RDMA drivers is included:
Additional service daemons are provided for:
This project uses a cmake based build system. Quick start:
$ bash build.sh
build/bin will contain the sample programs and build/lib will contain the shared libraries. The build is configured to run all the programs ‘in-place’ and cannot be installed.
$ apt-get install build-essential cmake gcc libudev-dev libnl-3-dev libnl-route-3-dev ninja-build pkg-config valgrind python3-dev cython3 python3-docutils pandoc
Supported releases:
$ dnf builddep redhat/rdma-core.spec
NOTE: Fedora Core uses the name ‘ninja-build’ for the ‘ninja’ command.
$ zypper install cmake gcc libnl3-devel libudev-devel ninja pkg-config valgrind-devel python3-devel python3-Cython python3-docutils pandoc
Install required packages:
$ yum install cmake gcc libnl3-devel libudev-devel make pkgconfig valgrind-devel
Developers on CentOS 7 or Amazon Linux 2 are suggested to install more modern tooling for the best experience.
CentOS 7:
$ yum install epel-release $ yum install cmake3 ninja-build pandoc
Amazon Linux 2:
$ amazon-linux-extras install epel $ yum install cmake3 ninja-build pandoc
NOTE: EPEL uses the name ‘ninja-build’ for the ‘ninja’ command, and ‘cmake3’ for the ‘cmake’ command.
To set up software RDMA on an existing interface with either of the available drivers, use the following commands, substituting <DRIVER> with the name of the driver of your choice (rdma_rxe or siw) and <TYPE> with the type corresponding to the driver (rxe or siw).
# modprobe <DRIVER> # rdma link add <NAME> type <TYPE> netdev <DEVICE>
Please note that you need version of iproute2 recent enough is required for the command above to work.
You can use either ibv_devices or rdma link to verify that the device was successfully added.
Bugs should be reported to the linux-rdma@vger.kernel.org mailing list In your bug report, please include:
Information about your system:
How to reproduce the bug.
If the bug is a crash, the exact output printed out when the crash occurred, including any kernel messages produced.
See Contributing to rdma-core.
Stable versions are released regularly with backported fixes (see Documentation/stable.md) The current minimum version still maintained is ‘v28.X’