From: Zhu Yanjun <yanjun.zhu@linux.dev>
To: Willy Tarreau <w@1wt.eu>,
sungbyeongchan <tjdqudcks0424@naver.com>,
"yanjun.zhu@linux.dev" <yanjun.zhu@linux.dev>
Cc: Zhu Yanjun <zyjzyj2000@gmail.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Leon Romanovsky <leon@kernel.org>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
security@kernel.org
Subject: Re: [BUG] RDMA/rxe: unchecked receive WQE cursor causes OOB access
Date: Tue, 6 Oct 2026 22:00:02 -0700 [thread overview]
Message-ID: <86debfbb-b507-4ec0-8ed6-bf112b5f960e@linux.dev> (raw)
In-Reply-To: <asWzwbYj7kVTiQ3L@1wt.eu>
在 2026/10/6 19:51, Willy Tarreau 写道:
> Hello,
>
> On Tue, Oct 06, 2026 at 06:12:38PM +0900, sungbyeongchan wrote:
>> This report was prepared with AI assistance and is being treated as
>> public under Documentation/process/security-bugs.rst. A tested source
>> reproducer, logs, configuration, and proposed patch are available to the
>> maintainers on request; the reproducer is intentionally not attached to
>> this public report.
>
> Please do *always* post a patch. Maintainers receive lots of messages
> like this one every single day, there's no point sending a message
> saying "you might be interested in a patch I have" without sending
> the patch, it wastes time and effort doing round trips. Just send it.
> Same for the reproducers, if they're not too big, just send them to
> the maintainers (not the mailing lists) so they have everything to
> start working on when they open their mailbox.
>
Thanks a lot. Willy. With AI assistance, too many problems have been found.
Yanjun Zhu
> Thanks,
> Willy
prev parent reply other threads:[~2026-10-07 6:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 9:12 sungbyeongchan
2026-10-07 2:51 ` Willy Tarreau
2026-10-07 5:00 ` Zhu Yanjun [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=86debfbb-b507-4ec0-8ed6-bf112b5f960e@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=security@kernel.org \
--cc=tjdqudcks0424@naver.com \
--cc=w@1wt.eu \
--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
all inboxes | Powered by JetHome®