From: Kent Overstreet <kent.overstreet@linux.dev>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-bcachefs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] more bcachefs fixes for 6.7
Date: Wed, 27 Dec 2023 11:44:50 -0500 [thread overview]
Message-ID: <2uukaswjjfuudinozm3igqtfwx2sgkmpwxp7t4jgq2icseoygm@sr3pst2cwvlq> (raw)
Hi Linus, few more small fixes for you
Cheers,
Kent
The following changes since commit 247ce5f1bb3ea90879e8552b8edf4885b9a9f849:
bcachefs: Fix bch2_alloc_sectors_start_trans() error handling (2023-12-19 19:01:52 -0500)
are available in the Git repository at:
https://evilpiepirate.org/git/bcachefs.git tags/bcachefs-2023-12-27
for you to fetch changes up to 7b474c77daddaf89bbb72594737538f4e0dce2fd:
bcachefs: Fix promotes (2023-12-26 19:31:11 -0500)
----------------------------------------------------------------
More bcachefs bugfixes for 6.7:
Just a few fixes: besides a few one liners, we have a fix for snapshots
+ compression where the extent update path didn't account for the fact
that with snapshots, we might split an existing extent into three, not
just two; and a small fixup for promotes which were broken by the recent
changes in the data update path to correctly take into account device
durability.
----------------------------------------------------------------
Kent Overstreet (4):
bcachefs: fix BCH_FSCK_ERR enum
bcachefs: Fix insufficient disk reservation with compression + snapshots
bcachefs: Fix leakage of internal error code
bcachefs: Fix promotes
fs/bcachefs/btree_update.c | 15 ++++++++-------
fs/bcachefs/data_update.c | 3 ++-
fs/bcachefs/error.h | 2 +-
fs/bcachefs/journal_io.c | 6 ++++--
fs/bcachefs/sb-errors.h | 2 +-
5 files changed, 16 insertions(+), 12 deletions(-)
next reply other threads:[~2023-12-27 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 16:44 Kent Overstreet [this message]
2023-12-28 21:26 ` [GIT PULL] more bcachefs fixes for 6.7 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2023-12-10 23:57 [GIT PULL] More " Kent Overstreet
2023-12-12 0:19 ` 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=2uukaswjjfuudinozm3igqtfwx2sgkmpwxp7t4jgq2icseoygm@sr3pst2cwvlq \
--to=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).