From: Christoph Hellwig <hch@infradead.org>
To: Carlos Maiolino <cem@kernel.org>
Cc: Yao Sang <sangyao@kylinos.cn>,
djwong@kernel.org, linux-xfs@vger.kernel.org,
fstests@vger.kernel.org
Subject: Re: [PATCH v2] xfs: shut down zoned file systems on writeback errors
Date: Mon, 15 Jun 2026 06:32:58 -0700 [thread overview]
Message-ID: <ai__CtK_5RI3hya2@infradead.org> (raw)
In-Reply-To: <178125341409.29986.5501338776712506668.b4-ty@b4>
FYI, this causes errors in generic/441 and xfs/665. In generic/441
the file system get shut down now before the error could be propagated
to fsync, and similarly for xfs/656 the file system gets shutdown
before reporting fserror events. In both cases the behavior makes
sense when a file system is not intended to survive data write errors.
I guess we need to introduce some way to check if a given file system
config will shut down on errors?
prev parent reply other threads:[~2026-06-15 13:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-12 2:44 [PATCH v2] xfs: shut down zoned file systems on writeback errors Yao Sang
2026-06-12 5:29 ` Christoph Hellwig
2026-06-12 8:36 ` Carlos Maiolino
2026-06-15 13:32 ` 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=ai__CtK_5RI3hya2@infradead.org \
--to=hch@infradead.org \
--cc=cem@kernel.org \
--cc=djwong@kernel.org \
--cc=fstests@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sangyao@kylinos.cn \
/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