From: Miklos Szeredi <miklos@szeredi.hu>
To: Ed Tsai <ed.tsai@mediatek.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
chenguanyou <chenguanyou9338@gmail.com>,
"Stanley Chu (朱原陞)" <stanley.chu@mediatek.com>,
"Yong-xuan Wang (王詠萱)" <Yong-xuan.Wang@mediatek.com>
Subject: Re: [PATCH] [fuse] alloc_page nofs avoid deadlock
Date: Mon, 13 Jun 2022 10:45:00 +0200 [thread overview]
Message-ID: <CAJfpegsw3NpH6oTU9nxJLPUYMJVmfWhAa6yB8vnDZctP9vHc0g@mail.gmail.com> (raw)
In-Reply-To: <07ad7d51d15c7ffc708b55066ded653a4b2c5c98.camel@mediatek.com>
On Fri, 10 Jun 2022 at 09:48, Ed Tsai <ed.tsai@mediatek.com> wrote:
> Recently, we get this deadlock issue again. fuse_flush_time_update()
> use sync_inode_metadata() and it only write the metadata, so the
> writeback worker could still be blocked becaused of file data.
>
> I try to use write_inode_now() instead of sync_inode_metadata() and the
> writeback thread will not be blocked anymore. I don't think this is a
> good solution, but this confirm that there is still a potential
> deadlock because of file data. WDYT.
I'm not sure how that happens. Normally writeback doesn't block. Can
you provide the stack traces of all related tasks in the deadlock?
Thanks,
Miklos
next prev parent reply other threads:[~2022-06-13 8:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-03 12:52 [PATCH] [fuse] alloc_page nofs avoid deadlock chenguanyou
2021-06-08 14:54 ` Re:[PATCH] fuse: " chenguanyou
2021-06-08 15:30 ` [PATCH] [fuse] " Miklos Szeredi
2021-06-11 12:14 ` Re:[PATCH] fuse: " chenguanyou
2021-07-13 2:42 ` [PATCH] [fuse] " Ed Tsai
2021-08-18 9:24 ` Miklos Szeredi
2021-09-24 3:52 ` Ed Tsai
2021-09-24 7:52 ` Miklos Szeredi
2021-09-28 15:25 ` Miklos Szeredi
2021-09-29 3:31 ` Re:[PATCH] fuse: " chenguanyou
2021-12-14 9:25 ` [PATCH] [fuse] " Ed Tsai
2021-12-14 9:38 ` Greg Kroah-Hartman
2021-12-15 8:22 ` Ed Tsai
2021-12-15 13:52 ` Greg Kroah-Hartman
[not found] ` <SI2PR03MB5545E0B76E54013678B9FEEC8BA99@SI2PR03MB5545.apcprd03.prod.outlook.com>
2022-06-10 7:48 ` Ed Tsai
2022-06-13 8:45 ` Miklos Szeredi [this message]
2022-06-13 9:29 ` Ed Tsai
2022-07-05 8:53 ` [PATCH 1/1] fuse: add fuse_d_iput to postponed the iput Ed Tsai
2022-07-18 13:57 ` Miklos Szeredi
2022-07-11 7:49 ` [PATCH] [fuse] alloc_page nofs avoid deadlock Miklos Szeredi
2022-07-12 1:16 ` Ed Tsai
-- strict thread matches above, loose matches on Subject: below --
2021-06-03 12:41 chenguanyou
2021-06-03 12:56 ` Michal Hocko
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=CAJfpegsw3NpH6oTU9nxJLPUYMJVmfWhAa6yB8vnDZctP9vHc0g@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=Yong-xuan.Wang@mediatek.com \
--cc=chenguanyou9338@gmail.com \
--cc=ed.tsai@mediatek.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stanley.chu@mediatek.com \
/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).