Amir Goldstein <amir73il@xxxxxxxxx> wrote:
> xfstests is all 99% bash scripts and most of the uses of stat(2) are
> by executing
> stat(1), so all you have to do in order to exercise a statx() with existing
> tests is install a stat executable in your path that uses statx()
> instead of stat().
Actually, it would be easier to write the test in C as:
(1) How do you feed statx bad arguments from shell scripts (e.g. a kernel
address for the buffer pointer or the name pointer) to make sure it gives
appropriate errors?
(2) I want to do a comparison of the struct statx to a struct stat almost
every time statx is called.
(3) There's going to be a bunch of timestamp comparisons.
I grant that (2) and (3) can be done in shell scripts - I've not tried bash's
associative arrays, but they ought to make it easier. (1), however, is
something that requires C support and is something that I have in the LTP
tests as I copied that stuff from the stat/fstat/lstat tests there.
> It sounds like you are new to xfstests?
I've not tried to modify it before.
> xfstests is not extensively documented, but it quite simple, so it
> usually "just works".
I noticed the paucity of documentation. doc/ contains nothing more than an
old CHANGES file. "Quite simple" does not translate to "easy to use",
especially when you have to make changes outside the package to get it to work
- and nowhere in the docs that there are is this mentioned.
David
