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 fix for 6.4-rc8
Date: Tue, 20 Jun 2023 20:24:01 +0200 [thread overview]
Message-ID: <cover.1687283675.git.dsterba@suse.com> (raw)
Hi,
one more regression fix for an assertion failure that uncovered a nasty
problem with stripe calculations. This is caused by a u32 overflow when
there are enough devices. The fstests require 6 so this hasn't been
caught, I was able to hit it with 8.
The fix is minimal and only adds u64 casts, we'll clean that up later. I
did various additional tests to be sure. Please pull, thanks.
----------------------------------------------------------------
The following changes since commit b50f2d048ecf1512ff85128ea4153bceb0e60590:
btrfs: scrub: fix a return value overwrite in scrub_stripe() (2023-06-14 18:30:30 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.4-rc7-tag
for you to fetch changes up to a7299a18a179a9713651fce9ad00972a633c14a9:
btrfs: fix u32 overflows when left shifting stripe_nr (2023-06-20 19:10:31 +0200)
----------------------------------------------------------------
Qu Wenruo (1):
btrfs: fix u32 overflows when left shifting stripe_nr
fs/btrfs/volumes.c | 12 +++++++-----
1 file changed, 7 insertions(+), 5 deletions(-)
next reply other threads:[~2023-06-20 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 18:24 David Sterba [this message]
2023-06-20 19:00 ` [GIT PULL] Btrfs fix for 6.4-rc8 Linus Torvalds
2023-06-20 20:06 ` David Sterba
2023-06-20 22:53 ` 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.1687283675.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.