public inbox for gfs2@lists.linux.dev
 help / color / mirror / Atom feed
From: Alexander Aring <aahringo@redhat.com>
To: teigland@redhat.com
Cc: agruenba@redhat.com, gfs2@lists.linux.dev, aahringo@redhat.com
Subject: [PATCH v6.16-rc7 1/5] dlm: check on unequal 3 to allow more values
Date: Wed, 23 Jul 2025 11:21:52 -0400	[thread overview]
Message-ID: <20250723152156.2988833-2-aahringo@redhat.com> (raw)
In-Reply-To: <20250723152156.2988833-1-aahringo@redhat.com>

Currently everything that is above 3 as dlm_lockspace_release()
parameter is recognized to do everything what 3 does. Currently there is
no defined value above 3 to introduce a new value that does send a uevent
to the user space and adds this value as uevent attribute.

Signed-off-by: Alexander Aring <aahringo@redhat.com>
---
 fs/dlm/lockspace.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/dlm/lockspace.c b/fs/dlm/lockspace.c
index 1929327ffbe1c..ee11a70def92d 100644
--- a/fs/dlm/lockspace.c
+++ b/fs/dlm/lockspace.c
@@ -730,7 +730,7 @@ static int release_lockspace(struct dlm_ls *ls, int force)
 
 	dlm_device_deregister(ls);
 
-	if (force < 3 && dlm_user_daemon_available())
+	if (force != 3 && dlm_user_daemon_available())
 		do_uevent(ls, 0);
 
 	dlm_recoverd_stop(ls);
-- 
2.43.0


  reply	other threads:[~2025-07-23 15:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-23 15:21 [PATCH v6.16-rc7 0/5] dlm: dlm lockspace release option updates Alexander Aring
2025-07-23 15:21 ` Alexander Aring [this message]
2025-07-23 15:21 ` [PATCH v6.16-rc7 2/5] dlm: introduce release parameter defines Alexander Aring
2025-07-23 15:21 ` [PATCH v6.16-rc7 3/5] dlm: add release recover attribute for leaving event Alexander Aring
2025-07-23 15:21 ` [PATCH v6.16-rc7 4/5] dlm: add lockspace member configfs release_recover Alexander Aring
2025-07-23 15:21 ` [PATCH v6.16-rc7 5/5] dlm: introduce DLM_RELEASE_RECOVER 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=20250723152156.2988833-2-aahringo@redhat.com \
    --to=aahringo@redhat.com \
    --cc=agruenba@redhat.com \
    --cc=gfs2@lists.linux.dev \
    --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