public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+a3f758b8d8cb7e49afec@syzkaller.appspotmail.com>
To: chaorace@gmail.com, dan.carpenter@linaro.org,
	dmitry.torokhov@gmail.com, dzm91@hust.edu.cn, error27@gmail.com,
	gregkh@linuxfoundation.org, hdanton@sina.com,
	hust-os-kernel-patches@googlegroups.com,
	kernel-janitors@vger.kernel.org, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	matthias.benkmann@gmail.com, mkorpershoek@baylibre.com,
	mudongliangabcd@gmail.com, nate@yocom.org,
	pgriffais@valvesoftware.com, radon86dev@gmail.com,
	rafael@kernel.org, rojtberg@gmail.com, s.demassari@gmail.com,
	stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com,
	vi@endrift.com
Subject: Re: [syzbot] [usb?] general protection fault in xpad_probe
Date: Sat, 29 Apr 2023 22:19:23 -0700	[thread overview]
Message-ID: <0000000000006c7b6b05fa86d9ee@google.com> (raw)
In-Reply-To: <00000000000083d76d05f909f716@google.com>

syzbot has bisected this issue to:

commit db7220c48d8d71476f881a7ae1285e1df4105409
Author: Vicki Pfau <vi@endrift.com>
Date:   Fri Mar 24 17:42:27 2023 +0000

    Input: xpad - fix support for some third-party controllers

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=1028a1f8280000
start commit:   92e815cf07ed Add linux-next specific files for 20230428
git tree:       linux-next
final oops:     https://syzkaller.appspot.com/x/report.txt?x=1228a1f8280000
console output: https://syzkaller.appspot.com/x/log.txt?x=1428a1f8280000
kernel config:  https://syzkaller.appspot.com/x/.config?x=c8c8ae4d47d23592
dashboard link: https://syzkaller.appspot.com/bug?extid=a3f758b8d8cb7e49afec
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=14a5408c280000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=10d3b0e4280000

Reported-by: syzbot+a3f758b8d8cb7e49afec@syzkaller.appspotmail.com
Fixes: db7220c48d8d ("Input: xpad - fix support for some third-party controllers")

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

  parent reply	other threads:[~2023-04-30  5:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-11  6:54 [syzbot] [kernel?] general protection fault in xpad_probe syzbot
2023-04-29 13:47 ` [syzbot] [usb?] " syzbot
2023-04-29 18:09   ` Alan Stern
2023-04-29 23:49     ` Dongliang Mu
2023-04-30  5:19 ` syzbot [this message]
     [not found] <20230430014527.3017-1-hdanton@sina.com>
2023-04-30  2:43 ` 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=0000000000006c7b6b05fa86d9ee@google.com \
    --to=syzbot+a3f758b8d8cb7e49afec@syzkaller.appspotmail.com \
    --cc=chaorace@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=dzm91@hust.edu.cn \
    --cc=error27@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdanton@sina.com \
    --cc=hust-os-kernel-patches@googlegroups.com \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=matthias.benkmann@gmail.com \
    --cc=mkorpershoek@baylibre.com \
    --cc=mudongliangabcd@gmail.com \
    --cc=nate@yocom.org \
    --cc=pgriffais@valvesoftware.com \
    --cc=radon86dev@gmail.com \
    --cc=rafael@kernel.org \
    --cc=rojtberg@gmail.com \
    --cc=s.demassari@gmail.com \
    --cc=stern@rowland.harvard.edu \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=vi@endrift.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