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.17-rc7
Date: Sun,  6 Mar 2022 17:32:30 +0100	[thread overview]
Message-ID: <cover.1646581845.git.dsterba@suse.com> (raw)

Hi,

a few more fixes for various problems that have user visible effects or
seem to be urgent. Please pull, thanks.

* fix corruption when combining DIO and non-blocking iouring over
  multiple extents (seen on MariaDB)

* fix relocation crash due to premature return from commit

* fix quota deadlock between rescan and qgroup removal

* fix item data bounds checks in tree-checker (found on a fuzzed image)

* fix fsync of prealloc extents after EOF

* add missing run of delayed items after unlink during log replay

* don't start relocation until snapshot drop is finished

* fix reversed condition for subpage writers locking

* fix warning on page error

----------------------------------------------------------------
The following changes since commit 558732df2122092259ab4ef85594bee11dbb9104:

  btrfs: reduce extent threshold for autodefrag (2022-02-24 16:11:28 +0100)

are available in the Git repository at:

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

for you to fetch changes up to ca93e44bfb5fd7996b76f0f544999171f647f93b:

  btrfs: fallback to blocking mode when doing async dio over multiple extents (2022-03-04 15:09:21 +0100)

----------------------------------------------------------------
Filipe Manana (3):
      btrfs: fix lost prealloc extents beyond eof after full fsync
      btrfs: add missing run of delayed items after unlink during log replay
      btrfs: fallback to blocking mode when doing async dio over multiple extents

Josef Bacik (2):
      btrfs: do not WARN_ON() if we have PageError set
      btrfs: do not start relocation until in progress drops are done

Omar Sandoval (1):
      btrfs: fix relocation crash due to premature return from btrfs_commit_transaction()

Qu Wenruo (1):
      btrfs: subpage: fix a wrong check on subpage->writers

Sidong Yang (1):
      btrfs: qgroup: fix deadlock between rescan worker and remove qgroup

Su Yue (1):
      btrfs: tree-checker: use u64 for item data end to avoid overflow

 fs/btrfs/ctree.h        | 10 ++++++++
 fs/btrfs/disk-io.c      | 10 ++++++++
 fs/btrfs/extent-tree.c  | 10 ++++++++
 fs/btrfs/extent_io.c    | 16 +++++++++---
 fs/btrfs/inode.c        | 28 +++++++++++++++++++++
 fs/btrfs/qgroup.c       |  9 ++++++-
 fs/btrfs/relocation.c   | 13 ++++++++++
 fs/btrfs/root-tree.c    | 15 ++++++++++++
 fs/btrfs/subpage.c      |  2 +-
 fs/btrfs/transaction.c  | 65 +++++++++++++++++++++++++++++++++++++++++++++++--
 fs/btrfs/transaction.h  |  1 +
 fs/btrfs/tree-checker.c | 18 +++++++-------
 fs/btrfs/tree-log.c     | 61 +++++++++++++++++++++++++++++++++++++---------
 13 files changed, 230 insertions(+), 28 deletions(-)

             reply	other threads:[~2022-03-06 16:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-06 16:32 David Sterba [this message]
2022-03-06 20:34 ` [GIT PULL] Btrfs fixes for 5.17-rc7 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.1646581845.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.