mirror of https://lore.kernel.org/lkml/
 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] Fixes for btrfs 5.19-rc4
Date: Tue, 21 Jun 2022 14:41:15 +0200	[thread overview]
Message-ID: <cover.1655815078.git.dsterba@suse.com> (raw)

Hi,

a few more fixes. Please pull thanks.

- print more error messages for invalid mount option values

- prevent remount with v1 space cache for subpage filesystem

- fix hang during unmount when block group reclaim task is running


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

  btrfs: zoned: introduce a minimal zone size 4M and reject mount (2022-05-17 20:15:25 +0200)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git for-5.19-rc3-tag

for you to fetch changes up to e3a4167c880cf889f66887a152799df4d609dd21:

  btrfs: add error messages to all unrecognized mount options (2022-06-07 17:29:50 +0200)

----------------------------------------------------------------
David Sterba (1):
      btrfs: add error messages to all unrecognized mount options

Filipe Manana (1):
      btrfs: fix hang during unmount when block group reclaim task is running

Qu Wenruo (1):
      btrfs: prevent remounting to v1 space cache for subpage mount

 fs/btrfs/disk-io.c | 13 +++++++++++--
 fs/btrfs/super.c   | 47 ++++++++++++++++++++++++++++++++++++++++-------
 2 files changed, 51 insertions(+), 9 deletions(-)

             reply	other threads:[~2022-06-21 12:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-21 12:41 David Sterba [this message]
2022-06-21 12:48 ` Linus Torvalds
2022-06-21 12:51   ` David Sterba
2022-06-21 18:27 ` 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.1655815078.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

all inboxes | Powered by JetHome®