From: Zhihao Cheng <chengzhihao1@huawei.com>
To: Nikolaos Karaolidis <nick@karaolidis.com>,
Christian Brauner <brauner@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>
Cc: Jan Kara <jack@suse.cz>, Mateusz Guzik <mjguzik@gmail.com>,
<linux-fsdevel@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>
Subject: Re: [PATCH] fs: rotate inodes whose page cache could not be dropped
Date: Sat, 17 Oct 2026 15:43:03 +0800 [thread overview]
Message-ID: <5b74fceb-dc8d-21ad-d313-eba7a0009056@huawei.com> (raw)
In-Reply-To: <20261016102515.111285-1-nick@karaolidis.com>
在 2026/10/16 18:25, Nikolaos Karaolidis 写道:
> When inode_lru_isolate() drops the page cache of an unused inode, it
> has to unlock the list, so it returns LRU_RETRY and the walk restarts
> at the head of the list, where the inode still is. If
> invalidate_mapping_pages() could not empty the mapping, the restarted
> walk strips the same inode again, and so on until nr_to_walk runs out.
> Every walk of that list then ends on this inode, and nothing behind it
> is reclaimed for as long as its cache stays.
[...]
> static void inode_wait_for_lru_isolating(struct inode *inode)
> @@ -981,7 +980,13 @@ static enum lru_status inode_lru_isolate(struct list_head *item,
> else
> __count_vm_events(PGINODESTEAL, reap);
> mm_account_reclaimed_pages(reap);
> +
> + spin_lock(&inode->i_lock);
> + /* The walk restarts here: don't retry leftovers right away */
> + if (!mapping_empty(&inode->i_data))
> + inode_state_set(inode, I_REFERENCED);
> inode_unpin_lru_isolating(inode);
> + spin_unlock(&inode->i_lock);
> return LRU_RETRY;
> }
Hi Nikolaos,
I find a possible BUG_ON if this patch applied, details shown as:
P1 P2
prune_icache_sb
lock(lru->lock)
inode_lru_isolate
if (!mapping_empty(&inode->i_data))
unlock(lru->lock)
spin_lock(&inode->i_lock)
inode_state_set(inode, I_REFERENCED)
inode_unpin_lru_isolating
spin_unlock(&inode->i_lock)
unlink
iget_locked // find_inode_fast gets the inode
iput
iput_final
drop = 1
evict
BUG_ON(inode_state_read_once(inode) !=
(I_FREEING | I_CLEAR)) // inode state with I_REFERENCED
Could that be possible?
next prev parent reply other threads:[~2026-10-17 7:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 10:25 Nikolaos Karaolidis
2026-10-17 7:43 ` Zhihao Cheng [this message]
2026-10-19 8:50 ` Nick Karaolidis
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=5b74fceb-dc8d-21ad-d313-eba7a0009056@huawei.com \
--to=chengzhihao1@huawei.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mjguzik@gmail.com \
--cc=nick@karaolidis.com \
--cc=stable@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
all inboxes | Powered by JetHome®