From: vienna-0FFH <viennaoffh@gmail.com>
To: Alexander Aring <aahringo@redhat.com>,
David Teigland <teigland@redhat.com>
Cc: gfs2@lists.linux.dev, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, viennaoffh@gmail.com,
syzbot+04dfbd15d442517e713a@syzkaller.appspotmail.com
Subject: [PATCH] dlm: don't warn when closing a node without a connection
Date: Wed, 14 Oct 2026 17:02:37 +0800 [thread overview]
Message-ID: <20261014090237.395-1-viennaoffh@gmail.com> (raw)
Opening and closing a configfs comm entry without ever configuring an
address for it triggers the following warning:
mkdir /sys/kernel/config/dlm/cluster
mkdir /sys/kernel/config/dlm/cluster/comms/1
rmdir /sys/kernel/config/dlm/cluster/comms/1
dlm: closing connection to node 1
------------[ cut here ]------------
!con
WARNING: fs/dlm/lowcomms.c:1455 at dlm_lowcomms_close+0x12d/0x470, CPU#1
Since commit 6f0b0b5d7ae7 ("fs: dlm: remove dlm_node_addrs lookup list")
the lowcomms connection has the same lifetime as the configfs comm
entry, but a connection is only created when an address is configured
via the addr attribute. Removing a comm entry for which no address was
ever set up is valid and the resulting close call has simply nothing
to do, so it must not warn.
Reported-by: syzbot+04dfbd15d442517e713a@syzkaller.appspotmail.com
Closes: https://syzkaller.appspot.com/bug?extid=04dfbd15d442517e713a
Fixes: 6f0b0b5d7ae7 ("fs: dlm: remove dlm_node_addrs lookup list")
Cc: stable@vger.kernel.org
Signed-off-by: vienna-0FFH <viennaoffh@gmail.com>
---
fs/dlm/lowcomms.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/fs/dlm/lowcomms.c b/fs/dlm/lowcomms.c
index 2aff1c7..86c7af9 100644
--- a/fs/dlm/lowcomms.c
+++ b/fs/dlm/lowcomms.c
@@ -1452,7 +1452,11 @@ int dlm_lowcomms_close(int nodeid)
idx = srcu_read_lock(&connections_srcu);
con = nodeid2con(nodeid, 0);
- if (WARN_ON_ONCE(!con)) {
+ /* case of dlm_midcomms_close() for a node which never had an
+ * address configured, so no connection was ever created and
+ * there is nothing to close
+ */
+ if (!con) {
srcu_read_unlock(&connections_srcu, idx);
return -ENOENT;
}
--
2.43.0
next reply other threads:[~2026-10-14 9:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 9:02 vienna-0FFH [this message]
2026-10-14 11:49 ` Greg KH
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=20261014090237.395-1-viennaoffh@gmail.com \
--to=viennaoffh@gmail.com \
--cc=aahringo@redhat.com \
--cc=gfs2@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+04dfbd15d442517e713a@syzkaller.appspotmail.com \
--cc=teigland@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
all inboxes | Powered by JetHome®