From: Alexander Aring <aahringo@redhat.com>
To: teigland@redhat.com
Cc: gfs2@lists.linux.dev, song@kernel.org, yukuai3@huawei.com,
agruenba@redhat.com, mark@fasheh.com, jlbec@evilplan.org,
joseph.qi@linux.alibaba.com, gregkh@linuxfoundation.org,
rafael@kernel.org, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
ocfs2-devel@lists.linux.dev, netdev@vger.kernel.org,
vvidic@valentin-vidic.from.hr, heming.zhao@suse.com,
lucien.xin@gmail.com, donald.hunter@gmail.com,
aahringo@redhat.com
Subject: [PATCHv2 dlm/next 01/12] dlm: introduce dlm_find_lockspace_name()
Date: Mon, 30 Sep 2024 16:13:47 -0400 [thread overview]
Message-ID: <20240930201358.2638665-2-aahringo@redhat.com> (raw)
In-Reply-To: <20240930201358.2638665-1-aahringo@redhat.com>
A DLM lockspace can be either identified by it's unique id or name. Later
patches will introduce a new netlink api that is using a unique
lockspace name to identify a lockspace in the lslist. This is mostly
required for sysfs functionality that is currently solved by a per
lockspace kobject allocation. The new netlink api cannot simple lookup
the lockspace by a container_of() call to do whatever sysfs is
providing so we introduce dlm_find_lockspace_name() to offer such
functionality.
Signed-off-by: Alexander Aring <aahringo@redhat.com>
---
fs/dlm/lockspace.c | 18 ++++++++++++++++++
fs/dlm/lockspace.h | 1 +
2 files changed, 19 insertions(+)
diff --git a/fs/dlm/lockspace.c b/fs/dlm/lockspace.c
index 8afac6e2dff0..00d37125bc44 100644
--- a/fs/dlm/lockspace.c
+++ b/fs/dlm/lockspace.c
@@ -238,6 +238,24 @@ void dlm_lockspace_exit(void)
kset_unregister(dlm_kset);
}
+struct dlm_ls *dlm_find_lockspace_name(const char *lsname)
+{
+ struct dlm_ls *ls;
+
+ spin_lock_bh(&lslist_lock);
+
+ list_for_each_entry(ls, &lslist, ls_list) {
+ if (!strncmp(ls->ls_name, lsname, DLM_LOCKSPACE_LEN)) {
+ atomic_inc(&ls->ls_count);
+ goto out;
+ }
+ }
+ ls = NULL;
+ out:
+ spin_unlock_bh(&lslist_lock);
+ return ls;
+}
+
struct dlm_ls *dlm_find_lockspace_global(uint32_t id)
{
struct dlm_ls *ls;
diff --git a/fs/dlm/lockspace.h b/fs/dlm/lockspace.h
index 47ebd4411926..7898a906aab9 100644
--- a/fs/dlm/lockspace.h
+++ b/fs/dlm/lockspace.h
@@ -22,6 +22,7 @@
int dlm_lockspace_init(void);
void dlm_lockspace_exit(void);
+struct dlm_ls *dlm_find_lockspace_name(const char *lsname);
struct dlm_ls *dlm_find_lockspace_global(uint32_t id);
struct dlm_ls *dlm_find_lockspace_local(void *id);
struct dlm_ls *dlm_find_lockspace_device(int minor);
--
2.43.0
next prev parent reply other threads:[~2024-09-30 20:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 20:13 [PATCHv2 dlm/next 00/12] dlm: net-namespace functionality Alexander Aring
2024-09-30 20:13 ` Alexander Aring [this message]
2024-09-30 20:13 ` [PATCHv2 dlm/next 02/12] dlm: disallow different configs nodeid storages Alexander Aring
2024-09-30 20:13 ` [PATCHv2 dlm/next 03/12] dlm: add struct net to dlm_new_lockspace() Alexander Aring
2024-09-30 20:13 ` [PATCHv2 dlm/next 04/12] dlm: handle port as __be16 network byte order Alexander Aring
2024-09-30 20:13 ` [PATCHv2 dlm/next 05/12] dlm: use dlm_config as only cluster configuration Alexander Aring
2024-09-30 20:13 ` [PATCHv2 dlm/next 06/12] dlm: dlm_config_info config fields to unsigned int Alexander Aring
2024-09-30 20:13 ` [PATCHv2 dlm/next 07/12] dlm: rename config to configfs Alexander Aring
2024-09-30 20:13 ` [PATCHv2 dlm/next 08/12] kobject: add kset_type_create_and_add() helper Alexander Aring
2024-09-30 20:13 ` [PATCHv2 dlm/next 09/12] kobject: export generic helper ops Alexander Aring
2024-09-30 20:13 ` [PATCHv2 dlm/next 10/12] dlm: separate dlm lockspaces per net-namespace Alexander Aring
2024-10-11 6:19 ` kernel test robot
2024-09-30 20:13 ` [PATCHv2 dlm/next 11/12] dlm: add nldlm net-namespace aware UAPI Alexander Aring
2024-09-30 20:22 ` Alexander Aring
2024-09-30 20:13 ` [PATCHv2 dlm/next 12/12] gfs2: separate mount context by net-namespaces Alexander Aring
2024-09-30 20:39 ` [PATCHv2 dlm/next 00/12] dlm: net-namespace functionality John Stoffel
2024-10-01 0:09 ` 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=20240930201358.2638665-2-aahringo@redhat.com \
--to=aahringo@redhat.com \
--cc=agruenba@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=donald.hunter@gmail.com \
--cc=gfs2@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=heming.zhao@suse.com \
--cc=jlbec@evilplan.org \
--cc=joseph.qi@linux.alibaba.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=lucien.xin@gmail.com \
--cc=mark@fasheh.com \
--cc=netdev@vger.kernel.org \
--cc=ocfs2-devel@lists.linux.dev \
--cc=rafael@kernel.org \
--cc=song@kernel.org \
--cc=teigland@redhat.com \
--cc=vvidic@valentin-vidic.from.hr \
--cc=yukuai3@huawei.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;
as well as URLs for NNTP newsgroup(s).