From: Chao Yu <chao@kernel.org>
To: Daeho Jeong <daeho43@gmail.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net, kernel-team@android.com
Cc: Daeho Jeong <daehojeong@google.com>
Subject: Re: [f2fs-dev] [PATCH] f2fs: remove circular locking between sb_internal and fs_reclaim
Date: Thu, 21 Oct 2021 20:11:20 +0800 [thread overview]
Message-ID: <e8b106fb-2878-2fa9-788f-965eef179a85@kernel.org> (raw)
In-Reply-To: <20211014190503.717830-1-daeho43@gmail.com>
On 2021/10/15 3:05, Daeho Jeong wrote:
> From: Daeho Jeong <daehojeong@google.com>
>
> We detected the below circular locking dependency between sb_internal
> and fs_reclaim. So, removed it by calling dquot_initialize() before
> sb_start_intwrite().
>
> ======================================================
> WARNING: possible circular locking dependency detected
> ------------------------------------------------------
> kswapd0/133 is trying to acquire lock:
> ffffff80d5fb9680 (sb_internal#2){.+.+}-{0:0}, at: evict+0xd4/0x2f8
>
> but task is already holding lock:
> ffffffda597c93a8 (fs_reclaim){+.+.}-{0:0}, at:
> __fs_reclaim_acquire+0x4/0x50
>
> which lock already depends on the new lock.
> ...
> other info that might help us debug this:
>
> Chain exists of:
>
> sb_internal#2 --> &s->s_dquot.dqio_sem --> fs_reclaim
>
> Possible unsafe locking scenario:
>
> CPU0 CPU1
> ---- ----
> lock(fs_reclaim);
> lock(&s->s_dquot.dqio_sem);
> lock(fs_reclaim);
> lock(sb_internal#2);
Sorry, I still didn't get the root cause of this deadlock issue, could
you please explain more about this?
And why calling dquot_initialize() in drop_inode() could break the
circular locking dependency?
Thanks,
>
> Signed-off-by: Daeho Jeong <daehojeong@google.com>
> ---
> fs/f2fs/super.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
> index 86eeb019cc52..a133932333c5 100644
> --- a/fs/f2fs/super.c
> +++ b/fs/f2fs/super.c
> @@ -1370,6 +1370,8 @@ static int f2fs_drop_inode(struct inode *inode)
> /* should remain fi->extent_tree for writepage */
> f2fs_destroy_extent_node(inode);
>
> + dquot_initialize(inode);
> +
> sb_start_intwrite(inode->i_sb);
> f2fs_i_size_write(inode, 0);
>
>
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next prev parent reply other threads:[~2021-10-21 12:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-14 19:05 [f2fs-dev] [PATCH] f2fs: remove circular locking between sb_internal and fs_reclaim Daeho Jeong
2021-10-21 12:11 ` Chao Yu [this message]
2021-10-21 16:44 ` Daeho Jeong
2021-10-22 15:32 ` Chao Yu
2021-10-25 16:22 ` Daeho Jeong
2021-10-26 1:09 ` Chao Yu
2021-10-26 17:56 ` Daeho Jeong
2021-10-27 18:36 ` Daeho Jeong
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=e8b106fb-2878-2fa9-788f-965eef179a85@kernel.org \
--to=chao@kernel.org \
--cc=daeho43@gmail.com \
--cc=daehojeong@google.com \
--cc=kernel-team@android.com \
--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).