From: Tal Zussman <tz2294@columbia.edu>
To: dsterba@suse.cz
Cc: David Sterba <dsterba@suse.com>, Chris Mason <mason@kernel.org>,
Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 00/18] btrfs: remove the v1 space cache
Date: Wed, 14 Oct 2026 14:00:04 -0400 [thread overview]
Message-ID: <7eee4fcf-1348-4d60-a1ec-cd3b76eb5904@columbia.edu> (raw)
In-Reply-To: <20261013122214.GA1310987@suse.cz>
On 10/13/26 8:22 AM, David Sterba wrote:
>
> Thanks, unfortunatelly this did not make it into the 7.4 pull as the
> freeze was yesterday and I was not able to process the v3 last week.
> The v4 still has some issues reported by sashiko. It could be still
> possible to send that separately as 2nd pull to 7.4 because the code has
> been in linux-next, small fixups would be possible, and it's code
> removal.
>
No problem. I took a look at the Sashiko feedback. It looks like a
rare pre-existing issue, with the fix being to change the `if (truncate)`
to `if (truncate && !ret)`. I can prepend a standalone fix for this at the
start of the series and respin.
Thanks,
Tal
prev parent reply other threads:[~2026-10-14 18:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-12 16:28 Tal Zussman
2026-10-12 16:28 ` [PATCH v4 01/18] btrfs: update the inode item when removing a free space inode Tal Zussman
2026-10-12 16:28 ` [PATCH v4 02/18] btrfs: stop enabling the v1 space cache from the on-disk state Tal Zussman
2026-10-12 16:28 ` [PATCH v4 03/18] btrfs: remove the v1 space cache writeout from the transaction commit Tal Zussman
2026-10-12 16:28 ` [PATCH v4 04/18] btrfs: remove the free space cache endio workqueue Tal Zussman
2026-10-12 16:28 ` [PATCH v4 05/18] btrfs: remove the v1 space cache write path Tal Zussman
2026-10-12 16:28 ` [PATCH v4 06/18] btrfs: rename cache_write_mutex to dirty_bgs_update_mutex Tal Zussman
2026-10-12 16:28 ` [PATCH v4 07/18] btrfs: drop the transaction handle from the prealloc helpers Tal Zussman
2026-10-12 16:28 ` [PATCH v4 08/18] btrfs: remove the v1 space cache load path Tal Zussman
2026-10-12 16:28 ` [PATCH v4 09/18] btrfs: remove btrfs_disk_cache_state Tal Zussman
2026-10-12 16:28 ` [PATCH v4 10/18] btrfs: remove the SPACE_CACHE mount option flag Tal Zussman
2026-10-12 16:28 ` [PATCH v4 11/18] btrfs: replace btrfs_set_free_space_cache_v1_active() with a cleanup helper Tal Zussman
2026-10-12 16:28 ` [PATCH v4 12/18] btrfs: remove the free space cache trimming ranges Tal Zussman
2026-10-12 16:28 ` [PATCH v4 13/18] btrfs: remove BTRFS_RESERVE_FLUSH_FREE_SPACE_INODE Tal Zussman
2026-10-12 16:28 ` [PATCH v4 14/18] btrfs: remove the free space inode ordered extent special cases Tal Zussman
2026-10-12 16:28 ` [PATCH v4 15/18] btrfs: remove the free space inode special cases from the COW paths Tal Zussman
2026-10-12 16:28 ` [PATCH v4 16/18] btrfs: stop special-casing free space inodes in the delalloc accounting Tal Zussman
2026-10-12 16:28 ` [PATCH v4 17/18] btrfs: stop reading free space inodes from the commit root Tal Zussman
2026-10-12 16:28 ` [PATCH v4 18/18] btrfs: remove TRANS_JOIN_NOLOCK Tal Zussman
2026-10-13 12:22 ` [PATCH v4 00/18] btrfs: remove the v1 space cache David Sterba
2026-10-14 18:00 ` Tal Zussman [this message]
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=7eee4fcf-1348-4d60-a1ec-cd3b76eb5904@columbia.edu \
--to=tz2294@columbia.edu \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mason@kernel.org \
--cc=wqu@suse.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
all inboxes | Powered by JetHome®