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.8-rc3
Date: Tue, 23 Jun 2020 15:53:45 +0200	[thread overview]
Message-ID: <cover.1592918083.git.dsterba@suse.com> (raw)

Hi,

a number of fixes, located in two areas, one performance fix and one
fixup for better integration with another patchset.

Please pull, thanks.

- bug fixes in nowait aio:
  - fix snapshot creation hang after nowait-aio was used
  - fix failure to write to prealloc extent past EOF
  - don't block when extent range is locked

- block group fixes:
  - relocation failure when scrub runs in parallel
  - refcount fix when removing fails
  - fix race between removal and creation
  - space accounting fixes

- reinstante fast path check for log tree at unlink time, fixes
  performance drop up to 30% in REAIM

- kzfree/kfree fixup to ease treewide patchset renaming kzfree

----------------------------------------------------------------
The following changes since commit 55e20bd12a56e06c38b953177bb162cbbaa96004:

  Revert "btrfs: switch to iomap_dio_rw() for dio" (2020-06-14 01:19:02 +0200)

are available in the Git repository at:

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

for you to fetch changes up to b091f7fede97cc64f7aaad3eeb37965aebee3082:

  btrfs: use kfree() in btrfs_ioctl_get_subvol_info() (2020-06-16 19:24:03 +0200)

----------------------------------------------------------------
Filipe Manana (9):
      btrfs: fix a block group ref counter leak after failure to remove block group
      btrfs: fix race between block group removal and block group creation
      btrfs: fix data block group relocation failure due to concurrent scrub
      btrfs: fix bytes_may_use underflow when running balance and scrub in parallel
      btrfs: check if a log root exists before locking the log_mutex on unlink
      btrfs: fix hang on snapshot creation after RWF_NOWAIT write
      btrfs: fix failure of RWF_NOWAIT write into prealloc extent beyond eof
      btrfs: fix RWF_NOWAIT write not failling when we need to cow
      btrfs: fix RWF_NOWAIT writes blocking on extent locks and waiting for IO

Waiman Long (1):
      btrfs: use kfree() in btrfs_ioctl_get_subvol_info()

 fs/btrfs/block-group.c | 44 +++++++++++++++++++++++++++-----------------
 fs/btrfs/ctree.h       |  2 ++
 fs/btrfs/file.c        | 46 +++++++++++++++++++++++++++++++++++++---------
 fs/btrfs/inode.c       | 39 ++++++++++++++++++++++++++++++---------
 fs/btrfs/ioctl.c       |  2 +-
 fs/btrfs/tree-log.c    |  5 +++++
 6 files changed, 102 insertions(+), 36 deletions(-)

             reply	other threads:[~2020-06-23 13:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-23 13:53 David Sterba [this message]
2020-06-23 16:50 ` [GIT PULL] Btrfs fixes for 5.8-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.1592918083.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