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-rc5
Date: Tue, 30 May 2023 22:13:38 +0200 [thread overview]
Message-ID: <cover.1685474426.git.dsterba@suse.com> (raw)
Hi,
please pull one bug fix and two build warning fixes, thanks.
- call proper end bio callback for metadata RAID0 in a rare case of an
unaligned block
- build warning fixes
- fix uninitialized variable (reported by gcc 10.2)
- fix warning about potential access beyond array bounds on mips64
with 64k pages (runtime check would not allow that)
----------------------------------------------------------------
The following changes since commit 597441b3436a43011f31ce71dc0a6c0bf5ce958a:
btrfs: use nofs when cleaning up aborted transactions (2023-05-17 13:08:28 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.4-rc4-tag
for you to fetch changes up to 5ad9b4719fc9bc4715c7e19875a962095b0577e7:
btrfs: fix csum_tree_block page iteration to avoid tripping on -Werror=array-bounds (2023-05-26 23:24:55 +0200)
----------------------------------------------------------------
Christoph Hellwig (1):
btrfs: call btrfs_orig_bbio_end_io in btrfs_end_bio_work
Shida Zhang (1):
btrfs: fix an uninitialized variable warning in btrfs_log_inode
pengfuyuan (1):
btrfs: fix csum_tree_block page iteration to avoid tripping on -Werror=array-bounds
fs/btrfs/bio.c | 2 +-
fs/btrfs/disk-io.c | 2 +-
fs/btrfs/tree-log.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
next reply other threads:[~2023-05-30 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 20:13 David Sterba [this message]
2023-05-30 21:40 ` [GIT PULL] Btrfs fixes for 6.4-rc5 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.1685474426.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