linux-kernel - Re: [PATCH] sctp: check transport existence before processing a send primitive

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3afa71f8ed15ea4c10b31a4cf41c39ea6edc56cb.camel@igalia.com>
Date: Wed, 02 Apr 2025 16:03:53 +0200
From: Ricardo Cañuelo Navarro <rcn@...lia.com>
To: Simon Horman <horms@...nel.org>
Cc: Marcelo Ricardo Leitner <marcelo.leitner@...il.com>, Xin Long	
 <lucien.xin@...il.com>, "David S. Miller" <davem@...emloft.net>, Eric
 Dumazet	 <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, Paolo
 Abeni	 <pabeni@...hat.com>, kernel-dev@...lia.com,
 linux-sctp@...r.kernel.org, 	netdev@...r.kernel.org,
 linux-kernel@...r.kernel.org, stable@...r.kernel.org
Subject: Re: [PATCH] sctp: check transport existence before processing a
 send primitive

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