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.3-rc5
Date: Sun, 2 Apr 2023 19:34:12 +0200 [thread overview]
Message-ID: <cover.1680455513.git.dsterba@suse.com> (raw)
Hi,
a few more fixes, for stable trees. Please pull, thanks.
- scan block devices in non-exclusive mode to avoid temporary mkfs
failures
- fix race between quota disable and quota assign ioctls
- fix deadlock when aborting transaction during relocation with scrub
- ignore fiemap path cache when there are multiple paths for a node
----------------------------------------------------------------
The following changes since commit e15acc25880cf048dba9df94d76ed7e7e10040e6:
btrfs: zoned: drop space_info->active_total_bytes (2023-03-15 20:51:07 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.3-rc4-tag
for you to fetch changes up to 2280d425ba3599bdd85c41bd0ec8ba568f00c032:
btrfs: ignore fiemap path cache when there are multiple paths for a node (2023-03-29 01:16:23 +0200)
----------------------------------------------------------------
Anand Jain (1):
btrfs: scan device in non-exclusive mode
Filipe Manana (3):
btrfs: fix race between quota disable and quota assign ioctls
btrfs: fix deadlock when aborting transaction during relocation with scrub
btrfs: ignore fiemap path cache when there are multiple paths for a node
fs/btrfs/backref.c | 85 +++++++++++++++++++++++++++++++++++++-------------
fs/btrfs/ioctl.c | 2 ++
fs/btrfs/qgroup.c | 11 ++++++-
fs/btrfs/transaction.c | 15 ++++++++-
fs/btrfs/volumes.c | 20 ++++++++++--
5 files changed, 107 insertions(+), 26 deletions(-)
next reply other threads:[~2023-04-02 17:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 17:34 David Sterba [this message]
2023-04-02 18:02 ` [GIT PULL] Btrfs fixes for 6.3-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.1680455513.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox