From: syzbot <syzbot+14afda08dc3484d5db82@syzkaller.appspotmail.com>
To: junjie.cao@intel.com, linux-hams@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hams?] possible deadlock in nr_rt_ioctl (2)
Date: Wed, 03 Dec 2025 19:41:02 -0800 [thread overview]
Message-ID: <693102ce.a70a0220.d98e3.01c5.GAE@google.com> (raw)
In-Reply-To: <20251204032128.23306-1-junjie.cao@intel.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+14afda08dc3484d5db82@syzkaller.appspotmail.com
Tested-by: syzbot+14afda08dc3484d5db82@syzkaller.appspotmail.com
Tested on:
commit: 8dcc9e1c netrom: fix possible deadlock in nr_rt_device..
git tree: https://github.com/Junjie650/linux.git v2-fix-netrom-deadlock
console output: https://syzkaller.appspot.com/x/log.txt?x=1674401a580000
kernel config: https://syzkaller.appspot.com/x/.config?x=90f44281c1be60ac
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.
prev parent reply other threads:[~2025-12-04 3:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-26 13:33 [syzbot] [hams?] possible deadlock in nr_rt_ioctl (2) syzbot
2025-06-26 14:13 ` Edward Adam Davis
2025-06-26 14:28 ` syzbot
2025-06-26 14:20 ` Edward Adam Davis
2025-06-26 14:41 ` syzbot
2025-06-26 21:49 ` Hillf Danton
2025-06-26 22:09 ` syzbot
2025-11-06 9:45 ` syzbot
2025-11-27 2:04 ` Forwarded: " syzbot
2025-11-27 2:04 ` Junjie Cao
2025-11-27 2:25 ` syzbot
2025-12-04 3:21 ` Forwarded: " syzbot
2025-12-04 3:21 ` Junjie Cao
2025-12-04 3:41 ` syzbot [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=693102ce.a70a0220.d98e3.01c5.GAE@google.com \
--to=syzbot+14afda08dc3484d5db82@syzkaller.appspotmail.com \
--cc=junjie.cao@intel.com \
--cc=linux-hams@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.