From: syzbot <syzbot+8400677f3fd43f37d3bc@syzkaller.appspotmail.com>
To: chengen.du@canonical.com, davem@davemloft.net,
edumazet@google.com, eric.dumazet@gmail.com, horms@kernel.org,
kuba@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, pabeni@redhat.com,
syzkaller-bugs@googlegroups.com, willemb@google.com,
willemdebruijn.kernel@gmail.com
Subject: Re: [syzbot] [net?] kernel BUG in vlan_get_tci
Date: Wed, 01 Jan 2025 08:11:04 -0800 [thread overview]
Message-ID: <67756918.050a0220.25abdd.0a11.GAE@google.com> (raw)
In-Reply-To: <6772c485.050a0220.2f3838.04c6.GAE@google.com>
syzbot has bisected this issue to:
commit 79eecf631c14e7f4057186570ac20e2cfac3802e
Author: Chengen Du <chengen.du@canonical.com>
Date: Sat Jul 13 11:47:35 2024 +0000
af_packet: Handle outgoing VLAN packets without hardware offloading
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=116e3818580000
start commit: 9268abe611b0 Merge branch 'net-lan969x-add-rgmii-support'
git tree: net-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=136e3818580000
console output: https://syzkaller.appspot.com/x/log.txt?x=156e3818580000
kernel config: https://syzkaller.appspot.com/x/.config?x=b087c24b921cdc16
dashboard link: https://syzkaller.appspot.com/bug?extid=8400677f3fd43f37d3bc
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=172066df980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=133c6ac4580000
Reported-by: syzbot+8400677f3fd43f37d3bc@syzkaller.appspotmail.com
Fixes: 79eecf631c14 ("af_packet: Handle outgoing VLAN packets without hardware offloading")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-01-01 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 16:04 syzbot
2025-01-01 16:11 ` 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=67756918.050a0220.25abdd.0a11.GAE@google.com \
--to=syzbot+8400677f3fd43f37d3bc@syzkaller.appspotmail.com \
--cc=chengen.du@canonical.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--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=willemb@google.com \
--cc=willemdebruijn.kernel@gmail.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
Powered by JetHome