linux-kernel.vger.kernel.org archive mirror
 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.14-rc3
Date: Fri, 23 Jul 2021 21:45:29 +0200	[thread overview]
Message-ID: <cover.1627068865.git.dsterba@suse.com> (raw)

Hi,

a few fixes and one patch to help some block layer API cleanups.
Please pull, thanks.

* skip missing device when running fstrim

* fix unpersisted i_size on fsync after expanding truncate

* fix lock inversion problem when doing qgroup extent tracing

* replace bdgrab/bdput usage, replace gendisk by block_device

----------------------------------------------------------------
The following changes since commit ea32af47f00a046a1f953370514d6d946efe0152:

  btrfs: zoned: fix wrong mutex unlock on failure to allocate log root tree (2021-07-07 18:27:44 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.14-rc2-tag

for you to fetch changes up to c7c3a6dcb1efd52949acc1e640be9aad1206a13a:

  btrfs: store a block_device in struct btrfs_ordered_extent (2021-07-22 15:50:15 +0200)

----------------------------------------------------------------
Anand Jain (1):
      btrfs: check for missing device in btrfs_trim_fs

Christoph Hellwig (1):
      btrfs: store a block_device in struct btrfs_ordered_extent

Filipe Manana (2):
      btrfs: fix unpersisted i_size on fsync after expanding truncate
      btrfs: fix lock inversion problem when doing qgroup extent tracing

 fs/btrfs/backref.c            |  6 +++---
 fs/btrfs/backref.h            |  3 ++-
 fs/btrfs/delayed-ref.c        |  4 ++--
 fs/btrfs/extent-tree.c        |  3 +++
 fs/btrfs/inode.c              |  2 +-
 fs/btrfs/ordered-data.c       |  2 --
 fs/btrfs/ordered-data.h       |  3 +--
 fs/btrfs/qgroup.c             | 38 ++++++++++++++++++++++++++++++--------
 fs/btrfs/qgroup.h             |  2 +-
 fs/btrfs/tests/qgroup-tests.c | 20 ++++++++++----------
 fs/btrfs/tree-log.c           | 31 ++++++++++++++++++++++---------
 fs/btrfs/zoned.c              | 12 ++++--------
 12 files changed, 79 insertions(+), 47 deletions(-)

             reply	other threads:[~2021-07-23 19:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-23 19:45 David Sterba [this message]
2021-07-24  0:43 ` [GIT PULL] Btrfs fixes for 5.14-rc3 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.1627068865.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;
as well as URLs for NNTP newsgroup(s).