From: "Yanjun.Zhu" <yanjun.zhu@linux.dev>
To: syzbot <syzbot+b0da83a6c0e2e2bddbd4@syzkaller.appspotmail.com>,
edwards@nvidia.com, hdanton@sina.com, jgg@ziepe.ca,
leon@kernel.org, leonro@nvidia.com, linux-kernel@vger.kernel.org,
linux-rdma@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [rdma?] WARNING in gid_table_release_one (3)
Date: Fri, 12 Sep 2025 13:01:13 -0700 [thread overview]
Message-ID: <691d3ecd-7960-46bb-b41e-be223e320d33@linux.dev> (raw)
In-Reply-To: <6f3b9149-2a2d-4532-b38f-946b98e72000@linux.dev>
On 9/12/25 12:38 PM, yanjun.zhu wrote:
> On 9/11/25 9:42 PM, syzbot wrote:
>> syzbot has bisected this issue to:
>>
>> commit a92fbeac7e94a420b55570c10fe1b90e64da4025
>> Author: Leon Romanovsky <leonro@nvidia.com>
>> Date: Tue May 28 12:52:51 2024 +0000
>>
>> RDMA/cache: Release GID table even if leak is detected
>
> Maybe this commit just detects ref leaks and reports ref leak.
> Even though this commit is reverted, this ref leak still occurs.
>
> The root cause is not in this commit.
>
> "
> GID entry ref leak for dev syz1 index 2 ref=615
> "
>
> Ref leaks in dev syz1.
In this link: https://syzkaller.appspot.com/x/log.txt?x=157dab12580000
"
[ 184.209420][ T6164] infiniband syz1: set active
[ 184.215960][ T6164] infiniband syz1: added syz_tun
[ 184.222514][ T6001] veth0_macvtap: entered promiscuous mode
[ 184.231935][ T42] wlan0: Created IBSS using preconfigured BSSID
50:50:50:50:50:50
[ 184.239777][ T42] wlan0: Creating new IBSS network, BSSID
50:50:50:50:50:50
[ 184.256962][ T6001] veth1_macvtap: entered promiscuous mode
[ 184.276479][ T6164] syz1: rxe_create_cq: returned err = -12 < --
rxe_create_cq failed, the test should not continue.
[ 184.288430][ T6008] veth0_vlan: entered promiscuous mode
"
err = -12, is -ENOMEM.
It means that memory allocation fails.
Zhu Yanjun
>
> Zhu Yanjun
>
>>
>> bisection log: https://syzkaller.appspot.com/x/bisect.txt?
>> x=13fc9642580000
>> start commit: 5f540c4aade9 Add linux-next specific files for 20250910
>> git tree: linux-next
>> final oops: https://syzkaller.appspot.com/x/report.txt?
>> x=10029642580000
>> console output: https://syzkaller.appspot.com/x/log.txt?x=17fc9642580000
>> kernel config: https://syzkaller.appspot.com/x/.config?
>> x=5ed48faa2cb8510d
>> dashboard link: https://syzkaller.appspot.com/bug?
>> extid=b0da83a6c0e2e2bddbd4
>> syz repro: https://syzkaller.appspot.com/x/repro.syz?
>> x=15b52362580000
>> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16b41642580000
>>
>> Reported-by: syzbot+b0da83a6c0e2e2bddbd4@syzkaller.appspotmail.com
>> Fixes: a92fbeac7e94 ("RDMA/cache: Release GID table even if leak is
>> detected")
>>
>> For information about bisection process see: https://goo.gl/
>> tpsmEJ#bisection
>
next prev parent reply other threads:[~2025-09-12 20:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 11:35 [syzbot] [rdma?] WARNING in gid_table_release_one (3) syzbot
2025-05-14 8:54 ` Leon Romanovsky
2025-09-17 12:45 ` Jason Gunthorpe
2025-09-11 15:34 ` syzbot
2025-09-16 16:15 ` yanjun.zhu
2025-09-12 4:42 ` syzbot
2025-09-12 19:38 ` yanjun.zhu
2025-09-12 20:01 ` Yanjun.Zhu [this message]
2025-09-12 22:33 ` Yanjun.Zhu
2025-09-12 22:55 ` Yanjun.Zhu
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=691d3ecd-7960-46bb-b41e-be223e320d33@linux.dev \
--to=yanjun.zhu@linux.dev \
--cc=edwards@nvidia.com \
--cc=hdanton@sina.com \
--cc=jgg@ziepe.ca \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=syzbot+b0da83a6c0e2e2bddbd4@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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