From: Ye Bin <yebin@huaweicloud.com>
To: tytso@mit.edu, adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org
Cc: jack@suse.cz
Subject: [PATCH v2 3/4] ext4: show inode orphan list detail information
Date: Wed, 15 Apr 2026 18:55:04 +0800 [thread overview]
Message-ID: <20260415105505.342358-4-yebin@huaweicloud.com> (raw)
In-Reply-To: <20260415105505.342358-1-yebin@huaweicloud.com>
From: Ye Bin <yebin10@huawei.com>
Some inodes added to the orphan list are due to truncation, while others
are due to deletion.Therefore, we printed the information of inode as
follows: inode number/i_nlink/i_size/i_blocks/projid/file path. By using
this information, it is possible to quickly identify files that have been
deleted but are still being referenced.
Signed-off-by: Ye Bin <yebin10@huawei.com>
---
fs/ext4/orphan.c | 128 ++++++++++++++++++++++++++++++++++++++++++++++-
1 file changed, 126 insertions(+), 2 deletions(-)
diff --git a/fs/ext4/orphan.c b/fs/ext4/orphan.c
index a6bffe67ef75..4d6f8c9edaeb 100644
--- a/fs/ext4/orphan.c
+++ b/fs/ext4/orphan.c
@@ -682,23 +682,147 @@ struct ext4_proc_orphan {
struct ext4_inode_info cursor;
};
-static void *ext4_orphan_seq_start(struct seq_file *seq, loff_t *pos)
+static struct inode *ext4_list_next(struct ext4_proc_orphan *s,
+ struct list_head *head,
+ struct list_head *p)
{
+ list_for_each_continue(p, head) {
+ struct ext4_inode_info *ei;
+ struct inode *inode;
+
+ ei = list_entry(p, typeof(*ei), i_orphan);
+ inode = &ei->vfs_inode;
+
+ /*
+ * It is safe to insert a cursor into the orphan list
+ * because ext4_orphan_del() will skip cursor. When the
+ * orphan list is processed in ext4_put_super(),
+ * ext4_seq_orphan_release() must have already been called,
+ * so the cursor must have already been removed from the
+ * orphan list.Therefore, there will be no access to a
+ * stale cursor.
+ */
+ list_move(&s->cursor.i_orphan, &ei->i_orphan);
+
+ /*
+ * Because the cursor has moved to the node after the
+ * current node, the traversal cannot continue from the
+ * current node. Instead, the traversal should continue
+ * from the cursor.
+ */
+ p = &s->cursor.i_orphan;
+
+ if (ext4_is_cursor(inode))
+ continue;
+
+ if (!igrab(inode))
+ continue;
+
+ return inode;
+ }
+
return NULL;
}
+static void *ext4_orphan_seq_start(struct seq_file *seq, loff_t *pos)
+{
+ struct ext4_proc_orphan *s = seq->private;
+ struct super_block *sb = pde_data(file_inode(seq->file));
+ struct ext4_sb_info *sbi = EXT4_SB(sb);
+ struct list_head *prev;
+
+ mutex_lock(&sbi->s_orphan_lock);
+
+ if (!*pos) {
+ prev = &sbi->s_orphan;
+ } else {
+ prev = &s->cursor.i_orphan;
+ if (list_empty(prev))
+ return NULL;
+ }
+
+ return ext4_list_next(s, &sbi->s_orphan, prev);
+}
+
static void *ext4_orphan_seq_next(struct seq_file *seq, void *v, loff_t *pos)
{
- return NULL;
+ struct super_block *sb = pde_data(file_inode(seq->file));
+ struct ext4_sb_info *sbi = EXT4_SB(sb);
+ struct ext4_proc_orphan *s = seq->private;
+ struct inode *inode = v;
+
+ ++*pos;
+
+ /*
+ * To prevent the deadlock caused by orphan node deletion when the
+ * last inode reference count is released, the inode reference
+ * count needs to be released in the unlocked state.
+ */
+ mutex_unlock(&sbi->s_orphan_lock);
+ iput(inode);
+ mutex_lock(&sbi->s_orphan_lock);
+
+ return ext4_list_next(s, &sbi->s_orphan, &s->cursor.i_orphan);
+}
+
+static void ext4_show_filename(struct seq_file *seq, struct inode *inode)
+{
+ struct dentry *dentry;
+
+ dentry = d_find_alias(inode);
+ if (!dentry)
+ dentry = d_find_any_alias(inode);
+
+ if (dentry)
+ seq_dentry(seq, dentry, " \t\n\\");
+ else
+ seq_puts(seq, "unknown");
+
+ seq_puts(seq, "\"\n");
+
+ /*
+ * Since igrab() has already been called in ext4_list_next(), the
+ * inode will not be released here, so there will be no deadlock.
+ */
+ dput(dentry);
}
static int ext4_orphan_seq_show(struct seq_file *seq, void *v)
{
+ struct inode *inode = v;
+
+ /*
+ * Print the original data without differentiating namespaces.
+ */
+ seq_printf(seq, "ino: %llu, link: %u, size: %llu, blocks: %llu, proj: %u, path: \"",
+ inode->i_ino, inode->i_nlink,
+ i_size_read(inode), inode->i_blocks,
+ __kprojid_val(EXT4_I(inode)->i_projid));
+
+ ext4_show_filename(seq, inode);
+
return 0;
}
static void ext4_orphan_seq_stop(struct seq_file *seq, void *v)
{
+ struct super_block *sb = pde_data(file_inode(seq->file));
+ struct ext4_sb_info *sbi = EXT4_SB(sb);
+ struct ext4_proc_orphan *s = seq->private;
+ struct inode *inode = v;
+
+ /*
+ * stop() is called when the cache is full, so the traversal
+ * position needs to be moved back to the front of the current
+ * inode.
+ */
+ if (v)
+ list_move_tail(&s->cursor.i_orphan,
+ &EXT4_I(inode)->i_orphan);
+
+ mutex_unlock(&sbi->s_orphan_lock);
+
+ iput(inode);
}
const struct seq_operations ext4_orphan_seq_ops = {
--
2.34.1
next prev parent reply other threads:[~2026-04-15 10:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 10:55 [PATCH v2 0/4] show orphan file inode detail info Ye Bin
2026-04-15 10:55 ` [PATCH v2 1/4] ext4: register 'orphan_list' procfs Ye Bin
2026-04-15 10:55 ` [PATCH v2 2/4] ext4: skip cursor node in ext4_orphan_del() Ye Bin
2026-04-15 23:56 ` Darrick J. Wong
2026-04-15 10:55 ` Ye Bin [this message]
2026-04-15 10:55 ` [PATCH v2 4/4] ext4: show orphan file inode detail info Ye Bin
2026-04-15 17:59 ` [PATCH v2 0/4] " Jan Kara
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=20260415105505.342358-4-yebin@huaweicloud.com \
--to=yebin@huaweicloud.com \
--cc=adilger.kernel@dilger.ca \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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