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 6.8-rc4
Date: Wed, 7 Feb 2024 09:15:35 +0100 [thread overview]
Message-ID: <cover.1707292515.git.dsterba@suse.com> (raw)
Hi,
please pull a few error handling fixes. Thanks.
- two fixes preventing deletion and manual creation of subvolume qgroup
- unify error code returned for unknown send flags
- fix assertion during subvolume creation when anonymous device could
be allocated by other thread (e.g. due to backref walk)
----------------------------------------------------------------
The following changes since commit 7f2d219e78e95a137a9c76fddac7ff8228260439:
btrfs: scrub: limit RST scrub to chunk boundary (2024-01-18 23:43:08 +0100)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux.git tags/for-6.8-rc3-tag
for you to fetch changes up to e03ee2fe873eb68c1f9ba5112fee70303ebf9dfb:
btrfs: do not ASSERT() if the newly created subvolume already got read (2024-01-31 08:42:53 +0100)
----------------------------------------------------------------
Boris Burkov (2):
btrfs: forbid creating subvol qgroups
btrfs: forbid deleting live subvol qgroup
David Sterba (1):
btrfs: send: return EOPNOTSUPP on unknown flags
Qu Wenruo (1):
btrfs: do not ASSERT() if the newly created subvolume already got read
fs/btrfs/disk-io.c | 13 +++++++++++--
fs/btrfs/ioctl.c | 5 +++++
fs/btrfs/qgroup.c | 14 ++++++++++++++
fs/btrfs/send.c | 2 +-
4 files changed, 31 insertions(+), 3 deletions(-)
next reply other threads:[~2024-02-07 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 8:15 David Sterba [this message]
2024-02-07 8:26 ` [GIT PULL] Btrfs fixes for 6.8-rc4 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.1707292515.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