linux-kernel.vger.kernel.org archive mirror
 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 updates for 5.9, part 2
Date: Thu, 13 Aug 2020 15:52:05 +0200	[thread overview]
Message-ID: <cover.1597326304.git.dsterba@suse.com> (raw)

Hi,

second batch with one minor update, the rest are fixes that have arrived
a bit late for the first batch. There are also some recent fixes for
bugs that were discovered during the merge window and pop up during
testing.

Please pull, thanks.

Fixes:

- fix compression messages when remounting with different level or
  compression algorithm

- tree-log: fix some memory leaks on error handling paths

- restore I_VERSION on remount

- fix return values and error code mixups

- fix umount crash with quotas enabled when removing sysfs files

- fix trim range on a shrunk device

User visible changes:

- show correct subvolume path in /proc/mounts for bind mounts

----------------------------------------------------------------
The following changes since commit 5e548b32018d96c377fda4bdac2bf511a448ca67:

  btrfs: do not set the full sync flag on the inode during page release (2020-07-27 12:55:48 +0200)

are available in the Git repository at:

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

for you to fetch changes up to c57dd1f2f6a7cd1bb61802344f59ccdc5278c983:

  btrfs: trim: fix underflow in trim length to prevent access beyond device boundary (2020-08-12 10:15:58 +0200)

----------------------------------------------------------------
Boleyn Su (1):
      btrfs: check correct variable after allocation in btrfs_backref_iter_alloc

David Sterba (1):
      btrfs: fix messages after changing compression level by remount

Filipe Manana (1):
      btrfs: fix memory leaks after failure to lookup checksums during inode logging

Josef Bacik (3):
      btrfs: only search for left_info if there is no right_info in try_merge_free_space
      btrfs: don't show full path of bind mounts in subvol=
      btrfs: make sure SB_I_VERSION doesn't get unset by remount

Pavel Machek (1):
      btrfs: fix return value mixup in btrfs_get_extent

Qu Wenruo (3):
      btrfs: inode: fix NULL pointer dereference if inode doesn't need compression
      btrfs: sysfs: fix NULL pointer dereference at btrfs_sysfs_del_qgroups()
      btrfs: trim: fix underflow in trim length to prevent access beyond device boundary

 fs/btrfs/backref.c          |  2 +-
 fs/btrfs/extent-io-tree.h   |  2 ++
 fs/btrfs/extent-tree.c      | 14 ++++++++++++++
 fs/btrfs/free-space-cache.c |  4 ++--
 fs/btrfs/inode.c            | 18 ++++++++++++------
 fs/btrfs/super.c            | 30 +++++++++++++++++++++++-------
 fs/btrfs/sysfs.c            |  8 +++++---
 fs/btrfs/tree-log.c         |  8 ++------
 fs/btrfs/volumes.c          |  4 ++++
 9 files changed, 65 insertions(+), 25 deletions(-)

             reply	other threads:[~2020-08-13 13:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-13 13:52 David Sterba [this message]
2020-08-13 19:47 ` [GIT PULL] Btrfs updates for 5.9, part 2 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.1597326304.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;
as well as URLs for NNTP newsgroup(s).