[ANNOUNCE] Linux Test Project October Release Available

[ANNOUNCE] Linux Test Project October Release Available

[Robert Williamson]

The Linux Test Project test suite LTP-20021008.tgz has been released. Visit
our website (http://ltp.sourceforge.net) to download the latest version of
the testsuite, and for information on test results on pre-releases, release
candidates & stable releases of the kernel. There is also a list of test
cases that are expected to fail, please find the list at (
http://ltp.sourceforge.net/expected-errors.php)

The highlights of this release are:

- Updated the STAX LTP driver. You can now specify client and server
logging paths.  The ability to define how long a single test is allowed run
has been added. Plus, hardware information is now included in the logs for
each client. The HowTo has been updated as well.

- Updated the Database Opensource Test Suite (DOTS) with added
functionality to allow the use of MySQL and PostreSQL databases,
complementing the existing features that allow the use of DB2, Oracle, and
Sybase databases.  Additionally, DOTS is now available as an on-demand test
suite at the Open Source Development Lab's Linux Kernel Scalable Test
Platform. (http://www.osdl.org/stp)

- An additional shared memory control test has been added (shmctl04), that
tests the SHM_INFO command.

We encourage the community to post results, patches, or new tests on our
mailing list, and to use the CVS bug tracking facility to report problems
that you might encounter. More details available at our web-site.


Change Log
------------
- Added "shmctl04" to test the SHM_INFO command  ( Mingming Cao )
- Fix for improper child exit in "execve02"      ( Colin Gibbs )
- Fix for "nanosleep02" to eliminate false       ( Andreas Arcangeli )
  positives
- Fix for "personality01 to undef the personality( Marcus Meissner )
  macro before calling personality()
- Fix for "sendfile02" that adds a waitpid() call( Susanne Wintenberger )
  to guarantee child exit before the test ends
- Fix for /tools/rand_lines.c that eliminates an ( Nathan Straz )
  IA64 compile time warning
- Added "shmctl04" to the "syscalls" runtest file( Paul Larson )
- Removed test 8 from "diotest4". Opening a      ( Paul Larson )
  directory for direct I/O is not allowed.
- Fix for PPC cross compile issues applied to:   ( Paul Larson )
    "mmap01"
    "pth_str01"
    "pth_str03"
    "shmem_test_04"
- Fix for "fcntl01" to allow it to run without   ( Paul Larson )
  predefining the file descriptors
- Fix for "readv02" to check for EINVAL on       ( Paul Larson )
  2.5.35 and above kernels
- Fix for "stime01" to allow the checked time to ( Paul Larson )
  be off +1 second
- Fix for "writev01" to check for EINVAL on      ( Paul Larson )
  2.5.35 and above kernels

Robbie  Williamson <robbiew@us.ibm.com>
Linux Test Project
http://ltp.sourceforge.net

Re: [ANNOUNCE] Linux Test Project October Release Available

[Andrew Morton]

Robert Williamson wrote:
> 
> ...
> - Fix for "writev01" to check for EINVAL on      ( Paul Larson )
>   2.5.35 and above kernels
> 

whoa.  I've been asleep.  The 2.4 kernel _does_ return zero
if passed a zero segment count.

So we need to fix 2.5 to do that as well.  Sure, the spec
appears to allow either, but given that, we should preserve
the 2.4 behaviour.

Does that sound sane?    If so then we should unfix this fix
in LTP.  Sorry.

Re: [ANNOUNCE] Linux Test Project October Release Available

[Ingo Oeser]

On Tue, Oct 08, 2002 at 01:11:29PM -0700, Andrew Morton wrote:
> Robert Williamson wrote:
> > 
> > ...
> > - Fix for "writev01" to check for EINVAL on      ( Paul Larson )
> >   2.5.35 and above kernels
> > 
> 
> whoa.  I've been asleep.  The 2.4 kernel _does_ return zero
> if passed a zero segment count.
> 
> So we need to fix 2.5 to do that as well.  Sure, the spec
> appears to allow either, but given that, we should preserve
> the 2.4 behaviour.

I agree. Passing zero counts means "no work to do" and passing
that information is never a problem in any function.

The same goes for a segment with zero len (which is a way to
measure user space to kernel driver latency, if the driver
implements writev and readv).

It's only a "performance bug", if that is used in a real
application, no wrong parameters.

Regards

Ingo Oeser
-- 
Science is what we can tell a computer. Art is everything else. --- D.E.Knuth