linux-kernel - Re: [PATCH v4] exfat: check disk status during buffer write

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAPqOJe0shhTkZN=ybpQP_h79BYACKdAzipxS4Q=1PAB6H1hZBA@mail.gmail.com>
Date: Tue, 13 Aug 2024 09:42:05 +0800
From: dongliang cui <cuidongliang390@...il.com>
To: Christoph Hellwig <hch@...radead.org>
Cc: Dongliang Cui <dongliang.cui@...soc.com>, linkinjeon@...nel.org, sj1557.seo@...sung.com, 
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org, 
	niuzhiguo84@...il.com, hao_hao.wang@...soc.com, ke.wang@...soc.com, 
	Zhiguo Niu <zhiguo.niu@...soc.com>
Subject: Re: [PATCH v4] exfat: check disk status during buffer write

On Mon, Aug 12, 2024 at 8:06 PM Christoph Hellwig <hch@...radead.org> wrote:
>
> > 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.
>
Thank you for your help. I will pay attention to the timestamp issue later.