From: Kent Overstreet <kent.overstreet@linux.dev>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-bcachefs@vger.kernel.org, linux-stable@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] bcachefs fixes for 6.7.y
Date: Sun, 10 Mar 2024 15:43:38 -0400 [thread overview]
Message-ID: <2zaqetj6wlxgpbxgex643dnudgwhcrz23xgfuai3t3hgavjb2d@vwhyha3hlg5y> (raw)
The following changes since commit 2e7cdd29fc42c410eab52fffe5710bf656619222:
Linux 6.7.9 (2024-03-06 14:54:01 +0000)
are available in the Git repository at:
https://evilpiepirate.org/git/bcachefs.git tags/bcachefs-for-v6.7-stable-20240310
for you to fetch changes up to 560ceb6a4d9e3bea57c29f5f3a7a1d671dfc7983:
bcachefs: Fix BTREE_ITER_FILTER_SNAPSHOTS on inodes btree (2024-03-10 14:36:57 -0400)
----------------------------------------------------------------
bcachefs fixes for 6.7 stable
"bcachefs: fix simulateously upgrading & downgrading" is the important
one here. This fixes a really nasty bug where in a rare situation we
wouldn't downgrade; we'd write a superblock where the version number is
higher than the currently supported version.
This caused total failure to mount multi device filesystems with the
splitbrain checking in 6.8, since now we wouldn't be updating the member
sequence numbers used for splitbrain checking, but the version number
said we would be - and newer versions would attempt to kick every device
out of the fs.
----------------------------------------------------------------
Helge Deller (1):
bcachefs: Fix build on parisc by avoiding __multi3()
Kent Overstreet (3):
bcachefs: check for failure to downgrade
bcachefs: fix simulateously upgrading & downgrading
bcachefs: Fix BTREE_ITER_FILTER_SNAPSHOTS on inodes btree
Mathias Krause (1):
bcachefs: install fd later to avoid race with close
fs/bcachefs/btree_iter.c | 4 +++-
fs/bcachefs/chardev.c | 3 +--
fs/bcachefs/errcode.h | 1 +
fs/bcachefs/mean_and_variance.h | 2 +-
fs/bcachefs/super-io.c | 27 ++++++++++++++++++++++++---
5 files changed, 30 insertions(+), 7 deletions(-)
next reply other threads:[~2024-03-10 19:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-10 19:43 Kent Overstreet [this message]
2024-03-10 19:52 ` [GIT PULL] bcachefs fixes for 6.7.y Kent Overstreet
2024-03-13 0:54 ` Kent Overstreet
2024-03-13 18:20 ` Greg Kroah-Hartman
2024-03-13 18:52 ` Kent Overstreet
2024-03-24 13:51 ` Greg Kroah-Hartman
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=2zaqetj6wlxgpbxgex643dnudgwhcrz23xgfuai3t3hgavjb2d@vwhyha3hlg5y \
--to=kent.overstreet@linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stable@vger.kernel.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).