From: syzbot <syzbot+b8bf7edf9f83071ea0a9@syzkaller.appspotmail.com>
To: andriy.shevchenko@linux.intel.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
rafael@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] general protection fault in wpan_phy_register
Date: Sat, 21 Oct 2023 13:03:31 -0700 [thread overview]
Message-ID: <000000000000af2dbf06083f7baf@google.com> (raw)
In-Reply-To: <0000000000008f824606052a2d9b@google.com>
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=13ea2e89680000
start commit: ac28b1ec6135 net: ipv4: fix one memleak in __inet_del_ifa()
git tree: net
kernel config: https://syzkaller.appspot.com/x/.config?x=e82a7781f9208c0d
dashboard link: https://syzkaller.appspot.com/bug?extid=b8bf7edf9f83071ea0a9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14871d58680000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14ace678680000
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
next prev parent reply other threads:[~2023-10-21 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 14:22 [syzbot] [kernel?] general protection fault in wpan_phy_register syzbot
2023-10-21 20:03 ` syzbot [this message]
2023-10-23 10:13 ` Andy Shevchenko
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=000000000000af2dbf06083f7baf@google.com \
--to=syzbot+b8bf7edf9f83071ea0a9@syzkaller.appspotmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rafael@kernel.org \
--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 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.