From: Anand Jain <anajain.sg@gmail.com>
To: Boris Burkov <boris@bur.io>
Cc: linux-btrfs@vger.kernel.org, kernel-team@fb.com, fstests@vger.kernel.org
Subject: Re: [PATCH 2/2] btrfs: test qgroup deletion races with squota writes
Date: Tue, 19 May 2026 14:15:09 +0800 [thread overview]
Message-ID: <24280a77-8119-4b00-87e4-223ffded1b92@gmail.com> (raw)
In-Reply-To: <20260518162841.GA3181893@zen.localdomain>
Boris,
The 7.1.0-rc3-gf5d9f327e4b2 kernel includes the for-next tree
plus my latest f_fsid kernel patches.
I double-checked and the required btrfs squota patches were
indeed present:
$ git log --oneline fs/btrfs | grep "check for subvolume before"
404bf5a24f2e btrfs: check for subvolume before deleting squota qgroup
$ git log --oneline fs/btrfs | grep "forbid creating subvol qgroups"
0c309d66dacd btrfs: forbid creating subvol qgroups
Possibly the issue was likely my messed-up VM image from
SELinux + fanotifywait troubleshooting last evening.
After a fresh restart, btrfs/348 passes:
$ ./check -s gen btrfs/348
...
Ran: btrfs/348
Passed all 1 tests
Sorry for the noise!.
Looks good.
Reviewed-by: Anand Jain <asj@kernel.org>
A small nit (which can be fixed during merge).
>>> diff --git a/tests/btrfs/348 b/tests/btrfs/348
>>> new file mode 100755
>>> index 00000000..ab816301
>>> --- /dev/null
>>> +++ b/tests/btrfs/348
>>> @@ -0,0 +1,136 @@
>>> +#! /bin/bash
>>> +# SPDX-License-Identifier: GPL-2.0
>>> +# Copyright (c) 2024 Meta Platforms, Inc. All Rights Reserved.
Do you need this to be `s/2024/2026/` ?
Thanks.
prev parent reply other threads:[~2026-05-19 6:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-13 0:43 [PATCH 0/2] squota delete fstests Boris Burkov
2026-05-13 0:43 ` [PATCH 1/2] btrfs: inline enable_quota helper in test 301 Boris Burkov
2026-05-14 3:34 ` Zorro Lang
2026-05-15 21:15 ` Boris Burkov
2026-05-16 13:55 ` Zorro Lang
2026-05-19 6:18 ` Anand Jain
2026-05-13 0:43 ` [PATCH 2/2] btrfs: test qgroup deletion races with squota writes Boris Burkov
2026-05-18 9:18 ` Anand Jain
2026-05-18 16:28 ` Boris Burkov
2026-05-19 6:15 ` Anand Jain [this message]
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=24280a77-8119-4b00-87e4-223ffded1b92@gmail.com \
--to=anajain.sg@gmail.com \
--cc=boris@bur.io \
--cc=fstests@vger.kernel.org \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@vger.kernel.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