From: syzbot <syzbot+08df3e4c9b304b37cb04@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [block?] general protection fault in rtlock_slowlock_locked
Date: Sat, 08 Nov 2025 00:11:02 -0800 [thread overview]
Message-ID: <690efb16.a70a0220.22f260.0077.GAE@google.com> (raw)
In-Reply-To: <20251108074339.9025-1-hdanton@sina.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+08df3e4c9b304b37cb04@syzkaller.appspotmail.com
Tested-by: syzbot+08df3e4c9b304b37cb04@syzkaller.appspotmail.com
Tested on:
commit: e811c33b Merge tag 'drm-fixes-2025-11-08' of https://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15c5117c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=41ad820f608cb833
dashboard link: https://syzkaller.appspot.com/bug?extid=08df3e4c9b304b37cb04
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=11746a58580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-11-08 8:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 16:01 [syzbot] [ntfs3?] [usb?] general protection fault in rtlock_slowlock_locked syzbot
2025-11-08 4:01 ` [syzbot] [block?] " syzbot
2025-11-08 7:43 ` Hillf Danton
2025-11-08 8:11 ` syzbot [this message]
2025-11-10 12:13 ` Edward Adam Davis
2025-11-10 12:52 ` syzbot
2025-11-10 13:08 ` Edward Adam Davis
2025-11-10 13:26 ` syzbot
2025-11-10 14:18 ` Edward Adam Davis
2025-11-10 14:41 ` syzbot
2025-11-10 14:50 ` Edward Adam Davis
2025-11-10 15:17 ` syzbot
2025-11-10 23:20 ` Edward Adam Davis
2025-11-11 0:12 ` 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=690efb16.a70a0220.22f260.0077.GAE@google.com \
--to=syzbot+08df3e4c9b304b37cb04@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