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 fixes for 6.6-rc5
Date: Fri, 6 Oct 2023 15:27:47 +0200 [thread overview]
Message-ID: <cover.1696529195.git.dsterba@suse.com> (raw)
Hi,
please pull a few more fixes. Thanks.
- reject unknown mount options
- adjust transaction abort error message level
- fix one more build warning with -Wmaybe-uninitialized
- proper error handling in several COW-related cases
----------------------------------------------------------------
The following changes since commit b4c639f699349880b7918b861e1bd360442ec450:
btrfs: initialize start_slot in btrfs_log_prealloc_extents (2023-09-21 18:52:23 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.6-rc4-tag
for you to fetch changes up to e36f94914021e58ee88a8856c7fdf35adf9c7ee1:
btrfs: error out when reallocating block for defrag using a stale transaction (2023-10-04 01:04:33 +0200)
----------------------------------------------------------------
Filipe Manana (4):
btrfs: always print transaction aborted messages with an error level
btrfs: error out when COWing block using a stale transaction
btrfs: error when COWing block from a root that is being deleted
btrfs: error out when reallocating block for defrag using a stale transaction
Josef Bacik (1):
btrfs: fix some -Wmaybe-uninitialized warnings in ioctl.c
Qu Wenruo (1):
btrfs: reject unknown mount options early
fs/btrfs/ctree.c | 52 +++++++++++++++++++++++++++++++++++++-------------
fs/btrfs/ioctl.c | 4 ++--
fs/btrfs/super.c | 4 ++++
fs/btrfs/transaction.h | 4 ++--
4 files changed, 47 insertions(+), 17 deletions(-)
next reply other threads:[~2023-10-06 13:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-06 13:27 David Sterba [this message]
2023-10-06 15:15 ` [GIT PULL] Btrfs fixes for 6.6-rc5 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.1696529195.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.