Skip to content
C Shell HTML Makefile Python M4 Other
Find file
Latest commit e52148b May 3, 2016 @metan-ucw metan-ucw scenario_groups/default: Remove dma_thread_diotest
Looks like there is no interest in fixing the race between fork() and
direct I/O between the kernel devs [1]. Even the open.2 manual page
states that this is a known problem and that it leads to undefined
behavior. This renders these testcases useless. They fail but that's all
we can do about it.

So let's disable the testcases from default run for now.

We may either try to change them to use madvise(MAD_DONTFORK) or shared
mapping for the buffers which are suggested workarounds, or remove them
completely.

[1] http://www.spinics.net/lists/linux-mm/msg75488.html

The issue was recently brought up in LTP GitHub issue #63.

(It's fairly easy to reproduce with a ext3 fs, for me with 2GB loopback
 all of the dma_thread_diotest have failed every time.)

Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
Failed to load latest commit information.
doc lib/tst_run_cmd: Make it possible to detect ENOENT Apr 27, 2016
include tst_atomic: add atomic_add_return for x86/64, ppc/64 and s390/x Apr 19, 2016
lib lib/tst_mkfs: Exit with TCONF on missing mkfs.foo Apr 27, 2016
m4 m4: add a check for __sync_add_and_fetch Apr 19, 2016
pan ltp-pan: Flush FILE buffers before fork() Apr 25, 2016
runtest network/stress/icmp: add icmp-uni-basic to implement all icmp basic s… Apr 28, 2016
scenario_groups scenario_groups/default: Remove dma_thread_diotest May 3, 2016
scripts Remove whitespace at end of line Oct 18, 2012
testcases syscalls/umount2_{02,03}: Retry umount2() on EBUSY May 2, 2016
testscripts fix the redirection order Nov 26, 2015
tools lib: tst_res: Cleanup. Feb 3, 2016
utils sctp: sctputils.c: fix test_peer_addr() Jul 1, 2015
.gitignore module.mk: don't run module builds multiple times Jun 30, 2015
.gitmodules gitmodules: update mce-test repo URL May 31, 2012
COPYING update GPLv2 text in COPYING Jan 26, 2015
IDcheck.sh Update FSF address Oct 19, 2012
INSTALL Update mailing list address, archive, etc. Sep 15, 2015
Makefile build: fix out-of-tree build Apr 2, 2014
Makefile.release Use `tar [..] .' instead of `tar [..] *'. Dec 13, 2010
README doc, README: Fix three links to LTP download Oct 22, 2015
README.kernel_config p9auth: remove this test Sep 17, 2014
TODO Update TODO Feb 17, 2016
VERSION LTP 20160126 Jan 26, 2016
configure.ac m4: add a check for __sync_add_and_fetch Apr 19, 2016
execltp.in PEP8 and update the copyright date May 20, 2012
ltpmenu Fix shell scripts to run correctly on Debian Apr 1, 2014
runalltests.sh perfcounters: delete runtest/perfcounters Apr 1, 2015
runltp runltp: Fix overrided -T option Apr 26, 2016
runltplite.sh runltp, runltplite.sh: Fix bashism. Mar 24, 2014
ver_linux Remove whitespace at end of line Oct 18, 2012

README

Linux Test Project
------------------

Linux Test Project is a joint project started by SGI, OSDL and Bull developed
and maintained by IBM, Cisco, Fujitsu, SUSE, Red Hat, Oracle and others. The
project goal is to deliver tests to the open source community that validate the
reliability, robustness, and stability of Linux.

The LTP testsuite contains a collection of tools for testing the Linux kernel
and related features. Our goal is to improve the Linux kernel and system
libraries by bringing test automation to the testing effort. Interested open
source contributors are encouraged to join.

Project pages are located at: http://linux-test-project.github.io/

The latest image is always available at:
https://github.com/linux-test-project/ltp/releases

The discussion about the project happens at ltp mailing list:
http://lists.linux.it/listinfo/ltp

The git repository is located at GitHub at:
https://github.com/linux-test-project/ltp

Warning!
--------
Be careful with these tests!

Don't run them on production systems. Growfiles, doio, and iogen in particular
stress the I/O capabilities of systems and while they should not cause problems
on properly functioning systems, they are intended to find (or cause) problems.

Developers corner
-----------------

Before you start you should read following documents:

* doc/test-writing-guidelines.txt
* doc/build-system-guide.txt

these two should contain all information needed for modifying or creating LTP
testcases. If something is not covered there don't hesitate to ask on the LTP
mailing list.

Also note that these documents are available online at:

https://github.com/linux-test-project/ltp/wiki/Test-Writing-Guidelines
https://github.com/linux-test-project/ltp/wiki/BuildSystem
Something went wrong with that request. Please try again.