From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: syzbot <syzbot+b8bf7edf9f83071ea0a9@syzkaller.appspotmail.com>
Cc: 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: Mon, 23 Oct 2023 13:13:13 +0300 [thread overview]
Message-ID: <ZTZHObssfh+46Lm6@smile.fi.intel.com> (raw)
In-Reply-To: <000000000000af2dbf06083f7baf@google.com>
On Sat, Oct 21, 2023 at 01:03:31PM -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=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
--
With Best Regards,
Andy Shevchenko
prev parent reply other threads:[~2023-10-23 10:13 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
2023-10-23 10:13 ` 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=ZTZHObssfh+46Lm6@smile.fi.intel.com \
--to=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=syzbot+b8bf7edf9f83071ea0a9@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;
as well as URLs for NNTP newsgroup(s).