From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs urgent fix for 6.17
Date: Wed, 6 Aug 2025 13:14:26 +0200 [thread overview]
Message-ID: <cover.1754478249.git.dsterba@suse.com> (raw)
Hi,
please pull a single btrfs commit. It fixes a problem that people
started to hit since 6.15.3 during log replay (e.g. after a crash).
The bug is old but got more likely to happen since 5e85262e542d6da got
backported to stable (6.15 only). The summer vacation time caused delays
of the fix delivery, apologies to everyone. Thanks.
----------------------------------------------------------------
The following changes since commit 005b0a0c24e1628313e951516b675109a92cacfe:
btrfs: send: use fallocate for hole punching with send stream v2 (2025-07-22 01:23:14 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.17-fix-tag
for you to fetch changes up to 0a32e4f0025a74c70dcab4478e9b29c22f5ecf2f:
btrfs: fix log tree replay failure due to file with 0 links and extents (2025-08-06 13:01:38 +0200)
----------------------------------------------------------------
Filipe Manana (1):
btrfs: fix log tree replay failure due to file with 0 links and extents
fs/btrfs/tree-log.c | 48 ++++++++++++++++++++++++++++++------------------
1 file changed, 30 insertions(+), 18 deletions(-)
next reply other threads:[~2025-08-06 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-06 11:14 David Sterba [this message]
2025-08-06 12:56 ` [GIT PULL] Btrfs urgent fix for 6.17 pr-tracker-bot
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=cover.1754478249.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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