[<prev] [next>] [day] [month] [year] [list]
Message-ID: <6927b67e.a70a0220.d98e3.00e8.GAE@google.com>
Date: Wed, 26 Nov 2025 18:25:02 -0800
From: syzbot <syzbot+14afda08dc3484d5db82@...kaller.appspotmail.com>
To: junjie.cao@...el.com, linux-hams@...r.kernel.org,
linux-kernel@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [hams?] possible deadlock in nr_rt_ioctl (2)
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+14afda08dc3484d5db82@...kaller.appspotmail.com
Tested-by: syzbot+14afda08dc3484d5db82@...kaller.appspotmail.com
Tested on:
commit: a3aa8a52 net/netrom: Fix deadlock in nr_rt_ioctl
git tree: https://github.com/Junjie650/linux.git fix-netrom-deadlock
console output: https://syzkaller.appspot.com/x/log.txt?x=17016e12580000
kernel config: https://syzkaller.appspot.com/x/.config?x=61603eec826f5965
dashboard link: https://syzkaller.appspot.com/bug?extid=14afda08dc3484d5db82
compiler: gcc (Debian 12.2.0-14+deb12u1) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.
Powered by blists - more mailing lists