public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+83976e47ec1ef91e66f1@syzkaller.appspotmail.com>
To: hdanton@sina.com, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [usb?] general protection fault in status_show
Date: Sat, 25 Jan 2025 02:44:02 -0800	[thread overview]
Message-ID: <6794c072.050a0220.3ab881.0011.GAE@google.com> (raw)
In-Reply-To: <20250125102324.1822-1-hdanton@sina.com>

Hello,

syzbot has tested the proposed patch but the reproducer is still triggering an issue:
lost connection to test machine



Tested on:

commit:         b46c89c0 Merge tag 'spi-fix-v6.14-merge-window' of git..
git tree:       upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1292d5df980000
kernel config:  https://syzkaller.appspot.com/x/.config?x=d00941da012c109
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=13b799f8580000


  reply	other threads:[~2025-01-25 10:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-17  6:14 [syzbot] [usb?] general protection fault in status_show syzbot
2025-01-17 15:41 ` [syzbot] syzbot
2025-01-22 22:19 ` [syzbot] Re: [syzbot] [usb?] general protection fault in status_show 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 [this message]
     [not found] <Z4p6BwKCBliyJAC2@qasdev.system>
2025-01-17 16:01 ` syzbot
     [not found] <257f9669-a5eb-4577-9341-1a730bc53eaa@linuxfoundation.org>
2025-01-22 22:34 ` 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=6794c072.050a0220.3ab881.0011.GAE@google.com \
    --to=syzbot+83976e47ec1ef91e66f1@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