From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: linux-efi@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Ard Biesheuvel <ardb@kernel.org>,
Christian Brauner <brauner@kernel.org>
Subject: Re: [RFC PATCH 0/3] create simple libfs directory iterator and make efivarfs use it
Date: Wed, 19 Mar 2025 12:46:10 -0400 [thread overview]
Message-ID: <70ba7c8e2cdc4c76f71274c9aaf77b360692613d.camel@HansenPartnership.com> (raw)
In-Reply-To: <20250318234505.GY2023217@ZenIV>
On Tue, 2025-03-18 at 23:45 +0000, Al Viro wrote:
[...]
> I suspect that you are making it too generic for its own good.
>
> dcache_readdir() needs to cope with the situation when there are
> fuckloads of opened-and-unliked files in there. That's why we
> play those games with cursors under if (need_resched()) there.
Yes, but those games will never really activate for the efivarfs code
because we expect to be mostly positive. What I was aiming for was to
make sure there's no duplication of the subtle code, so someone can't
forget to update it in two places, so doing a callback approach seemed
natural.
> That's not the case for efivarfs. There you really want just
> "grab a reference to the next positive, drop the reference we
> were given" and that's it.
>
> IOW, find_next_child() instead of scan_positives(). Export that
> and it becomes just a simple loop -
> child = NULL;
> while ((child = find_next_child(parent, child)) != NULL) {
> struct inode *inode = d_inode(child);
> struct efivar_entry *entry = efivar_entry(inode);
>
> err = efivar_entry_size(entry, &size);
>
> inode_lock(inode);
> i_size_write(inode, err ? 0 : size + sizeof(__u32));
> inode_unlock(inode);
>
> if (err)
> simple_recursive_removal(child, NULL);
> }
> and that's it. No callbacks, no cursors, no iterators - just an
> export of helper already there.
So we don't mind the callbacks; we have to do it for efivar_init()
lower down anyway. However, I did take a cut at doing this based on
simple positive (see below). I assume you won't like the way I have to
allocate and toss a cursor for each iteration, nor the fact that
there's still the cond_resched() in there? I think I can fix that but
I'd have to slice apart simple_positive(), which is a bigger
undertaking.
> And we might want a better function name than that...
I went for simple_next_child() ...
Regards,
James
---
fs/libfs.c | 41 +++++++++++++++++++++++++++++++++++++++++
include/linux/fs.h | 2 ++
2 files changed, 43 insertions(+)
diff --git a/fs/libfs.c b/fs/libfs.c
index 8444f5cc4064..86f29cc2b85a 100644
--- a/fs/libfs.c
+++ b/fs/libfs.c
@@ -146,6 +146,47 @@ static struct dentry *scan_positives(struct dentry *cursor,
return found;
}
+/**
+ * simple_next_child - get next child of the parent directory
+ *
+ * @parent: the directory to scan
+ * @child: last child (or NULL to start at the beginning)
+ *
+ * returns the next positive child in sequence with the reference
+ * elevated but if a child is passed in will drop that
+ * reference. Returns NULL on either error or when directory has been
+ * fully scanned.
+ *
+ * The intended use is as an iterator because all the references will
+ * be dropped by the end of the while loop:
+ *
+ * child = NULL
+ * while(child = simple_next_child(parent, child)) {
+ * // do something
+ * }
+ */
+struct dentry *simple_next_child(struct dentry *parent, struct dentry *child)
+{
+ struct hlist_node **p;
+ struct dentry *cursor = d_alloc_cursor(parent);
+
+ if (!cursor) {
+ dput(child);
+ return NULL;
+ }
+
+ if (child)
+ p = &child->d_sib.next;
+ else
+ p = &parent->d_children.first;
+
+ child = scan_positives(cursor, p, 1, child);
+ dput(cursor);
+
+ return child;
+}
+EXPORT_SYMBOL(simple_next_child);
+
loff_t dcache_dir_lseek(struct file *file, loff_t offset, int whence)
{
struct dentry *dentry = file->f_path.dentry;
diff --git a/include/linux/fs.h b/include/linux/fs.h
index 2788df98080f..dd84d1c3b8af 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 struct dentry *simple_next_child(struct dentry *parent,
+ struct dentry *child);
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
next prev parent reply other threads:[~2025-03-19 16:46 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 ` [RFC PATCH 2/3] libfs: add simple directory iteration " James Bottomley
2025-03-18 21:33 ` 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 [this message]
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=70ba7c8e2cdc4c76f71274c9aaf77b360692613d.camel@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