From: syzbot <syzbot+14afda08dc3484d5db82@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [hams?] possible deadlock in nr_rt_ioctl (2)
Date: Thu, 26 Jun 2025 15:09:02 -0700 [thread overview]
Message-ID: <685dc4fe.a00a0220.2e5631.037b.GAE@google.com> (raw)
In-Reply-To: <20250626214902.1880-1-hdanton@sina.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: f02769e7 Merge tag 'devicetree-fixes-for-6.16-1' of gi..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14217182580000
kernel config: https://syzkaller.appspot.com/x/.config?x=644a0493ff5118b1
dashboard link: https://syzkaller.appspot.com/bug?extid=14afda08dc3484d5db82
compiler: gcc (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40
patch: https://syzkaller.appspot.com/x/patch.diff?x=127e7182580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-06-26 22:09 UTC|newest]
Thread overview: 12+ 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 [this message]
2025-11-06 9:45 ` syzbot
2025-11-27 2:04 ` Forwarded: " syzbot
2025-12-04 3:21 ` syzbot
[not found] <20251127020450.118479-1-junjie.cao@intel.com>
2025-11-27 2:25 ` syzbot
[not found] <20251204032128.23306-1-junjie.cao@intel.com>
2025-12-04 3:41 ` syzbot
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=685dc4fe.a00a0220.2e5631.037b.GAE@google.com \
--to=syzbot+14afda08dc3484d5db82@syzkaller.appspotmail.com \
--cc=hdanton@sina.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox