Linux Btrfs filesystem development
 help / color / mirror / Atom feed
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 5.13-rc2
Date: Mon, 10 May 2021 23:06:13 +0200	[thread overview]
Message-ID: <cover.1620679798.git.dsterba@suse.com> (raw)

Hi,

first batch of various fixes, here's a list of notable ones:

- fix unmountable seed device after fstrim

- fix silent data loss in zoned mode due to ordered extent splitting

- fix race leading to unpersisted data and metadata on fsync

- fix deadlock when cloning inline extents and using qgroups

Please pull, thanks.

----------------------------------------------------------------
The following changes since commit 18bb8bbf13c1839b43c9e09e76d397b753989af2:

  btrfs: zoned: automatically reclaim zones (2021-04-20 20:46:31 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.13-rc1-tag

for you to fetch changes up to 77364faf21b4105ee5adbb4844fdfb461334d249:

  btrfs: initialize return variable in cleanup_free_space_cache_v1 (2021-05-04 18:05:15 +0200)

----------------------------------------------------------------
Anand Jain (1):
      btrfs: fix unmountable seed device after fstrim

Filipe Manana (4):
      btrfs: zoned: fix silent data loss after failure splitting ordered extent
      btrfs: do not consider send context as valid when trying to flush qgroups
      btrfs: fix race leading to unpersisted data and metadata on fsync
      btrfs: fix deadlock when cloning inline extents and using qgroups

Naohiro Aota (1):
      btrfs: zoned: sanity check zone type

Tom Rix (1):
      btrfs: initialize return variable in cleanup_free_space_cache_v1

 fs/btrfs/ctree.h            |  2 +-
 fs/btrfs/extent-tree.c      |  6 +++++-
 fs/btrfs/file.c             | 35 +++++++++++++++++++++++++----------
 fs/btrfs/free-space-cache.c |  2 +-
 fs/btrfs/inode.c            |  4 ++--
 fs/btrfs/ioctl.c            |  2 +-
 fs/btrfs/ordered-data.c     |  2 +-
 fs/btrfs/qgroup.c           | 16 ++++++++++------
 fs/btrfs/send.c             |  4 ++--
 fs/btrfs/tree-log.c         |  3 ++-
 fs/btrfs/zoned.c            |  5 +++++
 11 files changed, 55 insertions(+), 26 deletions(-)

             reply	other threads:[~2021-05-10 21:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-10 21:06 David Sterba [this message]
2021-05-10 21:15 ` [GIT PULL] Btrfs fixes for 5.13-rc2 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.1620679798.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