All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>
To: linux-sctp@vger.kernel.org
Subject: Re: sctp_getpaddrs() on a SHUTDOWN association
Date: Sat, 14 May 2016 02:29:23 +0000	[thread overview]
Message-ID: <20160514022923.GC13980@localhost.localdomain> (raw)
In-Reply-To: <20160513103533.GH3043@timmy>

Hi,

On Fri, May 13, 2016 at 12:35:33PM +0200, Adam Endrodi wrote:
> 
> Hi there,
> 
> 
> I've got a simple case: a multi-homed client connects to a server, then
> disconnects right away.  On the server side we receive the SCTP_COMM_UP
> notification and try to get the client's addresses with sctp_getpaddrs().
> But since the L3 connection has been SHUTDOWN properly the function fails
> with EINVAL.
> 
> Unfortunately accept(2) only returns the first address of the client.
> 
> I have a 3.13.0-37.64 generic kernel from Ubuntu, but the affected code
> path seems to be the same as in kernel 4.4.
> 
> Do you happen to have an idea how to work it around and obtain the client's
> addresses after the associtation has been SHUTDOWN?  I've made the client
> wait a little before closing the connection, but I don't like it.
> 
> Thanks,
> adam

Not to work around, as that seems just impossible.

But one idea to improve it would be to not schedule SCTP_CMD_DELETE_TCB
right on sctp_sf_do_4_C() but when that event:
        ev = sctp_ulpevent_make_assoc_change(asoc, 0, SCTP_SHUTDOWN_COMP, 
                                             0, 0, 0, NULL, GFP_ATOMIC);  
is consumed by the application, or right away if the event allocation
fails.

I didn't check for possible side-effects of this change, btw.

  Marcelo


      reply	other threads:[~2016-05-14  2:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-13 10:35 sctp_getpaddrs() on a SHUTDOWN association Adam Endrodi
2016-05-14  2:29 ` Marcelo Ricardo Leitner [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=20160514022923.GC13980@localhost.localdomain \
    --to=marcelo.leitner@gmail.com \
    --cc=linux-sctp@vger.kernel.org \
    /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.