[RFC 1/2] dlm: drop setting SOCK_NOSPACE
From: Alexander Aring <aahringo@redhat.com>
Date: 2026-10-02 23:21:31
Also in:
gfs2
Subsystem:
distributed lock manager (dlm), filesystems (vfs and infrastructure), the rest · Maintainers:
Alexander Aring, David Teigland, Alexander Viro, Christian Brauner, Linus Torvalds
It makes no sense to set SOCK_NOSPACE here when we have already checked for it. Signed-off-by: Alexander Aring <aahringo@redhat.com> --- fs/dlm/lowcomms.c | 4 ---- 1 file changed, 4 deletions(-)
diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
index 6aa68a24acab..c3a414d2e32b 100644
--- a/fs/dlm/lowcomms.c
+++ b/fs/dlm/lowcomms.c@@ -1391,10 +1391,6 @@ static int send_to_sock(struct connection *con) spin_lock_bh(&con->writequeue_lock); if (test_bit(SOCK_NOSPACE, &con->sock->flags) && !test_and_set_bit(CF_APP_LIMITED, &con->flags)) { - /* Notify TCP that we're limited by the - * application window size. - */ - sk_set_nospace(con->sock->sk); con->sock->sk->sk_write_pending++; clear_bit(CF_SEND_PENDING, &con->flags);
--
2.43.0