From: syzbot <syzbot+bc9e2d2dbcb347dd215a@syzkaller.appspotmail.com>
To: akpm@linux-foundation.org, davem@davemloft.net, jiri@nvidia.com,
kuba@kernel.org, leonro@nvidia.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] WARNING in page_counter_cancel (3)
Date: Sat, 18 Dec 2021 11:59:18 -0800 [thread overview]
Message-ID: <000000000000420dda05d37117f9@google.com> (raw)
In-Reply-To: <00000000000021bb9b05d14bf0c7@google.com>
syzbot has bisected this issue to:
commit 22849b5ea5952d853547cc5e0651f34a246b2a4f
Author: Leon Romanovsky <leonro@nvidia.com>
Date: Thu Oct 21 14:16:14 2021 +0000
devlink: Remove not-executed trap policer notifications
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16464095b00000
start commit: 158b515f703e tun: avoid double free in tun_free_netdev
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=15464095b00000
console output: https://syzkaller.appspot.com/x/log.txt?x=11464095b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=fa556098924b78f0
dashboard link: https://syzkaller.appspot.com/bug?extid=bc9e2d2dbcb347dd215a
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=13ff127eb00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=11bedb6db00000
Reported-by: syzbot+bc9e2d2dbcb347dd215a@syzkaller.appspotmail.com
Fixes: 22849b5ea595 ("devlink: Remove not-executed trap policer notifications")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
prev parent reply other threads:[~2021-12-18 19:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 12:49 syzbot
2021-12-18 14:04 ` syzbot
2021-12-21 23:57 ` Andrew Morton
2021-12-29 9:23 ` Michal Hocko
2022-01-05 0:08 ` Mat Martineau
2021-12-18 19: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=000000000000420dda05d37117f9@google.com \
--to=syzbot+bc9e2d2dbcb347dd215a@syzkaller.appspotmail.com \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netdev@vger.kernel.org \
--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