From: Michael Tuexen <Michael.Tuexen@lurchi.franken.de>
To: linux-sctp@vger.kernel.org
Subject: Re: EAGAIN
Date: Sun, 07 Jun 2020 15:17:45 +0000 [thread overview]
Message-ID: <5F3CF6C8-1FE3-48C5-8E6C-2EC35E0E2FBF@lurchi.franken.de> (raw)
In-Reply-To: <0D6B7E65-36EC-4132-B02C-0371099E480A@list.fink.org>
> On 7. Jun 2020, at 16:04, David Laight <David.Laight@ACULAB.COM> wrote:
>
> From: Michael Tuexen
>> Sent: 07 June 2020 13:48
> ...
>> If you killed the peer, I would assume that there is an SCTP message containing an
>> ABORT chunk in the wire. Is that true? If that is true, you could subscribe to
>> SCTP_ASSOC_CHANGE notification, which should tell you.
>
> Actually for TCP-style 1-1 connections you must subscribe to
> SCTP_ASSOC_CHANGE.
I guess you are referring to UDP (1-to-many) style sockets.
For 1-to-1 style sockets, the normal error handling should
work, like it does for TCP (returning -1 in a system call
and errno being ETIMEDOUT or ECONNRESET). At least this is
the way intended by the specification and I think Linux
does it that way.
Best regards
Michael
>
> If you don't and the far end is killed (eg kernel crash) and
> restarts with the same port number pair then you get no
> indication that everything has disconnected and reconnected.
>
> David
>
> -
> Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
> Registration No: 1397386 (Wales)
>
next prev parent reply other threads:[~2020-06-07 15:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 12:18 EAGAIN Andreas Fink
2020-06-07 12:47 ` EAGAIN Michael Tuexen
2020-06-07 12:59 ` EAGAIN Andreas Fink
2020-06-07 13:46 ` EAGAIN Michael Tuexen
2020-06-07 14:04 ` EAGAIN David Laight
2020-06-07 15:17 ` Michael Tuexen [this message]
2020-06-07 17:05 ` EAGAIN David Laight
2020-06-07 17:31 ` EAGAIN Michael Tuexen
2020-06-08 6:13 ` EAGAIN Andreas Fink
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=5F3CF6C8-1FE3-48C5-8E6C-2EC35E0E2FBF@lurchi.franken.de \
--to=michael.tuexen@lurchi.franken.de \
--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 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).