From: Christoph Hellwig <hch@infradead.org>
To: Dongliang Cui <dongliang.cui@unisoc.com>
Cc: linkinjeon@kernel.org, sj1557.seo@samsung.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
niuzhiguo84@gmail.com, hao_hao.wang@unisoc.com,
ke.wang@unisoc.com, cuidongliang390@gmail.com,
Zhiguo Niu <zhiguo.niu@unisoc.com>
Subject: Re: [PATCH v4] exfat: check disk status during buffer write
Date: Mon, 12 Aug 2024 05:06:51 -0700 [thread overview]
Message-ID: <Zrn622M2F1x-fH3n@infradead.org> (raw)
In-Reply-To: <20240808063648.255732-1-dongliang.cui@unisoc.com>
> Apart from generic/622, all other shutdown-related cases can pass.
>
> generic/622 fails the test after the shutdown ioctl implementation, but
> when it's not implemented, this case will be skipped.
>
> This case designed to test the lazytime mount option, based on the test
> results, it appears that the atime and ctime of files cannot be
> synchronized to the disk through interfaces such as sync or fsync.
> It seems that it has little to do with the implementation of shutdown
> itself.
>
> If you need detailed information about generic/622, I can upload it.
generic/622 tests that file systems implement at least lazytime
semantics. If exfat fails that it probably has timestamp handling
issue which are unrelated to the shutdown support, but which are only
exposed by this test that requires shutdown support. It would be great
if someone could look into that, but that's not a precondition for
your patch.
next prev parent reply other threads:[~2024-08-12 12:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-08 6:36 Dongliang Cui
2024-08-09 12:57 ` Namjae Jeon
2024-08-12 1:40 ` dongliang cui
2024-08-12 12:06 ` Christoph Hellwig [this message]
2024-08-13 1:42 ` dongliang cui
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=Zrn622M2F1x-fH3n@infradead.org \
--to=hch@infradead.org \
--cc=cuidongliang390@gmail.com \
--cc=dongliang.cui@unisoc.com \
--cc=hao_hao.wang@unisoc.com \
--cc=ke.wang@unisoc.com \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niuzhiguo84@gmail.com \
--cc=sj1557.seo@samsung.com \
--cc=zhiguo.niu@unisoc.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
all inboxes | Powered by JetHome®