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.cz>,
	linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 5.12-rc1, part 2
Date: Fri,  5 Mar 2021 16:55:17 +0100	[thread overview]
Message-ID: <cover.1614954547.git.dsterba@suse.com> (raw)

From: David Sterba <dsterba@suse.cz>

Hi,

more regression fixes and stabilization. Please pull, thanks.

Regressions:

- zoned mode
  - count zone sizes in wider int types
  - fix space accounting for read-only block groups

- subpage: fix page tail zeroing

Fixes:

- fix spurious warning when remounting with free space tree

- fix warning when creating a directory with smack enabled

- ioctl checks for qgroup inheritance when creating a snapshot

- qgroup
  - fix missing unlock on error path in zero range
  - fix amount of released reservation on error
  - fix flushing from unsafe context with open transaction, potentially
    deadlocking

- minor build warning fixes

----------------------------------------------------------------
The following changes since commit 6e37d245994189ba757df7dc2950a44d31421ac6:

  btrfs: zoned: fix deadlock on log sync (2021-02-22 18:08:48 +0100)

are available in the Git repository at:

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

for you to fetch changes up to badae9c86979c459bd7d895d6d7ddc7a01131ff7:

  btrfs: zoned: do not account freed region of read-only block group as zone_unusable (2021-03-04 16:16:58 +0100)

----------------------------------------------------------------
Boris Burkov (1):
      btrfs: fix spurious free_space_tree remount warning

Dan Carpenter (1):
      btrfs: validate qgroup inherit for SNAP_CREATE_V2 ioctl

Filipe Manana (1):
      btrfs: fix warning when creating a directory with smack enabled

Naohiro Aota (2):
      btrfs: zoned: use sector_t for zone sectors
      btrfs: zoned: do not account freed region of read-only block group as zone_unusable

Nikolay Borisov (4):
      btrfs: unlock extents in btrfs_zero_range in case of quota reservation errors
      btrfs: free correct amount of space in btrfs_delayed_inode_reserve_metadata
      btrfs: export and rename qgroup_reserve_meta
      btrfs: don't flush from btrfs_delayed_inode_reserve_metadata

Qu Wenruo (1):
      btrfs: subpage: fix the false data csum mismatch error

Randy Dunlap (1):
      btrfs: ref-verify: use 'inline void' keyword ordering

 fs/btrfs/delayed-inode.c    |  5 +++--
 fs/btrfs/extent_io.c        | 21 ++++++++++++++++-----
 fs/btrfs/file.c             |  5 ++++-
 fs/btrfs/free-space-cache.c |  7 ++++++-
 fs/btrfs/inode.c            |  2 +-
 fs/btrfs/ioctl.c            | 19 ++++++++++++++++++-
 fs/btrfs/qgroup.c           |  8 ++++----
 fs/btrfs/qgroup.h           |  2 ++
 fs/btrfs/ref-verify.c       |  4 ++--
 fs/btrfs/super.c            |  4 ++--
 fs/btrfs/xattr.c            | 31 +++++++++++++++++++++++++++----
 fs/btrfs/zoned.c            |  4 ++--
 12 files changed, 87 insertions(+), 25 deletions(-)

             reply	other threads:[~2021-03-05 15:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 15:55 David Sterba [this message]
2021-03-05 21:58 ` [GIT PULL] Btrfs fixes for 5.12-rc1, 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.1614954547.git.dsterba@suse.com \
    --to=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --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