From: Petr Vorel <pvorel@suse.cz>
To: Andrea Cervesato <andrea.cervesato@suse.de>
Cc: Linux Test Project <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 0/2] Add infiniband testing suite
Date: Tue, 7 Apr 2026 14:56:58 +0200 [thread overview]
Message-ID: <20260407125658.GB25645@pevik> (raw)
In-Reply-To: <20260325-infiniband_rdma-v1-0-9c1bd3e69d29@suse.com>
> This patch series introduces a test for infiniband testing, based on
> https://marc.info/?l=linux-kernel&m=152625244101970&w=2.
https://lore.kernel.org/lkml/20180513230237.GG677@sol.localdomain/
Thanks for pointing out the C source. I was looking at the original syzkaller
reproducer [1] which IMHO did more things, simplified C source is quite similar
to what you do in LTP test.
Have you verified if it actually reproduce the bug on affected kernel? Does it
reproduce the bug?
I tried it only on too new kernel (6.12 based SLE16 kernel, required to install
rdma-core, rdma_cm kernel module, which creates /dev/infiniband/rdma_cm, was
loaded by default).
Kind regards,
Petr
[1] https://syzkaller.appspot.com/text?tag=ReproSyz&x=1686969e400000
> Consider this as a snapshot for a possible test. I sent it to the ML
> just to have some feedbacks.
> Signed-off-by: Andrea Cervesato <andrea.cervesato@suse.com>
> ---
> Andrea Cervesato (2):
> lapi: Add fallback rdma_user_cm.h definitions
> device-drivers/rdma: Add ucma_uaf01 test
> configure.ac | 1 +
> include/lapi/rdma_user_cm.h | 72 ++++++++
> runtest/kernel_misc | 1 +
> testcases/kernel/device-drivers/Makefile | 1 +
> testcases/kernel/device-drivers/rdma/.gitignore | 1 +
> testcases/kernel/device-drivers/rdma/Makefile | 7 +
> testcases/kernel/device-drivers/rdma/ucma_uaf01.c | 208 ++++++++++++++++++++++
> 7 files changed, 291 insertions(+)
> ---
> base-commit: b874b6a264cf4f343c17d543ebe4ff91fbb89042
> change-id: 20260325-infiniband_rdma-c94a1f4f7255
> Best regards,
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-04-07 12:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 15:25 [LTP] [PATCH 0/2] Add infiniband testing suite Andrea Cervesato
2026-03-25 15:25 ` [LTP] [PATCH 1/2] lapi: Add fallback rdma_user_cm.h definitions Andrea Cervesato
2026-04-17 12:02 ` [LTP] " linuxtestproject.agent
2026-03-25 15:25 ` [LTP] [PATCH 2/2] device-drivers/rdma: Add ucma_uaf01 test Andrea Cervesato
2026-04-07 13:24 ` Petr Vorel
2026-04-07 13:24 ` Petr Vorel
2026-04-12 14:14 ` Leon Romanovsky
2026-04-12 14:14 ` Leon Romanovsky via ltp
2026-04-14 7:30 ` Petr Vorel
2026-04-14 7:30 ` Petr Vorel
2026-04-14 9:17 ` Leon Romanovsky
2026-04-14 9:17 ` Leon Romanovsky via ltp
2026-04-23 9:27 ` Petr Vorel
2026-04-23 9:27 ` Petr Vorel
2026-04-08 7:16 ` Petr Vorel
2026-04-07 12:56 ` Petr Vorel [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=20260407125658.GB25645@pevik \
--to=pvorel@suse.cz \
--cc=andrea.cervesato@suse.de \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.