On 9/11/25 9:42 PM, syzbot wrote:
syzbot has bisected this issue to:
commit a92fbeac7e94a420b55570c10fe1b90e64da4025
Author: Leon Romanovsky <leonro@xxxxxxxxxx>
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.
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@xxxxxxxxxxxxxxxxxxxxxxxxx
Fixes: a92fbeac7e94 ("RDMA/cache: Release GID table even if leak is detected")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
