From: syzbot <syzbot+c7aabc9fe93e7f3637ba@syzkaller.appspotmail.com>
To: coreteam@netfilter.org, davem@davemloft.net, dhowells@redhat.com,
fw@strlen.de, kadlec@netfilter.org,
linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
pablo@netfilter.org, syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in nf_ct_deliver_cached_events
Date: Thu, 24 Oct 2019 21:20:01 -0700 [thread overview]
Message-ID: <000000000000aecf020595b4762f@google.com> (raw)
In-Reply-To: <00000000000074bc3105958042ef@google.com>
syzbot has bisected this bug to:
commit 2341e0775747864b684abe8627f3d45b167f2940
Author: David Howells <dhowells@redhat.com>
Date: Thu Jun 9 22:02:51 2016 +0000
rxrpc: Simplify connect() implementation and simplify sendmsg() op
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12f869df600000
start commit: 12d61c69 Add linux-next specific files for 20191024
git tree: linux-next
final crash: https://syzkaller.appspot.com/x/report.txt?x=11f869df600000
console output: https://syzkaller.appspot.com/x/log.txt?x=16f869df600000
kernel config: https://syzkaller.appspot.com/x/.config?x=afb75fd8c9fd5ed8
dashboard link: https://syzkaller.appspot.com/bug?extid=c7aabc9fe93e7f3637ba
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10938e18e00000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=147caa97600000
Reported-by: syzbot+c7aabc9fe93e7f3637ba@syzkaller.appspotmail.com
Fixes: 2341e0775747 ("rxrpc: Simplify connect() implementation and simplify
sendmsg() op")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-10-25 4:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 14:03 KASAN: use-after-free Read in nf_ct_deliver_cached_events syzbot
2019-10-24 21:26 ` syzbot
2019-10-25 4:20 ` syzbot [this message]
2019-10-25 6:11 ` Florian Westphal
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=000000000000aecf020595b4762f@google.com \
--to=syzbot+c7aabc9fe93e7f3637ba@syzkaller.appspotmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=fw@strlen.de \
--cc=kadlec@netfilter.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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 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.