From: syzbot <syzbot+0ef06384b5f39a16ebb9@syzkaller.appspotmail.com>
To: Jason@zx2c4.com, a@unstable.cc, amcohen@nvidia.com,
b.a.t.m.a.n@lists.open-mesh.org, davem@davemloft.net,
dsahern@kernel.org, edumazet@google.com, fw@strlen.de,
idosch@OSS.NVIDIA.COM, justin.iurman@uliege.be, kuba@kernel.org,
linux-kernel@vger.kernel.org, mareklindner@neomailbox.ch,
netdev@vger.kernel.org, paskripkin@gmail.com,
praveen5582@gmail.com, sven@narfation.org, sw@simonwunderlich.de,
syzkaller-bugs@googlegroups.com, willemb@google.com,
yoshfuji@linux-ipv6.org, zxu@linkedin.com
Subject: Re: [syzbot] WARNING: ODEBUG bug in batadv_v_ogm_free
Date: Wed, 24 Nov 2021 09:42:10 -0800 [thread overview]
Message-ID: <0000000000009f52f205d18c60a7@google.com> (raw)
In-Reply-To: <000000000000ba80b905cdcd8b19@google.com>
syzbot suspects this issue was fixed by commit:
commit 6f68cd634856f8ca93bafd623ba5357e0f648c68
Author: Pavel Skripkin <paskripkin@gmail.com>
Date: Sun Oct 24 13:13:56 2021 +0000
net: batman-adv: fix error handling
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=114e3c16b00000
start commit: cf52ad5ff16c Merge tag 'driver-core-5.15-rc6' of git://git..
git tree: upstream
kernel config: https://syzkaller.appspot.com/x/.config?x=9479508d7bb83ad9
dashboard link: https://syzkaller.appspot.com/bug?extid=0ef06384b5f39a16ebb9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=17af7344b00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15dc02fb300000
If the result looks correct, please mark the issue as fixed by replying with:
#syz fix: net: batman-adv: fix error handling
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2021-11-24 17:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 1:46 [syzbot] WARNING: ODEBUG bug in batadv_v_ogm_free syzbot
2021-11-24 17:42 ` syzbot [this message]
2021-11-24 17:43 ` Pavel Skripkin
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=0000000000009f52f205d18c60a7@google.com \
--to=syzbot+0ef06384b5f39a16ebb9@syzkaller.appspotmail.com \
--cc=Jason@zx2c4.com \
--cc=a@unstable.cc \
--cc=amcohen@nvidia.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=idosch@OSS.NVIDIA.COM \
--cc=justin.iurman@uliege.be \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mareklindner@neomailbox.ch \
--cc=netdev@vger.kernel.org \
--cc=paskripkin@gmail.com \
--cc=praveen5582@gmail.com \
--cc=sven@narfation.org \
--cc=sw@simonwunderlich.de \
--cc=syzkaller-bugs@googlegroups.com \
--cc=willemb@google.com \
--cc=yoshfuji@linux-ipv6.org \
--cc=zxu@linkedin.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 read-only IMAP folder(s) and NNTP newsgroup(s).