From: Boris Burkov <boris@bur.io>
To: linux-btrfs@vger.kernel.org, kernel-team@fb.com
Cc: marc@merlins.org
Subject: [PATCH 0/4] btrfs: squota lifetime fixes
Date: Tue, 12 May 2026 12:34:52 -0700 [thread overview]
Message-ID: <cover.1778613519.git.boris@bur.io> (raw)
A recent report of read-only filesystems since enabling squotas:
https://lore.kernel.org/linux-btrfs/adnBhWfJQ1n3hZC8@merlins.org/
led me to investigate a handful of issues in squotas and find some trivial and
not so trivial bugs in their lifetime management. The aim of the series is to
strengthen enforcement of the invariant: "a squota qgroup must outlast extents
that are accounted to it".
This series consists of two fixes to squota lifetime bugs and two patches that
reduce the consequences of errors in lifetime management from full fs goes
read-only abort to "warning and inaccurate squotas which can be deleted
eventually"
Additional improvements to btrfs check and fstests to follow.
Boris Burkov (4):
btrfs: check for subvolume before deleting squota qgroup
btrfs: fix squota accounting during enable generation
btrfs: clamp to avoid squota underflow
btrfs: swallow btrfs_record_squota_delta() enoent
fs/btrfs/fs.h | 1 +
fs/btrfs/qgroup.c | 99 ++++++++++++++++++++++++++++++++---------------
2 files changed, 68 insertions(+), 32 deletions(-)
--
2.54.0
next reply other threads:[~2026-05-12 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-12 19:34 Boris Burkov [this message]
2026-05-12 19:34 ` [PATCH 1/4] btrfs: check for subvolume before deleting squota qgroup Boris Burkov
2026-05-12 19:34 ` [PATCH 2/4] btrfs: fix squota accounting during enable generation Boris Burkov
2026-05-12 19:34 ` [PATCH 3/4] btrfs: clamp to avoid squota underflow Boris Burkov
2026-05-13 0:53 ` Qu Wenruo
2026-05-12 19:34 ` [PATCH 4/4] btrfs: swallow btrfs_record_squota_delta() enoent Boris Burkov
2026-05-13 0:54 ` Qu Wenruo
2026-05-13 1:01 ` [PATCH 0/4] btrfs: squota lifetime fixes Qu Wenruo
2026-05-13 2:13 ` David Sterba
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.1778613519.git.boris@bur.io \
--to=boris@bur.io \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=marc@merlins.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