On Thu, Aug 20, 2020 at 11:48 AM Jason A. Donenfeld Jason@zx2c4.com wrote:
On Wed, Aug 19, 2020 at 8:42 PM syzbot syzbot+cc4c0f394e2611edba66@syzkaller.appspotmail.com wrote:
syzbot has bisected this issue to:
commit e7096c131e5161fa3b8e52a650d7719d2857adfd Author: Jason A. Donenfeld Jason@zx2c4.com Date: Sun Dec 8 23:27:34 2019 +0000
net: WireGuard secure network tunnelbisection log: https://syzkaller.appspot.com/x/bisect.txt?x=175ad8b1900000 start commit: e3ec1e8c net: eliminate meaningless memcpy to data in pskb.. git tree: net-next final oops: https://syzkaller.appspot.com/x/report.txt?x=14dad8b1900000 console output: https://syzkaller.appspot.com/x/log.txt?x=10dad8b1900000 kernel config: https://syzkaller.appspot.com/x/.config?x=3d400a47d1416652 dashboard link: https://syzkaller.appspot.com/bug?extid=cc4c0f394e2611edba66 syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15d9de91900000
Reported-by: syzbot+cc4c0f394e2611edba66@syzkaller.appspotmail.com Fixes: e7096c131e51 ("net: WireGuard secure network tunnel")
Having trouble linking this back to wireguard... Those oopses don't have anything to do with it either. Bisection error?
I don't see anything obviously wrong in the bisection log: bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=175ad8b1900000
On the other hand, it looks super precise. It tracked "WARNING in __cfg80211_connect_result" all the way down to the wireguard commit with no flakes or anything.