public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Joanne Koong <joannelkoong@gmail.com>
To: brauner@kernel.org
Cc: linux-fsdevel@vger.kernel.org, jack@suse.cz, miklos@szeredi.hu,
	david@kernel.org, therealgraysky@proton.me,
	linux-pm@vger.kernel.org
Subject: [PATCH v3 0/1] writeback: don't block sync for filesystems with no data integrity guarantees
Date: Thu, 19 Mar 2026 17:51:44 -0700	[thread overview]
Message-ID: <20260320005145.2483161-1-joannelkoong@gmail.com> (raw)

Changelog
---------
v2: https://lore.kernel.org/linux-fsdevel/20260319194540.3463371-1-joannelkoong@gmail.com/
v2 -> v3:
* Move SB_I_NO_DATA_INTEGRITY check to sync_inodes_sb() instead of
  sync_inodes_one_sb() (David)
* Move comment block (David)

v1: https://lore.kernel.org/linux-fsdevel/20260318225604.71545-1-joannelkoong@gmail.com/
v1 -> v2:
* Still kick off flusher threads for writeback for SB_I_NO_DATA_INTEGRITY,
  instead of skipping that entirely (Jan)
* Improve commit message (me)

Joanne Koong (1):
  writeback: don't block sync for filesystems with no data integrity
    guarantees

 fs/fs-writeback.c              | 18 ++++++++++++------
 fs/fuse/file.c                 |  4 +---
 fs/fuse/inode.c                |  1 +
 include/linux/fs/super_types.h |  1 +
 include/linux/pagemap.h        | 11 -----------
 5 files changed, 15 insertions(+), 20 deletions(-)

-- 
2.52.0


             reply	other threads:[~2026-03-20  0:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20  0:51 Joanne Koong [this message]
2026-03-20  0:51 ` [PATCH v3 1/1] writeback: don't block sync for filesystems with no data integrity guarantees Joanne Koong
2026-03-20  8:12   ` David Hildenbrand (Arm)
2026-03-20 10:16   ` Jan Kara
2026-03-20 13:19 ` [PATCH v3 0/1] " Christian Brauner

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=20260320005145.2483161-1-joannelkoong@gmail.com \
    --to=joannelkoong@gmail.com \
    --cc=brauner@kernel.org \
    --cc=david@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=therealgraysky@proton.me \
    /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