From: syzbot <syzbot+48c14f61594bdfadb086@syzkaller.appspotmail.com>
To: andrew@lunn.ch, davem@davemloft.net, edumazet@google.com,
horms@kernel.org, jv@jvosburgh.net, kuba@kernel.org,
linux-kernel@vger.kernel.org, liuhangbin@gmail.com,
netdev@vger.kernel.org, pabeni@redhat.com, sdf@fomichev.me,
stfomichev@gmail.com, sven@narfation.org, sw@simonwunderlich.de,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [net?] WARNING in __linkwatch_sync_dev
Date: Tue, 08 Apr 2025 20:59:05 -0700 [thread overview]
Message-ID: <67f5f089.050a0220.258fea.0009.GAE@google.com> (raw)
In-Reply-To: <67f4d325.050a0220.396535.0558.GAE@google.com>
syzbot has bisected this issue to:
commit 00b35530811f2aa3d7ceec2dbada80861c7632a8
Author: Eric Dumazet <edumazet@google.com>
Date: Thu Feb 6 14:04:22 2025 +0000
batman-adv: adopt netdev_hold() / netdev_put()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=175db74c580000
start commit: 7702d0130dc0 Add linux-next specific files for 20250408
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=14ddb74c580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10ddb74c580000
kernel config: https://syzkaller.appspot.com/x/.config?x=91edf513888f57d7
dashboard link: https://syzkaller.appspot.com/bug?extid=48c14f61594bdfadb086
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11520398580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16b1323f980000
Reported-by: syzbot+48c14f61594bdfadb086@syzkaller.appspotmail.com
Fixes: 00b35530811f ("batman-adv: adopt netdev_hold() / netdev_put()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2025-04-09 3:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 7:41 [syzbot] [net?] WARNING in __linkwatch_sync_dev syzbot
2025-04-08 15:56 ` Stanislav Fomichev
2025-04-08 21:40 ` syzbot
2025-04-09 3:59 ` 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=67f5f089.050a0220.258fea.0009.GAE@google.com \
--to=syzbot+48c14f61594bdfadb086@syzkaller.appspotmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdf@fomichev.me \
--cc=stfomichev@gmail.com \
--cc=sven@narfation.org \
--cc=sw@simonwunderlich.de \
--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.