public inbox for linux-kernel@vger.kernel.org
 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-rc3
Date: Mon, 17 May 2021 15:47:35 +0200	[thread overview]
Message-ID: <cover.1621258094.git.dsterba@suse.com> (raw)

Hi,

a few more fixes, please pull. Thanks.

- fix fiemap to print extents that could get misreported due to internal
  extent splitting and logical merging for fiemap output

- fix RCU stalls during delayed iputs

- fix removed dentries still existing after log is synced

----------------------------------------------------------------
The following changes since commit 77364faf21b4105ee5adbb4844fdfb461334d249:

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

are available in the Git repository at:

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

for you to fetch changes up to 54a40fc3a1da21b52dbf19f72fdc27a2ec740760:

  btrfs: fix removed dentries still existing after log is synced (2021-05-14 01:23:04 +0200)

----------------------------------------------------------------
Boris Burkov (1):
      btrfs: return whole extents in fiemap

Filipe Manana (1):
      btrfs: fix removed dentries still existing after log is synced

Johannes Thumshirn (1):
      btrfs: return 0 for dev_extent_hole_check_zoned hole_start in case of error

Josef Bacik (1):
      btrfs: avoid RCU stalls while running delayed iputs

 fs/btrfs/extent_io.c |  7 ++++++-
 fs/btrfs/inode.c     |  1 +
 fs/btrfs/tree-log.c  | 18 ++++++++++++++++++
 fs/btrfs/volumes.c   |  2 +-
 4 files changed, 26 insertions(+), 2 deletions(-)

             reply	other threads:[~2021-05-17 13:50 UTC|newest]

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