From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: Vlad Yasevich <vyasevich@gmail.com>,
Xin Long <lucien.xin@gmail.com>,
network dev <netdev@vger.kernel.org>,
linux-sctp@vger.kernel.org
Cc: vyasevic@redhat.com, davem@davemloft.net
Subject: Re: [PATCH net] sctp: sctp should release assoc when sctp_make_abort_user return NULL in sctp_close
Date: Thu, 17 Dec 2015 17:01:15 -0200 [thread overview]
Message-ID: <5673067B.6080001@gmail.com> (raw)
In-Reply-To: <5672FF06.2030803@gmail.com>
Em 17-12-2015 16:29, Vlad Yasevich escreveu:
> On 12/17/2015 09:30 AM, Xin Long wrote:
>> In sctp_close, sctp_make_abort_user may return NULL because of memory
>> allocation failure. If this happens, it will bypass any state change
>> and never free the assoc. The assoc has no chance to be freed and it
>> will be kept in memory with the state it had even after the socket is
>> closed by sctp_close().
>>
>> So if sctp_make_abort_user fails to allocate memory, we should just
>> free the asoc, as there isn't much else that we can do.
>>
>> Signed-off-by: Xin Long <lucien.xin@gmail.com>
>> Acked-by: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
>> ---
>> net/sctp/socket.c | 6 +++++-
>> 1 file changed, 5 insertions(+), 1 deletion(-)
>>
>> diff --git a/net/sctp/socket.c b/net/sctp/socket.c
>> index 9b6cc6d..267b8f8 100644
>> --- a/net/sctp/socket.c
>> +++ b/net/sctp/socket.c
>> @@ -1513,8 +1513,12 @@ static void sctp_close(struct sock *sk, long timeout)
>> struct sctp_chunk *chunk;
>>
>> chunk = sctp_make_abort_user(asoc, NULL, 0);
>> - if (chunk)
>> + if (chunk) {
>> sctp_primitive_ABORT(net, asoc, chunk);
>> + } else {
>> + sctp_unhash_established(asoc);
>> + sctp_association_free(asoc);
>> + }
>
> I don't think you can do that for an association that has not been closed.
>
> I think a cleaner approach might be to update abort primitive handlers
> to handle a NULL chunk value and unconditionally call the primitive.
>
> This guarantees that any timers or waitqueues that might be active are
> stopped correctly.
sctp_association_free() is the one who does that job, even that way. All
in between the primitive call and then the call to
sctp_association_free() is just status changes and packet xmit, which
doing this way we cut out when we are in memory pressure. pkt xmit or
ULP events are likely going to fail too anyway.
sctp_sf_do_9_1_prm_abort() -> SCTP_CMD_ASSOC_FAILED ->
sctp_cmd_assoc_failed -> ULP events, send abort, and
SCTP_CMD_DELETE_TCB ->
sctp_cmd_delete_tcb ->
sctp_unhash_established(asoc);
sctp_association_free(asoc);
and returns.
There is a check on sctp_cmd_delete_tcb() that avoids calling that on
temp assocs on listening sockets, but that condition is false due to the
check on sk_shutdown so it will call those two functions anyway.
Marcelo
next prev parent reply other threads:[~2015-12-17 19:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-17 14:30 [PATCH net] sctp: sctp should release assoc when sctp_make_abort_user return NULL in sctp_close Xin Long
2015-12-17 18:29 ` Vlad Yasevich
2015-12-17 19:01 ` Marcelo Ricardo Leitner [this message]
2015-12-17 19:33 ` Vlad Yasevich
2015-12-18 14:08 ` Vlad Yasevich
2015-12-18 16:23 ` Marcelo Ricardo Leitner
2015-12-21 9:56 ` Xin Long
2015-12-21 13:45 ` Marcelo Ricardo Leitner
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=5673067B.6080001@gmail.com \
--to=marcelo.leitner@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-sctp@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=vyasevic@redhat.com \
--cc=vyasevich@gmail.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).