From: syzbot <syzbot+4bb6356bb29d6299360e@syzkaller.appspotmail.com>
To: davem@davemloft.net, dhowells@redhat.com, edumazet@google.com,
kuba@kernel.org, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org, marc.dionne@auristor.com,
netdev@vger.kernel.org, pabeni@redhat.com,
roman.gushchin@linux.dev, shakeelb@google.com,
shaozhengchao@huawei.com, syzkaller-bugs@googlegroups.com,
vasily.averin@linux.dev
Subject: Re: [syzbot] kernel BUG in rxrpc_put_call
Date: Tue, 10 Jan 2023 03:45:22 -0800 [thread overview]
Message-ID: <0000000000003a0d7d05f1e76b4d@google.com> (raw)
In-Reply-To: <00000000000024d6fc05f1d9b858@google.com>
syzbot has bisected this issue to:
commit a275da62e8c111b897b9cb73eb91df2f4e475ca5
Author: David Howells <dhowells@redhat.com>
Date: Mon Oct 10 07:45:20 2022 +0000
rxrpc: Create a per-local endpoint receive queue and I/O thread
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=12ba382c480000
start commit: 60ea6f00c57d net: ipa: correct IPA v4.7 IMEM offset
git tree: net
final oops: https://syzkaller.appspot.com/x/report.txt?x=11ba382c480000
console output: https://syzkaller.appspot.com/x/log.txt?x=16ba382c480000
kernel config: https://syzkaller.appspot.com/x/.config?x=46221e8203c7aca6
dashboard link: https://syzkaller.appspot.com/bug?extid=4bb6356bb29d6299360e
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=141826f6480000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=15a8642c480000
Reported-by: syzbot+4bb6356bb29d6299360e@syzkaller.appspotmail.com
Fixes: a275da62e8c1 ("rxrpc: Create a per-local endpoint receive queue and I/O thread")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-01-10 11:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 19:24 [syzbot] kernel BUG in rxrpc_put_call syzbot
2023-01-10 11:45 ` syzbot [this message]
2023-01-11 9:26 ` David Howells
2023-01-11 9:26 ` syzbot
2023-01-11 9:41 ` David Howells
2023-01-11 16:50 ` 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=0000000000003a0d7d05f1e76b4d@google.com \
--to=syzbot+4bb6356bb29d6299360e@syzkaller.appspotmail.com \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.dionne@auristor.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=roman.gushchin@linux.dev \
--cc=shakeelb@google.com \
--cc=shaozhengchao@huawei.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=vasily.averin@linux.dev \
/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).