From: syzbot <syzbot+193e29e9387ea5837f1d@syzkaller.appspotmail.com>
To: arvid.brodin@alten.se, davem@davemloft.net, dhowells@redhat.com,
dirk.vandermerwe@netronome.com, edumazet@google.com,
jakub.kicinski@netronome.com, jiri@mellanox.com,
john.hurley@netronome.com, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
oss-drivers@netronome.com, syzkaller-bugs@googlegroups.com
Subject: Re: BUG: corrupted list in rxrpc_local_processor
Date: Mon, 12 Aug 2019 15:32:00 -0700 [thread overview]
Message-ID: <000000000000ac9048058ff3176e@google.com> (raw)
In-Reply-To: <000000000000492086058fad2979@google.com>
syzbot has bisected this bug to:
commit 427545b3046326cd7b4dbbd7869f08737df2ad2b
Author: Jakub Kicinski <jakub.kicinski@netronome.com>
Date: Tue Jul 9 02:53:12 2019 +0000
nfp: tls: count TSO segments separately for the TLS offload
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11d04eee600000
start commit: 125b7e09 net: tc35815: Explicitly check NET_IP_ALIGN is no..
git tree: net
final crash: https://syzkaller.appspot.com/x/report.txt?x=13d04eee600000
console output: https://syzkaller.appspot.com/x/log.txt?x=15d04eee600000
kernel config: https://syzkaller.appspot.com/x/.config?x=a4c9e9f08e9e8960
dashboard link: https://syzkaller.appspot.com/bug?extid=193e29e9387ea5837f1d
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=159d4eba600000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=16ba194a600000
Reported-by: syzbot+193e29e9387ea5837f1d@syzkaller.appspotmail.com
Fixes: 427545b30463 ("nfp: tls: count TSO segments separately for the TLS
offload")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2019-08-12 22:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 11:06 BUG: corrupted list in rxrpc_local_processor syzbot
2019-08-12 10:20 ` syzbot
2019-08-12 22:32 ` syzbot [this message]
2019-08-12 22:40 ` Jakub Kicinski
2019-08-12 22:41 ` David Howells
2019-08-13 0:51 ` syzbot
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=000000000000ac9048058ff3176e@google.com \
--to=syzbot+193e29e9387ea5837f1d@syzkaller.appspotmail.com \
--cc=arvid.brodin@alten.se \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dirk.vandermerwe@netronome.com \
--cc=edumazet@google.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=john.hurley@netronome.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.com \
--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;
as well as URLs for NNTP newsgroup(s).