From: Daniel Borkmann <dborkman@redhat•com>
To: davem@davemloft•net
Cc: netdev@vger•kernel.org, linux-sctp@vger•kernel.org
Subject: Re: [PATCH net] net: sctp: sctp_transport_destroy{,_rcu}: fix potential pointer corruption
Date: Fri, 09 Aug 2013 12:33:07 +0200 [thread overview]
Message-ID: <5204C563.5030808@redhat.com> (raw)
In-Reply-To: <1376042849-19732-1-git-send-email-dborkman@redhat.com>
On 08/09/2013 12:07 PM, Daniel Borkmann wrote:
> Probably this one is quite unlikely to be triggered, but it's more safe
> to hold a pointer to asoc and packet (instead of dereferencing) and access
> both though this after we have called sctp_transport_destroy_rcu() where
> the transport is being kfree()'d. Introduced by commit 8c98653f ("sctp:
> sctp_close: fix release of bindings for deferred call_rcu's").
>
> Signed-off-by: Daniel Borkmann <dborkman@redhat•com>
Please ignore this, will send an updated v2 in a moment.
prev parent reply other threads:[~2013-08-09 10:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 10:07 [PATCH net] net: sctp: sctp_transport_destroy{,_rcu}: fix potential pointer corruption Daniel Borkmann
2013-08-09 10:33 ` Daniel Borkmann [this message]
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=5204C563.5030808@redhat.com \
--to=dborkman@redhat$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=linux-sctp@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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