From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: David Sterba <dsterba@suse.cz>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.12-rc5
Date: Thu, 25 Mar 2021 22:36:55 +0100 [thread overview]
Message-ID: <cover.1616690512.git.dsterba@suse.com> (raw)
From: David Sterba <dsterba@suse.cz>
Hi,
there are few fixes for issues that have some user visibility and are
simple enough for this time of development cycle.
Please pull thanks.
- a few fixes for rescue= mount option, adding more checks for missing
trees
- fix sleeping in atomic context on qgroup deletion
- fix subvolume deletion on mount
- fix build with M= syntax
- fix checksum mismatch error message for direct io
----------------------------------------------------------------
The following changes since commit 485df75554257e883d0ce39bb886e8212349748e:
btrfs: always pin deleted leaves when there are active tree mod log users (2021-03-16 20:32:22 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.12-rc4-tag
for you to fetch changes up to c1d6abdac46ca8127274bea195d804e3f2cec7ee:
btrfs: fix check_data_csum() error message for direct I/O (2021-03-18 21:25:11 +0100)
----------------------------------------------------------------
David Sterba (1):
btrfs: fix build when using M=fs/btrfs
Filipe Manana (2):
btrfs: fix subvolume/snapshot deletion not triggered on mount
btrfs: fix sleep while in non-sleep context during qgroup removal
Johannes Thumshirn (1):
btrfs: zoned: remove outdated WARN_ON in direct IO
Josef Bacik (3):
btrfs: do not initialize dev stats if we have no dev_root
btrfs: initialize device::fs_info always
btrfs: do not initialize dev replace for bad dev root
Omar Sandoval (1):
btrfs: fix check_data_csum() error message for direct I/O
fs/btrfs/Makefile | 10 ++++++----
fs/btrfs/dev-replace.c | 3 +++
fs/btrfs/disk-io.c | 19 +++++++++++++++++--
fs/btrfs/inode.c | 18 +++++++++---------
fs/btrfs/qgroup.c | 12 ++++++++++--
fs/btrfs/volumes.c | 3 +++
6 files changed, 48 insertions(+), 17 deletions(-)
next reply other threads:[~2021-03-25 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 21:36 David Sterba [this message]
2021-03-25 22:42 ` [GIT PULL] Btrfs fixes for 5.12-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.1616690512.git.dsterba@suse.com \
--to=dsterba@suse.com \
--cc=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 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.