public inbox for linux-kernel@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 fixes for v6.2-rc8
Date: Mon,  6 Feb 2023 20:50:09 +0100	[thread overview]
Message-ID: <cover.1675710734.git.dsterba@suse.com> (raw)

Hi,

a few more short fixes. Please pull, thanks.

- explicitly initialize zlib work memory to fix a KCSAN warning

- limit number of send clones by maximum memory allocated

- limit device size extent in case it device shrink races with chunk
  allocation

- raid56 fixes
  - fix copy&paste error in RAID6 stripe recovery
  - make error bitmap update atomic

----------------------------------------------------------------
The following changes since commit b7adbf9ada3513d2092362c8eac5cddc5b651f5c:

  btrfs: fix race between quota rescan and disable leading to NULL pointer deref (2023-01-16 19:46:54 +0100)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-6.2-rc7-tag

for you to fetch changes up to a9ad4d87aa263de36895402b66115a3a4b88bf1c:

  btrfs: raid56: make error_bitmap update atomic (2023-01-27 14:57:10 +0100)

----------------------------------------------------------------
Alexander Potapenko (1):
      btrfs: zlib: zero-initialize zlib workspace

David Sterba (1):
      btrfs: send: limit number of clones and allocated memory size

Josef Bacik (1):
      btrfs: limit device extents to the device size

Qu Wenruo (1):
      btrfs: raid56: make error_bitmap update atomic

Tanmay Bhushan (1):
      btrfs: raid56: fix stripes if vertical errors are found

 fs/btrfs/raid56.c  | 14 +++++++++++---
 fs/btrfs/send.c    |  6 +++---
 fs/btrfs/volumes.c |  6 +++++-
 fs/btrfs/zlib.c    |  2 +-
 4 files changed, 20 insertions(+), 8 deletions(-)

             reply	other threads:[~2023-02-06 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-06 19:50 David Sterba [this message]
2023-02-06 20:15 ` [GIT PULL] Btrfs fixes for v6.2-rc8 Linus Torvalds
2023-02-06 20:18   ` David Sterba
2023-02-06 22:22 ` 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.1675710734.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