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.4-rc3
Date: Thu, 10 Oct 2019 16:48:51 +0200	[thread overview]
Message-ID: <cover.1570718349.git.dsterba@suse.com> (raw)

Hi,

a few more stabitly fixes, one build warning fix.

Changes:

- fix inode allocation under NOFS context

- fix leak in fiemap due to concurrent append writes

- fix log-root tree updates

- fix balance convert of single profile on 32bit architectures

- silence false positive warning on old GCCs (code moved in rc1)

Please pull, thanks.

----------------------------------------------------------------
The following changes since commit d4e204948fe3e0dc8e1fbf3f8f3290c9c2823be3:

  btrfs: qgroup: Fix reserved data space leak if we have multiple reserve calls (2019-09-27 15:24:34 +0200)

are available in the Git repository at:

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

for you to fetch changes up to 431d39887d6273d6d84edf3c2eab09f4200e788a:

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

----------------------------------------------------------------
Austin Kim (1):
      btrfs: silence maybe-uninitialized warning in clone_range

Filipe Manana (1):
      Btrfs: fix memory leak due to concurrent append writes with fiemap

Josef Bacik (3):
      btrfs: fix incorrect updating of log root tree
      btrfs: allocate new inode in NOFS context
      btrfs: fix uninitialized ret in ref-verify

Zygo Blaxell (1):
      btrfs: fix balance convert to single on 32-bit host CPUs

 fs/btrfs/file.c       | 13 ++++++++++++-
 fs/btrfs/inode.c      |  3 +++
 fs/btrfs/ref-verify.c |  2 +-
 fs/btrfs/send.c       |  2 +-
 fs/btrfs/tree-log.c   | 36 +++++++++++++++++++++++++++---------
 fs/btrfs/volumes.c    |  6 +++++-
 6 files changed, 49 insertions(+), 13 deletions(-)

             reply	other threads:[~2019-10-10 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-10 14:48 David Sterba [this message]
2019-10-10 15:45 ` [GIT PULL] Btrfs fixes for 5.4-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.1570718349.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.