The Linux Kernel Mailing List
 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 updtes for 6.10, part 2
Date: Fri, 24 May 2024 15:59:18 +0200	[thread overview]
Message-ID: <cover.1716556959.git.dsterba@suse.com> (raw)

Hi,

a few more updates, mostly stability fixes or user visible changes.
Please pull, thanks.

- fix race in zoned mode during device replace that can lead to
  use-after-free

- update return codes and lower message levels for quota rescan where
  it's causing false alerts

- fix unexpected qgroup id reuse under some conditions

- fix condition when looking up extent refs

- add option norecovery (removed in 6.8), the intended replacements
  haven't been used and some aplications still rely on the old one

- build warning fixes

----------------------------------------------------------------
The following changes since commit 0e39c9e524479b85c1b83134df0cfc6e3cb5353a:

  btrfs: qgroup: fix initialization of auto inherit array (2024-05-07 21:31:11 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.10-tag

for you to fetch changes up to 440861b1a03c72cc7be4a307e178dcaa6894479b:

  btrfs: re-introduce 'norecovery' mount option (2024-05-21 15:27:17 +0200)

----------------------------------------------------------------
Boris Burkov (1):
      btrfs: qgroup: fix qgroup id collision across mounts

David Sterba (1):
      btrfs: qgroup: update rescan message levels and error codes

Filipe Manana (2):
      btrfs: zoned: fix use-after-free due to race with dev replace
      btrfs: fix end of tree detection when searching for data extent ref

Lu Yao (1):
      btrfs: scrub: initialize ret in scrub_simple_mirror() to fix compilation warning

Qu Wenruo (1):
      btrfs: re-introduce 'norecovery' mount option

 fs/btrfs/extent-tree.c |  2 +-
 fs/btrfs/qgroup.c      | 32 +++++++++++++++++++++++++-------
 fs/btrfs/scrub.c       |  2 +-
 fs/btrfs/super.c       |  8 ++++++++
 fs/btrfs/zoned.c       | 13 ++++++++++---
 5 files changed, 45 insertions(+), 12 deletions(-)

             reply	other threads:[~2024-05-24 13:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 13:59 David Sterba [this message]
2024-05-24 16:45 ` [GIT PULL] Btrfs updtes for 6.10, 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.1716556959.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