From: syzbot <syzbot+5013d47539cdd43e7098@syzkaller.appspotmail.com>
To: ast@kernel.org, aviadye@mellanox.com, borisp@mellanox.com,
bpf@vger.kernel.org, daniel@iogearbox.net, davejwatson@fb.com,
davem@davemloft.net, dirk.vandermerwe@netronome.com,
edumazet@google.com, eranbe@mellanox.com, eric.dumazet@gmail.com,
jakub.kicinski@netronome.com, john.fastabend@gmail.com,
kafai@fb.com, kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, songliubraving@fb.com,
syzkaller-bugs@googlegroups.com, yhs@fb.com,
yoshfuji@linux-ipv6.org
Subject: Re: kernel BUG at include/linux/mm.h:LINE! (5)
Date: Fri, 06 Dec 2019 02:14:00 -0800 [thread overview]
Message-ID: <000000000000fdad650599064dc5@google.com> (raw)
In-Reply-To: <00000000000054cc6d05834c33d7@google.com>
syzbot suspects this bug was fixed by commit:
commit 9354544cbccf68da1b047f8fb7b47630e3c8a59d
Author: Dirk van der Merwe <dirk.vandermerwe@netronome.com>
Date: Mon Jun 24 04:26:58 2019 +0000
net/tls: fix page double free on TX cleanup
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12ebd77ae00000
start commit: 9e9322e5 selftest/net: Remove duplicate header
git tree: net-next
kernel config: https://syzkaller.appspot.com/x/.config?x=47f2db597668ac40
dashboard link: https://syzkaller.appspot.com/bug?extid=5013d47539cdd43e7098
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=148763eb200000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1416ff3d200000
If the result looks correct, please mark the bug fixed by replying with:
#syz fix: net/tls: fix page double free on TX cleanup
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-12-06 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 22:23 kernel BUG at include/linux/mm.h:LINE! (5) syzbot
2019-03-05 17:54 ` Eric Dumazet
2019-03-11 13:23 ` syzbot
2019-12-06 10:14 ` syzbot [this message]
2019-12-06 17:58 ` Jakub Kicinski
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=000000000000fdad650599064dc5@google.com \
--to=syzbot+5013d47539cdd43e7098@syzkaller.appspotmail.com \
--cc=ast@kernel.org \
--cc=aviadye@mellanox.com \
--cc=borisp@mellanox.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davejwatson@fb.com \
--cc=davem@davemloft.net \
--cc=dirk.vandermerwe@netronome.com \
--cc=edumazet@google.com \
--cc=eranbe@mellanox.com \
--cc=eric.dumazet@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=yhs@fb.com \
--cc=yoshfuji@linux-ipv6.org \
/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.