From: syzbot <syzbot+662f783a5cdf3add2719@syzkaller.appspotmail.com>
To: amir.hanania@intel.com, davem@davemloft.net, edumazet@google.com,
hdanton@sina.com, horms@kernel.org, idosch@idosch.org,
idosch@nvidia.com, jeffrey.t.kirsher@intel.com,
john.fastabend@gmail.com, kuba@kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, syzkaller-bugs@googlegroups.com,
vladbu@nvidia.com
Subject: Re: [syzbot] [net?] WARNING in unregister_vlan_dev
Date: Sun, 13 Aug 2023 01:26:36 -0700 [thread overview]
Message-ID: <000000000000496a0f0602c9b43c@google.com> (raw)
In-Reply-To: <00000000000090196d0602a6167d@google.com>
syzbot has bisected this issue to:
commit 718cb09aaa6fa78cc8124e9517efbc6c92665384
Author: Vlad Buslov <vladbu@nvidia.com>
Date: Tue Aug 8 09:35:21 2023 +0000
vlan: Fix VLAN 0 memory leak
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12ac8d6fa80000
start commit: 048c796beb6e ipv6: adjust ndisc_is_useropt() to also retur..
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=11ac8d6fa80000
console output: https://syzkaller.appspot.com/x/log.txt?x=16ac8d6fa80000
kernel config: https://syzkaller.appspot.com/x/.config?x=fa5bd4cd5ab6259d
dashboard link: https://syzkaller.appspot.com/bug?extid=662f783a5cdf3add2719
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1604a23da80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15261ffda80000
Reported-by: syzbot+662f783a5cdf3add2719@syzkaller.appspotmail.com
Fixes: 718cb09aaa6f ("vlan: Fix VLAN 0 memory leak")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2023-08-13 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 13:57 [syzbot] [net?] WARNING in unregister_vlan_dev syzbot
2023-08-13 8:26 ` syzbot [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=000000000000496a0f0602c9b43c@google.com \
--to=syzbot+662f783a5cdf3add2719@syzkaller.appspotmail.com \
--cc=amir.hanania@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hdanton@sina.com \
--cc=horms@kernel.org \
--cc=idosch@idosch.org \
--cc=idosch@nvidia.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vladbu@nvidia.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).