public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
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-rc7, part 2
Date: Fri, 23 Jun 2023 20:58:01 +0200	[thread overview]
Message-ID: <cover.1687448378.git.dsterba@suse.com> (raw)

Hi,

unfortunately the recent u32 overflow fix was not complete, there was
one conversion left, assertion not triggered by my tests but caught by
Qu's fstests case. The "cleanup for later" has been promoted to a proper
fix and wraps all uses of the stripe left shift so the diffstat has grown
but leaves no potentially problematic uses. We should have done it that
way before, sorry.

Please pull, thanks.

----------------------------------------------------------------
The following changes since commit a7299a18a179a9713651fce9ad00972a633c14a9:

  btrfs: fix u32 overflows when left shifting stripe_nr (2023-06-20 19:10:31 +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 cb091225a538005965b7c59c7c33ebe5358a5815:

  btrfs: fix remaining u32 overflows when left shifting stripe_nr (2023-06-22 17:03:55 +0200)

----------------------------------------------------------------
Qu Wenruo (1):
      btrfs: fix remaining u32 overflows when left shifting stripe_nr

 fs/btrfs/block-group.c  |  2 +-
 fs/btrfs/scrub.c        | 22 +++++++++++-----------
 fs/btrfs/tree-checker.c |  4 ++--
 fs/btrfs/volumes.c      | 29 +++++++++++++++--------------
 fs/btrfs/volumes.h      | 11 +++++++++++
 5 files changed, 40 insertions(+), 28 deletions(-)

             reply	other threads:[~2023-06-23 19:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23 18:58 David Sterba [this message]
2023-06-23 23:53 ` [GIT PULL] Btrfs fix for 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.1687448378.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