All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Pecio <michal.pecio@gmail.com>
To: syzbot <syzbot+7300affe388249d66dfe@syzkaller.appspotmail.com>
Cc: gregkh@linuxfoundation.org, i@zenithal.me,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	shuah@kernel.org, syzkaller-bugs@googlegroups.com,
	valentina.manea.m@gmail.com, syzkaller@googlegroups.com
Subject: Re: [syzbot] [usb?] general protection fault in vhci_hcd_probe
Date: Sat, 5 Sep 2026 10:43:31 +0200	[thread overview]
Message-ID: <20260905104331.6d4288df.michal.pecio@gmail.com> (raw)
In-Reply-To: <6a9bceeb.a5e650b3.26d8a.0008.GAE@google.com>

On Sat, 05 Sep 2026 01:12:27 -0700, syzbot wrote:
> syzbot has found a reproducer for the following issue on:
> 
> HEAD commit:    9d80aa4617b3 Add linux-next specific files for 20260903
> git tree:       git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> console output: https://syzkaller.appspot.com/x/log.txt?x=10adf4f9580000
> kernel config:  https://syzkaller.appspot.com/x/.config?x=bb4a32c282cc2ec7
> dashboard link: https://syzkaller.appspot.com/bug?extid=7300affe388249d66dfe
> compiler:       Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
> C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=121c7215580000

Who or what is coming up with these ideas and even commenting it?

    // Iterate platform devices
    dir = opendir("/sys/bus/platform/devices/");

    while ((ent = readdir(dir)) != NULL) {

        // Set driver override
        snprintf(path, sizeof(path), "/sys/bus/platform/devices/%s/driver_override", ent->d_name);
        fd = open(path, O_WRONLY);

        // Bind to vhci_hcd
        fd = open("/sys/bus/platform/drivers/vhci_hcd/bind", O_WRONLY);

  reply	other threads:[~2026-09-05  8:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-21  8:03 [syzbot] [usb?] general protection fault in vhci_hcd_probe syzbot
2026-09-05  8:12 ` syzbot
2026-09-05  8:43   ` Michal Pecio [this message]
2026-09-05 11:30     ` Greg KH
2026-09-06 10:38       ` Michal Pecio
2026-09-07  7:59         ` Aleksandr Nogikh
2026-09-07  8:22           ` Michal Pecio
2026-09-11  9:54             ` Aleksandr Nogikh

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=20260905104331.6d4288df.michal.pecio@gmail.com \
    --to=michal.pecio@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=i@zenithal.me \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=shuah@kernel.org \
    --cc=syzbot+7300affe388249d66dfe@syzkaller.appspotmail.com \
    --cc=syzkaller-bugs@googlegroups.com \
    --cc=syzkaller@googlegroups.com \
    --cc=valentina.manea.m@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.