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.9-rc3
Date: Mon, 24 Aug 2020 18:43:43 +0200	[thread overview]
Message-ID: <cover.1598283719.git.dsterba@suse.com> (raw)

Hi,

a few more fixes. Please pull, Thanks.

- fix swapfile activation on subvolumes with deleted snapshots

- error value mixup when removing directory entries from tree log

- fix lzo compression level reset after previous level setting

- fix space cache memory leak after transaction abort

- fix const function attribute

- more error handling improvements

----------------------------------------------------------------
The following changes since commit c57dd1f2f6a7cd1bb61802344f59ccdc5278c983:

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

are available in the Git repository at:

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

for you to fetch changes up to a84d5d429f9eb56f81b388609841ed993f0ddfca:

  btrfs: detect nocow for swap after snapshot delete (2020-08-21 12:21:23 +0200)

----------------------------------------------------------------
Boris Burkov (1):
      btrfs: detect nocow for swap after snapshot delete

David Sterba (1):
      btrfs: use the correct const function attribute for btrfs_get_num_csums

Filipe Manana (1):
      btrfs: fix space cache memory leak after transaction abort

Johannes Thumshirn (1):
      btrfs: handle errors from async submission

Josef Bacik (1):
      btrfs: check the right error variable in btrfs_del_dir_entries_in_log

Marcos Paulo de Souza (1):
      btrfs: reset compression level for lzo on remount

 fs/btrfs/ctree.c            |  2 +-
 fs/btrfs/ctree.h            |  6 +++---
 fs/btrfs/disk-io.c          |  1 +
 fs/btrfs/extent-tree.c      | 17 +++++++++++------
 fs/btrfs/file.c             |  2 +-
 fs/btrfs/free-space-cache.c |  2 +-
 fs/btrfs/inode.c            | 29 ++++++++++++++---------------
 fs/btrfs/super.c            |  1 +
 fs/btrfs/tree-log.c         | 10 ++++++----
 9 files changed, 39 insertions(+), 31 deletions(-)

             reply	other threads:[~2020-08-24 16:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 16:43 David Sterba [this message]
2020-08-24 19:21 ` [GIT PULL] Btrfs fixes for 5.9-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.1598283719.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