From: syzbot <syzbot+83976e47ec1ef91e66f1@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, qasdev00@gmail.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] general protection fault in status_show
Date: Fri, 17 Jan 2025 08:01:03 -0800 [thread overview]
Message-ID: <678a7ebf.050a0220.303755.000b.GAE@google.com> (raw)
In-Reply-To: <Z4p6BwKCBliyJAC2@qasdev.system>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+83976e47ec1ef91e66f1@syzkaller.appspotmail.com
Tested-by: syzbot+83976e47ec1ef91e66f1@syzkaller.appspotmail.com
Tested on:
commit: 9bffa1ad Merge tag 'drm-fixes-2025-01-17' of https://g..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=113fda18580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f5e182416a4b418f
dashboard link: https://syzkaller.appspot.com/bug?extid=83976e47ec1ef91e66f1
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=10bc69df980000
Note: testing is done by a robot and is best-effort only.
next parent reply other threads:[~2025-01-17 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Z4p6BwKCBliyJAC2@qasdev.system>
2025-01-17 16:01 ` syzbot [this message]
[not found] <257f9669-a5eb-4577-9341-1a730bc53eaa@linuxfoundation.org>
2025-01-22 22:34 ` [syzbot] [usb?] general protection fault in status_show syzbot
2025-01-17 6:14 syzbot
2025-01-23 11:31 ` Hillf Danton
2025-01-23 11:45 ` syzbot
2025-01-24 11:17 ` Hillf Danton
2025-01-24 11:32 ` syzbot
2025-01-25 10:23 ` Hillf Danton
2025-01-25 10:44 ` 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=678a7ebf.050a0220.303755.000b.GAE@google.com \
--to=syzbot+83976e47ec1ef91e66f1@syzkaller.appspotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=qasdev00@gmail.com \
--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