[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <0000000000000e34f70607eb86f5@google.com>
Date: Tue, 17 Oct 2023 08:53:28 -0700
From: syzbot <syzbot+410a8e33c6a740b40d51@...kaller.appspotmail.com>
To: andriy.shevchenko@...ux.intel.com, gregkh@...uxfoundation.org,
linux-kernel@...r.kernel.org, rafael@...nel.org,
ricardo@...liere.net, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [kernel?] general protection fault in hci_register_dev
syzbot suspects this issue was fixed by commit:
commit fd6f7ad2fd4d53fa14f4fd190f9b05d043973892
Author: Andy Shevchenko <andriy.shevchenko@...ux.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
Powered by blists - more mailing lists