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 6.4-rc7, part 2
Date: Fri, 16 Jun 2023 18:06:50 +0200 [thread overview]
Message-ID: <cover.1686930269.git.dsterba@suse.com> (raw)
Hi,
here's the second part, two fixes for NOCOW files, a regression fix in
scrub and an assertion fix. Please pull, thanks.
- NOCOW fixes:
- keep length of iomap direct io request in case of a failure
- properly pass mode of extent reference checking, this can break
some cases for swapfile
- fix error value confusion when scrubbing a stripe
- convert assertion to a proper error handling when loading global
roots, reported by syzbot
----------------------------------------------------------------
The following changes since commit 79b8ee702c918f1936e17cc53e14bec388ce1045:
btrfs: scrub: also report errors hit during the initial read (2023-06-08 14:34:01 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.4-rc6-tag
for you to fetch changes up to b50f2d048ecf1512ff85128ea4153bceb0e60590:
btrfs: scrub: fix a return value overwrite in scrub_stripe() (2023-06-14 18:30:30 +0200)
----------------------------------------------------------------
Chris Mason (1):
btrfs: can_nocow_file_extent should pass down args->strict from callers
Christoph Hellwig (1):
btrfs: fix iomap_begin length for nocow writes
Qu Wenruo (2):
btrfs: do not ASSERT() on duplicated global roots
btrfs: scrub: fix a return value overwrite in scrub_stripe()
fs/btrfs/disk-io.c | 10 ++++++++--
fs/btrfs/inode.c | 20 +++++++++++++-------
fs/btrfs/scrub.c | 2 +-
3 files changed, 22 insertions(+), 10 deletions(-)
next reply other threads:[~2023-06-16 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 16:06 David Sterba [this message]
2023-06-16 20:27 ` [GIT PULL] Btrfs fixes 6.4-rc7, 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.1686930269.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.