Netdev List
 help / color / mirror / Atom feed
From: Alexander Aring <aahringo@redhat.com>
To: edumazet@kernel.org
Cc: aahringo@redhat.com, gfs2@lists.linux.dev,
	netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	pabeni@redhat.com
Subject: [RFC 0/2] dlm: fix socket hang on send buffer limitation with socket error
Date: Fri,  2 Oct 2026 19:21:05 -0400	[thread overview]
Message-ID: <20261002232107.1578646-1-aahringo@redhat.com> (raw)

Hi,

This patch series is based on Eric Dumazet's series [0] cleaning up
and fixing kernel users of SOCK_NOSPACE handling. His series pointed out
that DLM socket handling can get stuck when the socket send buffer limit
is reached and a socket error occurs simultaneously.

This patch series provides a fix for this behavior. I was able to reproduce
the scenario and trigger the hang locally. With these patches applied on
top of Eric's series, I can no longer reproduce the issue.

Please feel free to review and take these patches if they look reasonable.

- Alex

[0] https://lore.kernel.org/netdev/20260929071743.23624-1-edumazet@kernel.org/

Alexander Aring (2):
  dlm: drop setting SOCK_NOSPACE
  dlm: fix socket hang on send buffer limitation with socket error

 fs/dlm/lowcomms.c | 50 ++++++++++++++++++++++++++++++++++-------------
 1 file changed, 36 insertions(+), 14 deletions(-)

-- 
2.43.0


             reply	other threads:[~2026-10-02 23:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02 23:21 Alexander Aring [this message]
2026-10-02 23:21 ` [RFC 1/2] dlm: drop setting SOCK_NOSPACE Alexander Aring
2026-10-02 23:21 ` [RFC 2/2] dlm: fix socket hang on send buffer limitation with socket error Alexander Aring
2026-10-05 14:53   ` Alexander Aring

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=20261002232107.1578646-1-aahringo@redhat.com \
    --to=aahringo@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=gfs2@lists.linux.dev \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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