From: Zhang Cen <rollkingzzc@gmail.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Carlos Maiolino <cem@kernel.org>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Zhang Cen <rollkingzzc@gmail.com>,
zerocling0077@gmail.com, 2045gemini@gmail.com
Subject: Re: [PATCH] xfs: drain inodegc before quota teardown on mount failure
Date: Thu, 28 May 2026 13:31:28 +0800 [thread overview]
Message-ID: <20260528053128.3036120-1-rollkingzzc@gmail.com> (raw)
In-Reply-To: <agwh6darf9q52za7@infradead.org>
Hi Christoph,
Sorry, I missed this reply earlier and only noticed it now from the
public archive.
> How did you run into this? Normal xfstests under a new sanitizer?
This was not from normal xfstests. I reproduced it in a KASAN-enabled
QEMU guest with a disposable quota-enabled XFS image, then forced a late
mount failure after quota setup while tracing the inodegc and quota
teardown path. The failing ordering was:
xfs_qm_mount_quotas()
late mount failure
xfs_qm_unmount_quotas()
xfs_qm_unmount() / xfs_qm_destroy_quotainfo()
xfs_inodegc_flush()
with inodegc still able to reach the dqattach/dqget side during the
teardown window.
> This looks good.
Thanks.
> This is later in the teardown order than where I'd expect it. The
> first thing that can bring in quotainodes is xfs_qm_newmount. I'd
> expect a new label placed above out_rtunmount to handle this. Is
> there a reason I'm missing why this won't work?
No, I don't think you are missing anything. A separate label above
out_rtunmount is the cleaner place for this. I'll send a v2 that keeps
the out_agresv inodegc drain before xfs_qm_unmount_quotas(), adds an
out_qm_unmount label above out_rtunmount, and routes the later
post-quota failure paths through that label.
I'll also fix the trailer spacing in v2.
Thanks,
Zhang
next prev parent reply other threads:[~2026-05-28 5:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 16:07 Zhang Cen
2026-05-19 8:40 ` Christoph Hellwig
2026-05-28 5:31 ` Zhang Cen [this message]
2026-05-28 8:32 ` Christoph Hellwig
2026-05-28 13:28 ` Cen Zhang
2026-06-02 7:01 ` Christoph Hellwig
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=20260528053128.3036120-1-rollkingzzc@gmail.com \
--to=rollkingzzc@gmail.com \
--cc=2045gemini@gmail.com \
--cc=cem@kernel.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=zerocling0077@gmail.com \
/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
Powered by JetHome