From: "yanjun.zhu" <yanjun.zhu@linux.dev>
To: Serhat Kumral <serhatkumral1@gmail.com>,
Zhu Yanjun <zyjzyj2000@gmail.com>,
Zhu Yanjun <yanjun.zhu@linux.dev>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Leon Romanovsky <leon@kernel.org>,
David Ahern <dsahern@kernel.org>,
linux-rdma@vger.kernel.org, linux-kernel@vger.kernel.org,
syzbot+8c9eede336e3a843750e@syzkaller.appspotmail.com
Subject: Re: [RFC PATCH 1/2] RDMA/rxe: drive UDP tunnel socket lifetime from the GID table
Date: Mon, 20 Jul 2026 12:19:55 -0700 [thread overview]
Message-ID: <9f89e398-9848-40bb-a674-9719d94a6151@linux.dev> (raw)
In-Reply-To: <20260720181551.30322-1-serhatkumral1@gmail.com>
On 7/20/26 11:15 AM, Serhat Kumral wrote:
> Thanks for the trace.
I have already provided all the details needed to reproduce this issue.
I suggest reproducing the problem locally first, which would help avoid
a lengthy back-and-forth discussion. It would also allow you to validate
your own fix in the same environment before submitting it.
Zhu Yanjun
>
>> KASAN: null-ptr-deref in range
>> [0x0000000000000000-0x0000000000000007]
>> RIP: 0010:ip_rcv+0xeb/0x570
>
> This shows that the failure is not a deadlock, but a NULL pointer
> dereference in the IPv4 receive path.
>
> To identify the exact source line and confirm which pointer is NULL,
> could you also provide the output of:
>
> ./scripts/faddr2line vmlinux 'ip_rcv+0xeb/0x570'
>
> My series does not modify the RXE IPv4 packet-processing functions,
> but it does change the lifetime of both IPv4 and IPv6 UDP tunnel
> sockets.
>
> Could you please run the same selftest on the same commit and config
> with this series reverted, and report whether it still crashes?
prev parent reply other threads:[~2026-07-20 19:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-18 14:26 [RFC PATCH 1/2] RDMA/rxe: drive UDP tunnel socket lifetime from the GID table Serhat Kumral
2026-07-18 14:26 ` [RFC PATCH 2/2] RDMA/nldev: remove the unused dellink link op Serhat Kumral
2026-07-18 15:39 ` [RFC PATCH 1/2] RDMA/rxe: drive UDP tunnel socket lifetime from the GID table Jason Gunthorpe
2026-07-19 17:54 ` Serhat Kumral
2026-07-18 16:01 ` Zhu Yanjun
2026-07-18 16:04 ` Jason Gunthorpe
2026-07-19 5:08 ` Zhu Yanjun
2026-07-19 17:59 ` Serhat Kumral
2026-07-19 20:50 ` Zhu Yanjun
2026-07-19 21:13 ` Zhu Yanjun
2026-07-20 18:15 ` Serhat Kumral
2026-07-20 19:19 ` yanjun.zhu [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=9f89e398-9848-40bb-a674-9719d94a6151@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=dsahern@kernel.org \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=serhatkumral1@gmail.com \
--cc=syzbot+8c9eede336e3a843750e@syzkaller.appspotmail.com \
--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