mirror of https://lore.kernel.org/lkml/
 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.4-rc5
Date: Tue, 22 Oct 2019 15:52:07 +0200	[thread overview]
Message-ID: <cover.1571751313.git.dsterba@suse.com> (raw)

Hi,

please pull the following updates, all stable material.
Thanks.

Changes:

* fixes of error handling cleanup of metadata accounting with qgroups
  enabled

* fix swapped values for qgroup tracepoints

* fix during file sync, the full-sync status might get dropped
  externally, eg. by background witeback under some circumstances

* don't start unused worker thread, functionality removed already

----------------------------------------------------------------
The following changes since commit 431d39887d6273d6d84edf3c2eab09f4200e788a:

  btrfs: silence maybe-uninitialized warning in clone_range (2019-10-08 13:14:55 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.4-rc4-tag

for you to fetch changes up to ba0b084ac309283db6e329785c1dc4f45fdbd379:

  Btrfs: check for the full sync flag while holding the inode lock during fsync (2019-10-17 20:36:02 +0200)

----------------------------------------------------------------
David Sterba (1):
      btrfs: don't needlessly create extent-refs kernel thread

Filipe Manana (3):
      Btrfs: add missing extents release on file extent cluster relocation error
      Btrfs: fix qgroup double free after failure to reserve metadata for delalloc
      Btrfs: check for the full sync flag while holding the inode lock during fsync

Qu Wenruo (4):
      btrfs: block-group: Fix a memory leak due to missing btrfs_put_block_group()
      btrfs: qgroup: Always free PREALLOC META reserve in btrfs_delalloc_release_extents()
      btrfs: tracepoints: Fix wrong parameter order for qgroup events
      btrfs: tracepoints: Fix bad entry members of qgroup events

 fs/btrfs/block-group.c       |  1 +
 fs/btrfs/ctree.h             |  5 +----
 fs/btrfs/delalloc-space.c    |  7 ++-----
 fs/btrfs/disk-io.c           |  6 ------
 fs/btrfs/file.c              | 43 ++++++++++++++++++++-----------------------
 fs/btrfs/inode-map.c         |  4 ++--
 fs/btrfs/inode.c             | 12 ++++++------
 fs/btrfs/ioctl.c             |  6 ++----
 fs/btrfs/qgroup.c            |  4 ++--
 fs/btrfs/relocation.c        |  9 +++++----
 include/trace/events/btrfs.h |  3 ++-
 11 files changed, 43 insertions(+), 57 deletions(-)

             reply	other threads:[~2019-10-22 13:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-22 13:52 David Sterba [this message]
2019-10-22 15:35 ` David Sterba
2019-10-23 10:25 ` 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.1571751313.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

all inboxes | Powered by JetHome®