net: unix: remove outdated BSD behavior comment in unix_release_sock()

Remove the long-standing comment in unix_release_sock() that described a
behavioral difference between Linux and BSD regarding when ECONNRESET is
sent to connected UNIX sockets upon closure.

As confirmed by testing on macOS (similar to BSD behavior), ECONNRESET
is only observed for SOCK_DGRAM sockets, not for SOCK_STREAM. Meanwhile,
Linux already returns ECONNRESET in cases where a socket is closed with
unread data or is not yet accept()ed. This means the previous comment no
longer accurately describes current behavior and is misleading.

Suggested-by: Kuniyuki Iwashima <kuniyu@google.com>
Signed-off-by: Sunday Adelodun <adelodunolaoluwa@yahoo.com>
Reviewed-by: Kuniyuki Iwashima <kuniyu@google.com>
Link: https://patch.msgid.link/20251021195906.20389-1-adelodunolaoluwa@yahoo.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>

diff --git a/net/unix/af_unix.c b/net/unix/af_unix.c
index 768098dec2310008632558ae928703b37c3cc8ef..54177caa9c12c315e313da2dcf4ee7ed00f44255 100644 (file)
--- a/net/unix/af_unix.c
+++ b/net/unix/af_unix.c
@@ -733,17 +733,6 @@ static void unix_release_sock(struct sock *sk, int embrion)
 
        /* ---- Socket is dead now and most probably destroyed ---- */
 
-       /*
-        * Fixme: BSD difference: In BSD all sockets connected to us get
-        *        ECONNRESET and we die on the spot. In Linux we behave
-        *        like files and pipes do and wait for the last
-        *        dereference.
-        *
-        * Can't we simply set sock->err?
-        *
-        *        What the above comment does talk about? --ANK(980817)
-        */
-
        if (READ_ONCE(unix_tot_inflight))
                unix_gc();              /* Garbage collect fds */
 }