From: Gang Yan <gang.yan@linux.dev>
To: zyjzyj2000@gmail.com
Cc: linux-rdma@vger.kernel.org, Gang Yan <yangang@kylinos.cn>
Subject: [PATCH net 0/2] RDMA/rxe: fix mr_check_range() iova overflow (OOB)
Date: Tue, 28 Jul 2026 17:11:26 +0800 [thread overview]
Message-ID: <20260728091128.9116-1-gang.yan@linux.dev> (raw)
From: Gang Yan <yangang@kylinos.cn>
Hi, Maintainers
I've recently started learning RDMA, using soft-RoCE (rxe) as my study
platform. While pair-programming with an AI assistant during this learning,
it flagged an integer overflow in mr_check_range(). I dug in, stood up a
small reproducer, and -- believing the issue is real and worth fixing --
put together this small series.
Thanks
Gang
Gang Yan (2):
RDMA/rxe: Fix integer overflow in mr_check_range() leading to OOB
access
DO-NOT-MERGE: selftest: add rxe mr_check_range() overflow reproducer
drivers/infiniband/sw/rxe/rxe_mr.c | 3 +-
tools/testing/selftests/rdma/Makefile | 8 +-
tools/testing/selftests/rdma/config | 2 +
.../testing/selftests/rdma/rxe_mr_overflow.c | 187 ++++++++++++++++++
.../testing/selftests/rdma/rxe_mr_overflow.sh | 132 +++++++++++++
5 files changed, 330 insertions(+), 2 deletions(-)
create mode 100644 tools/testing/selftests/rdma/rxe_mr_overflow.c
create mode 100644 tools/testing/selftests/rdma/rxe_mr_overflow.sh
--
2.43.0
next reply other threads:[~2026-07-28 9:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 9:11 Gang Yan [this message]
2026-07-28 9:11 ` [PATCH net 1/2] RDMA/rxe: Fix integer overflow in mr_check_range() leading to OOB access Gang Yan
2026-07-28 9:11 ` [PATCH net 2/2] DO-NOT-MERGE: selftest: add rxe mr_check_range() overflow reproducer Gang Yan
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=20260728091128.9116-1-gang.yan@linux.dev \
--to=gang.yan@linux.dev \
--cc=linux-rdma@vger.kernel.org \
--cc=yangang@kylinos.cn \
--cc=zyjzyj2000@gmail.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