public inbox for linux-sctp@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ricardo Cañuelo Navarro" <rcn@igalia.com>
To: Simon Horman <horms@kernel.org>
Cc: Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Xin Long	 <lucien.xin@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet	 <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>,
	Paolo Abeni	 <pabeni@redhat.com>,
	kernel-dev@igalia.com, linux-sctp@vger.kernel.org,
		netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] sctp: check transport existence before processing a send primitive
Date: Wed, 02 Apr 2025 16:03:53 +0200	[thread overview]
Message-ID: <3afa71f8ed15ea4c10b31a4cf41c39ea6edc56cb.camel@igalia.com> (raw)
In-Reply-To: <62dbd9ed967e43e7310cd5333867cfd8930321c4.camel@igalia.com>

By the way, I'm thinking of setting err to -EAGAIN here so that
userspace can retry the send and sctp_sendmsg() will try again to find
a suitable association or create a new one if necessary, but if someone
more knowledgeable about the SCTP implementation has a better
suggestion about what kind of error to return in this scenario, I'd
appreciate it.

Regards,
Ricardo

  reply	other threads:[~2025-04-02 14:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-02 10:25 [PATCH] sctp: check transport existence before processing a send primitive Ricardo Cañuelo Navarro
2025-04-02 13:21 ` Simon Horman
2025-04-02 13:37   ` Ricardo Cañuelo Navarro
2025-04-02 14:03     ` Ricardo Cañuelo Navarro [this message]
2025-04-02 19:40 ` Xin Long
2025-04-03  9:58   ` Ricardo Cañuelo Navarro
2025-04-03 14:42     ` Xin Long
2025-04-03 18:44       ` Xin Long
2025-04-04 10:04         ` Ricardo Cañuelo Navarro
2025-04-04 14:22           ` Xin Long
2025-04-07  7:37             ` Ricardo Cañuelo Navarro

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=3afa71f8ed15ea4c10b31a4cf41c39ea6edc56cb.camel@igalia.com \
    --to=rcn@igalia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kernel-dev@igalia.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stable@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