From: Christoph Hellwig <hch@infradead.org>
To: Mikhail Lobanov <m.lobanov@rosa.ru>
Cc: Carlos Maiolino <cem@kernel.org>,
"Darrick J . Wong" <djwong@kernel.org>,
Dave Chinner <dchinner@redhat.com>,
linux-xfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Cen Zhang <rollkingzzc@gmail.com>
Subject: Re: [PATCH] xfs: skip dquot attach when m_quotainfo is not set up
Date: Tue, 2 Jun 2026 00:07:14 -0700 [thread overview]
Message-ID: <ah6BIsvEitNW5Edb@infradead.org> (raw)
In-Reply-To: <20260531155211.43803-1-m.lobanov@rosa.ru>
Hi Mikhail,
this also seems to be somewhat related to Mikhail's fixes in a similar
area. I just replied there, and my gut feeling here is that if we
are in a mount failure path, we're probably better not doing any
inode inactivation, because well, we failed to mount the file system,
so we better don't do anything to the persistent data structures.
prev parent reply other threads:[~2026-06-02 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-31 15:52 [PATCH] xfs: skip dquot attach when m_quotainfo is not set up Mikhail Lobanov
2026-06-02 7:07 ` Christoph Hellwig [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=ah6BIsvEitNW5Edb@infradead.org \
--to=hch@infradead.org \
--cc=cem@kernel.org \
--cc=dchinner@redhat.com \
--cc=djwong@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=m.lobanov@rosa.ru \
--cc=rollkingzzc@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