[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6097b2118e820af8d9ffee6b663c4e260158d62a.camel@kernel.org>
Date: Thu, 13 Jul 2023 09:19:03 -0400
From: Jeff Layton <jlayton@...nel.org>
To: Theodore Ts'o <tytso@....edu>
Cc: brauner@...nel.org, Andreas Dilger <adilger.kernel@...ger.ca>,
Jan Kara <jack@...e.cz>, linux-fsdevel@...r.kernel.org,
linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] ext4: fix decoding of raw_inode timestamps
On Thu, 2023-07-13 at 09:04 -0400, Theodore Ts'o wrote:
> On Thu, Jul 13, 2023 at 06:48:04AM -0400, Jeff Layton wrote:
> >
> > The above output is what I get with the fix in place. Without this
> > patch, I get: ...
>
> Thanks!! It's good to know the _one_ kunit test we have is capable of
> detecting this. We have a patch series lined up to add our *second*
> unit test (for the block allocator) for the next merge window, and
> while our unit test coverage is still quite small, it's nice to know
> that it can detect problems --- and much faster than running xfstests. :-}
>
Yeah, it's pretty quick! I need to consider adding some tests for some
other areas that are difficult to view outside the kernel (the errseq_t
infrastructure comes to mind).
--
Jeff Layton <jlayton@...nel.org>
Powered by blists - more mailing lists