From: syzbot <syzbot+1eb4232fca28c0a6d1c2@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,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] KASAN: use-after-free Read in rxrpc_destroy_all_locals
Date: Thu, 08 Dec 2022 15:52:16 -0800 [thread overview]
Message-ID: <0000000000000c17c905ef59bad4@google.com> (raw)
In-Reply-To: <1805058.1670508568@warthog.procyon.org.uk>
Hello,
syzbot has tested the proposed patch but the reproducer is still triggering an issue:
INFO: rcu detected stall in corrupted
rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { P4104 } 2661 jiffies s: 2777 root: 0x0/T
rcu: blocking rcu_node structures (internal RCU debug):
Tested on:
commit: efb7555b rxrpc: Fix I/O thread stop
git tree: https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/ afs-testing
console output: https://syzkaller.appspot.com/x/log.txt?x=16b83997880000
kernel config: https://syzkaller.appspot.com/x/.config?x=fb14358c9774adf3
dashboard link: https://syzkaller.appspot.com/bug?extid=1eb4232fca28c0a6d1c2
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
Note: no patches were applied.
next prev parent reply other threads:[~2022-12-08 23:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-06 16:39 [syzbot] KASAN: use-after-free Read in rxrpc_destroy_all_locals syzbot
2022-12-08 2:37 ` syzbot
2022-12-08 14:09 ` David Howells
2022-12-08 23:52 ` syzbot [this message]
2022-12-09 6:28 ` syzbot
[not found] <20221208045304.8105-1-hdanton@sina.com>
2022-12-08 11:30 ` syzbot
[not found] <20221209014756.1672-1-hdanton@sina.com>
2022-12-09 2:11 ` syzbot
[not found] <20221209030750.1743-1-hdanton@sina.com>
2022-12-09 3:46 ` 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=0000000000000c17c905ef59bad4@google.com \
--to=syzbot+1eb4232fca28c0a6d1c2@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=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.