From: Theodore Ts'o <tytso@mit.edu>
To: chrubis@suse.cz
Cc: Luk???? Czerner <lczerner@redhat.com>,
Xiaoguang Wang <wangxg.fnst@cn.fujitsu.com>,
linux-ext4@vger.kernel.org
Subject: Re: OpenPosix test case mmap_11-4 fails in ext4 filesystem
Date: Wed, 21 May 2014 22:45:27 -0400 [thread overview]
Message-ID: <20140522024527.GA22059@thunk.org> (raw)
In-Reply-To: <20140521212003.GA7493@rei.suse.cz>
On Wed, May 21, 2014 at 11:20:03PM +0200, chrubis@suse.cz wrote:
>
> The test in question here (mmap_11-4) is a part of the Open Posix
> Testsuite that continues to live in LTP. The whole testsuite runs in
> about 30 minutes and covers most of the POSIX interfaces in ~1600
> testcases.
I'm pretty familiar with the PCTS (which is different from the Open
Posix Testsuite), epsecially as it relates to the tty/termios
interfaces.
At least with the PCTS, there are a large number of the tests which
are primarily issues which are implemented in the core VFS layer or in
the core TTY layer. If you are a core tty implementor (as I was), the
PCTS was really useful for that. If you are a serial device driver
implementor, however, not all of the tests were as useful.
I suspect the same would be true with file system related tests.
There will be those tests which are are really useful if you are doing
core VFS work, and then there are those tests which are useful if you
are working on a particular file system. Separating out those tests
which are most useful for developers would probably be a good thing,
although obviously tere will always be a certain amount of overlap.
> I guess that we can filter filesystem related syscalls quite easily. The
> overlap would take more work though. In LTP we have mostly conformance
> testcases and some stress testcases. I'm not much familiar with xfstests
> and its coverage.
Xfstests has already taken some parts of LTP. The xfstests sources
has a ltp directory with the following:
% ls ltp
total 376
40 aio-stress.c 8 doio.h 44 fsx.c 44 iogen.c 8 rwtest.sh*
84 doio.c 68 fsstress.c 76 growfiles.c 4 Makefile
Furthermore, there are a number of xfstests which run programs like
fsstress and fsx using a variety of configuration options which have
historically been best at stress testing file systems.
So it sounds like there's quite a lot of overlap, some of it caused by
xfstests grabbing bits and pieces of LTP, and part of it because
people have been adding both functional and stress tests to xfstests.
The question is what's the best way of dealing with the overlap.
Clearly xfstests has a lot more mindshare amonst file system
developers, and LTP does have that unfortunate reputation which it is
still trying to overcome. :-/
Cheers,
- Ted
next prev parent reply other threads:[~2014-05-22 2:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 6:39 OpenPosix test case mmap_11-4 fails in ext4 filesystem Xiaoguang Wang
2014-05-21 12:55 ` Lukáš Czerner
2014-05-21 14:12 ` Theodore Ts'o
2014-05-21 15:06 ` chrubis
2014-05-21 18:58 ` Theodore Ts'o
2014-05-21 21:20 ` chrubis
2014-05-21 22:06 ` Eric Sandeen
2014-05-22 2:45 ` Theodore Ts'o [this message]
2014-05-22 10:45 ` chrubis
2014-05-22 14:38 ` Theodore Ts'o
2014-05-21 15:18 ` Lukáš Czerner
2014-05-21 19:01 ` Theodore Ts'o
2014-05-22 13:42 ` Jan Kara
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=20140522024527.GA22059@thunk.org \
--to=tytso@mit.edu \
--cc=chrubis@suse.cz \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=wangxg.fnst@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).