From: David Sterba <dsterba@suse.cz>
To: torvalds@linux-foundation.org
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fix for 6.6-rc8
Date: Mon, 23 Oct 2023 18:10:27 +0200 [thread overview]
Message-ID: <cover.1698076832.git.dsterba@suse.com> (raw)
Hi,
one more fix for a problem with snapshot of a newly created subvolume
that can lead to inconsistent data under some circumstances. Kernel 6.5
added a performance optimization to skip transaction commit for
subvolume creation but this could end up with newer data on disk but not
linked to other structures.
The fix itself is an added condition, the rest of the patch is a
parameter added to several functions.
Please pull, thanks.
----------------------------------------------------------------
The following changes since commit 8a540e990d7da36813cb71a4a422712bfba448a4:
btrfs: fix stripe length calculation for non-zoned data chunk allocation (2023-10-15 19:00:59 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.6-rc7-tag
for you to fetch changes up to eb96e221937af3c7bb8a63208dbab813ca5d3d7e:
btrfs: fix unwritten extent buffer after snapshotting a new subvolume (2023-10-23 17:17:30 +0200)
----------------------------------------------------------------
Filipe Manana (1):
btrfs: fix unwritten extent buffer after snapshotting a new subvolume
fs/btrfs/backref.c | 14 +++++++++-----
fs/btrfs/backref.h | 3 ++-
fs/btrfs/ctree.c | 21 ++++++++++++++++-----
fs/btrfs/ctree.h | 3 ++-
fs/btrfs/relocation.c | 7 ++++---
5 files changed, 33 insertions(+), 15 deletions(-)
next reply other threads:[~2023-10-23 16:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 16:10 David Sterba [this message]
2023-10-23 18:03 ` [GIT PULL] Btrfs fix for 6.6-rc8 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.1698076832.git.dsterba@suse.com \
--to=dsterba@suse.cz \
--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