From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: syzbot <syzbot+410a8e33c6a740b40d51@syzkaller.appspotmail.com>
Cc: gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
rafael@kernel.org, ricardo@marliere.net,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] general protection fault in hci_register_dev
Date: Tue, 17 Oct 2023 18:56:09 +0300 [thread overview]
Message-ID: <ZS6umTVPGqY8Yycs@smile.fi.intel.com> (raw)
In-Reply-To: <0000000000000e34f70607eb86f5@google.com>
On Tue, Oct 17, 2023 at 08:53:28AM -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=17925039680000
> start commit: 92901222f83d Merge tag 'f2fs-for-6-6-rc1' of git://git.ker..
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=3bd57a1ac08277b0
> dashboard link: https://syzkaller.appspot.com/bug?extid=410a8e33c6a740b40d51
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14df7104680000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=125a5357a80000
>
> 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-17 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 15:43 syzbot
2023-09-18 20:32 ` Ricardo B. Marliere
2023-09-18 20:57 ` syzbot
2023-10-17 15:53 ` syzbot
2023-10-17 15:56 ` 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=ZS6umTVPGqY8Yycs@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ricardo@marliere.net \
--cc=syzbot+410a8e33c6a740b40d51@syzkaller.appspotmail.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
all inboxes | Powered by JetHome®