All of lore.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.5-rc7
Date: Fri, 17 Jan 2020 19:39:20 +0100	[thread overview]
Message-ID: <cover.1579282274.git.dsterba@suse.com> (raw)

Hi,

please pull a few more fixes that have been in the works during last 2
weeks.  All have a user visible effect and are stable material. Thanks.

* scrub: properly update progress after calling cancel ioctl, calling
  'resume' would start from the beginning otherwise

* fix subvolume reference removal, after moving out of the original path
  the reference is not recognized and will lead to transaction abort

* fix reloc root lifetime checks, could lead to crashes when there's
  subvolume cleaning running in parallel

* fix memory leak when quotas get disabled in the middle of extent
  accounting

* fix transaction abort in case of balance being started on degraded mount
  on eg. RAID1

----------------------------------------------------------------
The following changes since commit de7999afedff02c6631feab3ea726a0e8f8c3d40:

  Btrfs: fix infinite loop during nocow writeback due to race (2019-12-30 16:13:20 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.5-rc6-tag

for you to fetch changes up to b35cf1f0bf1f2b0b193093338414b9bd63b29015:

  btrfs: check rw_devices, not num_devices for balance (2020-01-17 15:40:54 +0100)

----------------------------------------------------------------
Filipe Manana (1):
      Btrfs: always copy scrub arguments back to user space

Johannes Thumshirn (1):
      btrfs: fix memory leak in qgroup accounting

Josef Bacik (4):
      btrfs: rework arguments of btrfs_unlink_subvol
      btrfs: fix invalid removal of root ref
      btrfs: do not delete mismatched root refs
      btrfs: check rw_devices, not num_devices for balance

Qu Wenruo (1):
      btrfs: relocation: fix reloc_root lifespan and access

 fs/btrfs/inode.c      | 73 +++++++++++++++++++++++++++------------------------
 fs/btrfs/ioctl.c      | 14 +++++++++-
 fs/btrfs/qgroup.c     |  6 ++++-
 fs/btrfs/relocation.c | 51 +++++++++++++++++++++++++++++++----
 fs/btrfs/root-tree.c  | 10 ++++---
 fs/btrfs/volumes.c    |  6 ++++-
 6 files changed, 114 insertions(+), 46 deletions(-)

             reply	other threads:[~2020-01-17 18:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 18:39 David Sterba [this message]
2020-01-17 20:00 ` [GIT PULL] Btrfs fixes for 5.5-rc7 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.1579282274.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.