From: David Sterba <dsterba@suse.com>
To: torvalds@linux-foundation.org
Cc: linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Btrfs fixes for 6.0-rc2
Date: Fri, 19 Aug 2022 14:00:51 +0200 [thread overview]
Message-ID: <cover.1660908668.git.dsterba@suse.com> (raw)
Hi,
a few short fixes and a lockdep warning fix (needs moving some code).
Please pull, thanks.
- tree-log replay fixes
- fix error handling when looking up extent refs
- fix warning when setting inode number of links
- relocation fixes
- reset block group read-only status when relocation fails
- unset control structure if transaction fails when starting to
process a block group
- add lockdep annotations to fix a warning during relocation where
blocks temporarily belong to another tree and can lead to reversed
dependencies
- tree-checker verifies if extent items don't overlap
----------------------------------------------------------------
The following changes since commit 0b078d9db8793b1bd911e97be854e3c964235c78:
btrfs: don't call btrfs_page_set_checked in finish_compressed_bio_read (2022-07-25 19:56:16 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.0-rc1-tag
for you to fetch changes up to 899b7f69f244e539ea5df1b4d756046337de44a5:
btrfs: tree-checker: check for overlapping extent items (2022-08-17 16:20:25 +0200)
----------------------------------------------------------------
Filipe Manana (2):
btrfs: fix lost error handling when looking up extended ref on log replay
btrfs: fix warning during log replay when bumping inode link count
Josef Bacik (4):
btrfs: reset RO counter on block group if we fail to relocate
btrfs: move lockdep class helpers to locking.c
btrfs: fix lockdep splat with reloc root extent buffers
btrfs: tree-checker: check for overlapping extent items
Zixuan Fu (1):
btrfs: unset reloc control if transaction commit fails in prepare_to_relocate()
fs/btrfs/block-group.c | 4 ++-
fs/btrfs/ctree.c | 3 ++
fs/btrfs/ctree.h | 2 ++
fs/btrfs/disk-io.c | 82 --------------------------------------------
fs/btrfs/disk-io.h | 10 ------
fs/btrfs/extent-tree.c | 18 +++++++++-
fs/btrfs/extent_io.c | 11 +++++-
fs/btrfs/locking.c | 91 +++++++++++++++++++++++++++++++++++++++++++++++++
fs/btrfs/locking.h | 14 ++++++++
fs/btrfs/relocation.c | 9 ++++-
fs/btrfs/tree-checker.c | 25 ++++++++++++--
fs/btrfs/tree-log.c | 8 +++--
12 files changed, 176 insertions(+), 101 deletions(-)
next reply other threads:[~2022-08-19 12:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-19 12:00 David Sterba [this message]
2022-08-19 21:14 ` [GIT PULL] Btrfs fixes for 6.0-rc2 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.1660908668.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 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.