From: Luca Stefani via B4 Relay <devnull+luca.stefani.ge1.gmail.com@kernel.org>
To: David Sterba <dsterba@suse.com>, Chris Mason <mason@kernel.org>,
Luca Stefani <luca.stefani.ge1@gmail.com>
Cc: Robbie Ko <robbieko@synology.com>,
Filipe Manana <fdmanana@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhiwei Liang <zhiwei.liang@zliang.me>, Qu Wenruo <wqu@suse.com>
Subject: [PATCH 0/2] btrfs: don't expose ERESTARTSYS to userspace
Date: Wed, 28 Oct 2026 18:55:48 +0100 [thread overview]
Message-ID: <20261028-b4-btrfs-fitrim-interruption-v1-0-bf5c53738b3a@gmail.com> (raw)
trim can expose -ERESTARTSYS when the trim loops gets interrupted by
a freezer request.
Preserve byte counts of partially completed discards.
Consume cancellation at btrfs_trim_fs(), and report partial progress.
Link: https://lore.kernel.org/20261028-btrfs-fitrim-freezer-v1-1-0ad1d58aa94d@zliang.me/
---
Luca Stefani (2):
btrfs: account partially completed discards
btrfs: don't report failure when trim is interrupted
fs/btrfs/extent-tree.c | 10 ++++------
fs/btrfs/free-space-cache.c | 5 ++---
2 files changed, 6 insertions(+), 9 deletions(-)
---
base-commit: 65ba8f34ec886ec72b2c07ddc8cf3d815c32869d
change-id: 20261028-b4-btrfs-fitrim-interruption-48ae75801fa0
Best regards,
--
Luca Stefani <luca.stefani.ge1@gmail.com>
next reply other threads:[~2026-10-28 17:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 17:55 Luca Stefani via B4 Relay [this message]
2026-10-28 17:55 ` [PATCH 1/2] btrfs: account partially completed discards Luca Stefani via B4 Relay
2026-10-28 21:02 ` Qu Wenruo
2026-10-28 17:55 ` [PATCH 2/2] btrfs: don't report failure when trim is interrupted Luca Stefani via B4 Relay
2026-10-28 21:06 ` Qu Wenruo
2026-10-29 8:56 ` Luca Stefani
2026-10-28 20:13 ` [PATCH 0/2] btrfs: don't expose ERESTARTSYS to userspace zhiwei.liang
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=20261028-b4-btrfs-fitrim-interruption-v1-0-bf5c53738b3a@gmail.com \
--to=devnull+luca.stefani.ge1.gmail.com@kernel.org \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.stefani.ge1@gmail.com \
--cc=mason@kernel.org \
--cc=robbieko@synology.com \
--cc=wqu@suse.com \
--cc=zhiwei.liang@zliang.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
all inboxes | Powered by JetHome®