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.4-rc4
Date: Fri, 26 May 2023 14:48:44 +0200 [thread overview]
Message-ID: <cover.1685104958.git.dsterba@suse.com> (raw)
Hi,
a few more fixes, please pull thanks.
- handle memory allocation error in checksumming helper (reported by
syzbot)
- fix lockdep splat when aborting a transaction, add NOFS protection
around invalidate_inode_pages2 that could allocate with GFP_KERNEL
- reduce chances to hit an ENOSPC during scrub with RAID56 profiles
----------------------------------------------------------------
The following changes since commit 1d6a4fc85717677e00fefffd847a50fc5928ce69:
btrfs: make clear_cache mount option to rebuild FST without disabling it (2023-05-10 14:51:27 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.4-rc3-tag
for you to fetch changes up to 597441b3436a43011f31ce71dc0a6c0bf5ce958a:
btrfs: use nofs when cleaning up aborted transactions (2023-05-17 13:08:28 +0200)
----------------------------------------------------------------
Johannes Thumshirn (1):
btrfs: handle memory allocation failure in btrfs_csum_one_bio
Josef Bacik (1):
btrfs: use nofs when cleaning up aborted transactions
Qu Wenruo (1):
btrfs: scrub: try harder to mark RAID56 block groups read-only
fs/btrfs/block-group.c | 14 ++++++++++++--
fs/btrfs/disk-io.c | 9 +++++++++
fs/btrfs/file-item.c | 4 +++-
fs/btrfs/scrub.c | 9 ++++++++-
4 files changed, 32 insertions(+), 4 deletions(-)
next reply other threads:[~2023-05-26 12:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 12:48 David Sterba [this message]
2023-05-26 20:38 ` [GIT PULL] Btrfs fixes for 6.4-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.1685104958.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