From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: syzbot <syzbot+c063a4e176681d2e0380@syzkaller.appspotmail.com>
Cc: christophe.jaillet@wanadoo.fr, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
rafael@kernel.org, raychi@google.com, royluo@google.com,
stern@rowland.harvard.edu, syzkaller-bugs@googlegroups.com,
yuran.pereira@hotmail.com
Subject: Re: [syzbot] [kernel?] general protection fault in usb_hub_create_port_device
Date: Mon, 16 Oct 2023 10:40:52 +0300 [thread overview]
Message-ID: <ZSzpBLL0D/wF7DHw@smile.fi.intel.com> (raw)
In-Reply-To: <000000000000a7d2820607bb49c2@google.com>
On Sat, Oct 14, 2023 at 11:20:36PM -0700, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit fd6f7ad2fd4d53fa14f4fd190f9b05d043973892
> Author: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Date: Mon Aug 28 14:58:24 2023 +0000
>
> driver core: return an error when dev_set_name() hasn't happened
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=148e8a9d680000
> start commit: 7733171926cc Merge tag 'mailbox-v6.6' of git://git.linaro...
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=b273cdfbc13e9a4b
> dashboard link: https://syzkaller.appspot.com/bug?extid=c063a4e176681d2e0380
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17a4ca00680000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=13bed168680000
>
> If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: driver core: return an error when dev_set_name() hasn't happened
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-10-16 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <000000000000d04ea90604a6efcc@google.com>
2023-10-15 6:20 ` [syzbot] [kernel?] general protection fault in usb_hub_create_port_device syzbot
2023-10-16 7:40 ` Andy Shevchenko [this message]
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=ZSzpBLL0D/wF7DHw@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=raychi@google.com \
--cc=royluo@google.com \
--cc=stern@rowland.harvard.edu \
--cc=syzbot+c063a4e176681d2e0380@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yuran.pereira@hotmail.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