From: Jingbo Xu <jefflexu@linux.alibaba.com>
To: Joanne Koong <joannelkoong@gmail.com>,
miklos@szeredi.hu, linux-fsdevel@vger.kernel.org
Cc: shakeel.butt@linux.dev, josef@toxicpanda.com, linux-mm@kvack.org,
bernd.schubert@fastmail.fm, kernel-team@meta.com
Subject: Re: [PATCH v5 3/5] fs/writeback: in wait_sb_inodes(), skip wait for AS_WRITEBACK_INDETERMINATE mappings
Date: Wed, 20 Nov 2024 20:07:04 +0800 [thread overview]
Message-ID: <949e9cf4-60df-4e2e-96a3-2219cfcbb46a@linux.alibaba.com> (raw)
In-Reply-To: <20241115224459.427610-4-joannelkoong@gmail.com>
On 11/16/24 6:44 AM, Joanne Koong wrote:
> For filesystems with the AS_WRITEBACK_INDETERMINATE flag set, writeback
> operations may take an indeterminate time to complete. For example, writing
> data back to disk in FUSE filesystems depends on the userspace server
> successfully completing writeback.
>
> In this commit, wait_sb_inodes() skips waiting on writeback if the
> inode's mapping has AS_WRITEBACK_INDETERMINATE set, else sync(2) may take an
> indeterminate amount of time to complete.
>
> If the caller wishes to ensure the data for a mapping with the
> AS_WRITEBACK_INDETERMINATE flag set has actually been written back to disk,
> they should use fsync(2)/fdatasync(2) instead.
>
> Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
> ---
> fs/fs-writeback.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/fs/fs-writeback.c b/fs/fs-writeback.c
> index d8bec3c1bb1f..ad192db17ce4 100644
> --- a/fs/fs-writeback.c
> +++ b/fs/fs-writeback.c
> @@ -2659,6 +2659,9 @@ static void wait_sb_inodes(struct super_block *sb)
> if (!mapping_tagged(mapping, PAGECACHE_TAG_WRITEBACK))
> continue;
>
> + if (mapping_writeback_indeterminate(mapping))
> + continue;
> +
> spin_unlock_irq(&sb->s_inode_wblist_lock);
>
> spin_lock(&inode->i_lock);
Reviewed-by: Jingbo Xu <jefflexu@linux.alibaba.com>
--
Thanks,
Jingbo
next prev parent reply other threads:[~2024-11-20 12:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 22:44 [PATCH v5 0/5] fuse: remove temp page copies in writeback Joanne Koong
2024-11-15 22:44 ` [PATCH v5 1/5] mm: add AS_WRITEBACK_INDETERMINATE mapping flag Joanne Koong
2024-11-15 23:11 ` Shakeel Butt
2024-11-15 22:44 ` [PATCH v5 2/5] mm: skip reclaiming folios in legacy memcg writeback indeterminate contexts Joanne Koong
2024-11-15 22:44 ` [PATCH v5 3/5] fs/writeback: in wait_sb_inodes(), skip wait for AS_WRITEBACK_INDETERMINATE mappings Joanne Koong
2024-11-20 12:07 ` Jingbo Xu [this message]
2024-11-15 22:44 ` [PATCH v5 4/5] mm/migrate: skip migrating folios under writeback with " Joanne Koong
2024-11-15 23:12 ` Shakeel Butt
2024-11-15 22:44 ` [PATCH v5 5/5] fuse: remove tmp folio for writebacks and internal rb tree Joanne Koong
2024-11-19 7:59 ` Jingbo Xu
2024-11-20 21:07 ` Joanne Koong
2024-11-20 9:56 ` Jingbo Xu
2024-11-20 21:53 ` Joanne Koong
2024-11-21 3:08 ` Jingbo Xu
2024-11-21 10:11 ` Bernd Schubert
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=949e9cf4-60df-4e2e-96a3-2219cfcbb46a@linux.alibaba.com \
--to=jefflexu@linux.alibaba.com \
--cc=bernd.schubert@fastmail.fm \
--cc=joannelkoong@gmail.com \
--cc=josef@toxicpanda.com \
--cc=kernel-team@meta.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=miklos@szeredi.hu \
--cc=shakeel.butt@linux.dev \
/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