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.17-rc3
Date: Fri,  4 Feb 2022 20:25:22 +0100	[thread overview]
Message-ID: <cover.1644001677.git.dsterba@suse.com> (raw)

Hi,

a few fixes and error handling improvements. Please pull, thanks.

* fix deadlock between quota disable and qgroup rescan worker

* fix use-after-free after failure to create a snapshot

* skip warning on unmount after log cleanup failure

* don't start transaction for scrub if the fs is mounted read-only

* tree checker verifies item sizes

----------------------------------------------------------------
The following changes since commit 27cdfde181bcacd226c230b2fd831f6f5b8c215f:

  btrfs: update writeback index when starting defrag (2022-01-24 18:16:28 +0100)

are available in the Git repository at:

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

for you to fetch changes up to 40cdc509877bacb438213b83c7541c5e24a1d9ec:

  btrfs: skip reserved bytes warning on unmount after log cleanup failure (2022-01-31 16:06:50 +0100)

----------------------------------------------------------------
Filipe Manana (2):
      btrfs: fix use-after-free after failure to create a snapshot
      btrfs: skip reserved bytes warning on unmount after log cleanup failure

Qu Wenruo (1):
      btrfs: don't start transaction for scrub if the fs is mounted read-only

Shin'ichiro Kawasaki (1):
      btrfs: fix deadlock between quota disable and qgroup rescan worker

Su Yue (2):
      btrfs: tree-checker: check item_size for inode_item
      btrfs: tree-checker: check item_size for dev_item

Tom Rix (1):
      btrfs: fix use of uninitialized variable at rm device ioctl

 fs/btrfs/block-group.c  | 39 +++++++++++++++++++++++++++++++++++++--
 fs/btrfs/ctree.h        |  6 ++++++
 fs/btrfs/ioctl.c        |  7 ++-----
 fs/btrfs/qgroup.c       | 21 +++++++++++++++++++--
 fs/btrfs/transaction.c  | 24 ++++++++++++++++++++++++
 fs/btrfs/transaction.h  |  2 ++
 fs/btrfs/tree-checker.c | 15 +++++++++++++++
 fs/btrfs/tree-log.c     | 23 +++++++++++++++++++++++
 8 files changed, 128 insertions(+), 9 deletions(-)

             reply	other threads:[~2022-02-04 19:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 19:25 David Sterba [this message]
2022-02-04 20:34 ` [GIT PULL] Btrfs fixes for 5.17-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.1644001677.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