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 6.1-rc4
Date: Mon, 31 Oct 2022 15:00:06 +0100 [thread overview]
Message-ID: <cover.1667223120.git.dsterba@suse.com> (raw)
Hi,
a few more fixes and regression fixes. Please pull, thannk.
- fix a corner case when handling tree-mod-log chagnes in reallocated
notes
- fix crash on raid0 filesystems created with <5.4 mkfs.btrfs that could
lead to division by zero
- add missing supper block checksum verification after thawing
filesystem
- handle one more case in send when dealing with orphan files
- fix parameter type mismatch for generation when reading dentry
- improved error handling in raid56 code
- better struct bio packing after recent cleanups
----------------------------------------------------------------
The following changes since commit 4efb365a3f04d0bee7833f168b0b00a15edefeac:
MAINTAINERS: update btrfs website links and files (2022-10-14 13:54:21 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.1-rc3-tag
for you to fetch changes up to 76a66ba101329316a5d7f4275070be22eb85fdf2:
btrfs: don't use btrfs_chunk::sub_stripes from disk (2022-10-25 10:17:33 +0200)
----------------------------------------------------------------
BingJing Chang (1):
btrfs: send: fix send failure of a subcase of orphan inodes
David Sterba (2):
btrfs: reorder btrfs_bio for better packing
btrfs: fix type of parameter generation in btrfs_get_dentry
Josef Bacik (1):
btrfs: fix tree mod log mishandling of reallocated nodes
Qu Wenruo (4):
btrfs: raid56: properly handle the error when unable to find the missing stripe
btrfs: raid56: avoid double freeing for rbio if full_stripe_write() failed
btrfs: make thaw time super block check to also verify checksum
btrfs: don't use btrfs_chunk::sub_stripes from disk
fs/btrfs/disk-io.c | 10 ++++------
fs/btrfs/disk-io.h | 2 ++
fs/btrfs/export.c | 2 +-
fs/btrfs/export.h | 2 +-
fs/btrfs/extent-tree.c | 25 +++++++++++++------------
fs/btrfs/raid56.c | 18 +++++++++++-------
fs/btrfs/send.c | 24 +++++++++++++-----------
fs/btrfs/super.c | 16 ++++++++++++++++
fs/btrfs/volumes.c | 12 +++++++++++-
fs/btrfs/volumes.h | 2 +-
10 files changed, 73 insertions(+), 40 deletions(-)
next reply other threads:[~2022-10-31 14:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 14:00 David Sterba [this message]
2022-10-31 19:43 ` [GIT PULL] Btrfs fixes for 6.1-rc4 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.1667223120.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.