From: David Howells <dhowells@redhat.com>
To: Hillf Danton <hdanton@sina.com>
Cc: dhowells@redhat.com,
syzbot <syzbot+eed305768ece6682bb7f@syzkaller.appspotmail.com>,
davem@davemloft.net, linux-afs@lists.infradead.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: KASAN: use-after-free Read in rxrpc_release_call
Date: Fri, 04 Oct 2019 15:40:04 +0100 [thread overview]
Message-ID: <17922.1570200004@warthog.procyon.org.uk> (raw)
In-Reply-To: <20190921122737.14884-1-hdanton@sina.com>
Hillf Danton <hdanton@sina.com> wrote:
> if (conn) {
> - rxrpc_disconnect_call(call);
> conn->security->free_call_crypto(call);
> + rxrpc_disconnect_call(call);
> }
Better to cache the security pointer in the call struct, I think.
David
next parent reply other threads:[~2019-10-04 14:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190921122737.14884-1-hdanton@sina.com>
2019-10-04 14:40 ` David Howells [this message]
2019-08-23 14:42 KASAN: use-after-free Read in rxrpc_release_call syzbot
2019-09-21 11:08 ` syzbot
2019-09-21 17:41 ` 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=17922.1570200004@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=davem@davemloft.net \
--cc=hdanton@sina.com \
--cc=linux-afs@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=syzbot+eed305768ece6682bb7f@syzkaller.appspotmail.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