public inbox for linux-efi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: linux-efi@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: Ard Biesheuvel <ardb@kernel.org>,
	Christian Brauner <brauner@kernel.org>,
	Al Viro <viro@zeniv.linux.org.uk>
Subject: [RFC PATCH 2/3] libfs: add simple directory iteration function with callback
Date: Tue, 18 Mar 2025 15:41:10 -0400	[thread overview]
Message-ID: <20250318194111.19419-3-James.Bottomley@HansenPartnership.com> (raw)
In-Reply-To: <20250318194111.19419-1-James.Bottomley@HansenPartnership.com>

The current iterate_dir() infrastructure is somewhat cumbersome to use
from within the kernel.  Introduce a lighter weight
simple_iterate_dir() function that directly iterates the directory and
executes a callback for each positive dentry.

Signed-off-by: James Bottomley <James.Bottomley@HansenPartnership.com>
---
 fs/libfs.c         | 33 +++++++++++++++++++++++++++++++++
 include/linux/fs.h |  2 ++
 2 files changed, 35 insertions(+)

diff --git a/fs/libfs.c b/fs/libfs.c
index 816bfe6c0430..37da5fe25242 100644
--- a/fs/libfs.c
+++ b/fs/libfs.c
@@ -214,6 +214,39 @@ static void internal_readdir(struct dentry *dentry, struct dentry *cursor,
 	dput(next);
 }
 
+/**
+ * generic_iterate_call - iterate all entries executing @callback
+ *
+ * @dir: directory to iterate over
+ * @data: data passed to callback
+ * @callback: callback to call
+ *
+ * Iterates over all positive dentries that are direct children of
+ * @dir (so doesn't include . and ..) and executes the callback for
+ * each of them.  Note that because there's no struct *mnt, the caller
+ * is responsible for pinning the filesystem.
+ *
+ * If the @callback returns true, the iteration will continue and if
+ * it returns @false, it will stop (note that since the cursor is
+ * destroyed the next invocation will go back to the beginning again).
+ *
+ */
+int simple_iterate_call(struct dentry *dir, void *data,
+			bool (*callback)(void *, struct dentry *))
+{
+	struct dentry *cursor = d_alloc_cursor(dir);
+
+	if (!cursor)
+		return -ENOMEM;
+
+	internal_readdir(dir, cursor, data, true, callback);
+
+	dput(cursor);
+
+	return 0;
+}
+EXPORT_SYMBOL(simple_iterate_call);
+
 static bool dcache_readdir_callback(void *data, struct dentry *entry)
 {
 	struct dir_context *ctx = data;
diff --git a/include/linux/fs.h b/include/linux/fs.h
index 2788df98080f..a84896f0b2d1 100644
--- a/include/linux/fs.h
+++ b/include/linux/fs.h
@@ -3531,6 +3531,8 @@ extern int simple_rename(struct mnt_idmap *, struct inode *,
 			 unsigned int);
 extern void simple_recursive_removal(struct dentry *,
                               void (*callback)(struct dentry *));
+extern int simple_iterate_call(struct dentry *dir, void *data,
+			       bool (*callback)(void *, struct dentry *));
 extern int noop_fsync(struct file *, loff_t, loff_t, int);
 extern ssize_t noop_direct_IO(struct kiocb *iocb, struct iov_iter *iter);
 extern int simple_empty(struct dentry *);
-- 
2.43.0


  parent reply	other threads:[~2025-03-18 19:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-18 19:41 [RFC PATCH 0/3] create simple libfs directory iterator and make efivarfs use it James Bottomley
2025-03-18 19:41 ` [RFC PATCH 1/3] libfs: rework dcache_readdir to use an internal function with callback James Bottomley
2025-03-18 21:32   ` Ard Biesheuvel
2025-03-18 21:49     ` James Bottomley
2025-03-18 19:41 ` James Bottomley [this message]
2025-03-18 21:33   ` [RFC PATCH 2/3] libfs: add simple directory iteration " Ard Biesheuvel
2025-03-18 21:50     ` James Bottomley
2025-03-18 19:41 ` [RFC PATCH 3/3] efivarfs: replace iterate_dir with libfs function simple_iterate_call James Bottomley
2025-03-18 21:34   ` Ard Biesheuvel
2025-03-18 23:45 ` [RFC PATCH 0/3] create simple libfs directory iterator and make efivarfs use it Al Viro
2025-03-18 23:49   ` Al Viro
2025-03-19 16:46   ` James Bottomley
2025-03-19 18:45     ` James Bottomley

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=20250318194111.19419-3-James.Bottomley@HansenPartnership.com \
    --to=james.bottomley@hansenpartnership.com \
    --cc=ardb@kernel.org \
    --cc=brauner@kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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