From: Chao Yu <chao@kernel.org>
To: Jaegeuk Kim <jaegeuk@kernel.org>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH 1/2 v2] f2fs: don't get FREEZE lock in f2fs_evict_inode in frozen fs
Date: Fri, 11 Mar 2022 15:25:25 +0800 [thread overview]
Message-ID: <86d59c1d-b453-5ee2-4737-b4dd03829965@kernel.org> (raw)
In-Reply-To: <Yircgd9d773xnk3+@google.com>
On 2022/3/11 13:22, Jaegeuk Kim wrote:
> Let's purge inode cache in order to avoid the below deadlock.
>
> [freeze test] shrinkder
> freeze_super
> - pwercpu_down_write(SB_FREEZE_FS)
> - super_cache_scan
> - down_read(&sb->s_umount)
> - prune_icache_sb
> - dispose_list
> - evict
> - f2fs_evict_inode
> thaw_super
> - down_write(&sb->s_umount);
> - __percpu_down_read(SB_FREEZE_FS)
>
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Reviewed-by: Chao Yu <chao@kernel.org>
Thanks,
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
prev parent reply other threads:[~2022-03-11 7:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 21:48 [f2fs-dev] [PATCH 1/2] f2fs: evict inode cache for frozen fs Jaegeuk Kim
2022-03-09 21:48 ` [f2fs-dev] [PATCH 2/2] f2fs: use spin_lock to avoid hang Jaegeuk Kim
2022-03-10 2:23 ` Chao Yu
2022-03-10 2:51 ` Jaegeuk Kim
2022-03-16 2:33 ` Chao Yu
2022-03-10 1:53 ` [f2fs-dev] [PATCH 1/2] f2fs: evict inode cache for frozen fs Chao Yu
2022-03-11 3:10 ` Chao Yu
2022-03-11 5:22 ` Jaegeuk Kim
2022-03-10 2:52 ` [f2fs-dev] [PATCH 1/2 v2] f2fs: do not expose unwritten blocks to user by DIO Jaegeuk Kim
2022-03-11 5:22 ` [f2fs-dev] [PATCH 1/2 v2] f2fs: don't get FREEZE lock in f2fs_evict_inode in frozen fs Jaegeuk Kim
2022-03-11 7:25 ` Chao Yu [this message]
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=86d59c1d-b453-5ee2-4737-b4dd03829965@kernel.org \
--to=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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).