Re: [LTP] changing syscall return values

[Manoj I. <ma...@au...>]

First check the expected failure list on the ltp web site wrt to your
kernel version. Yes, these tests may be expected to fail on 2.4.18. bugs
might be open for these failures.So, the first stop should be the
expected failure list for your kernel version.

--
Manjo
> I'm running LTP on a 2.4.18 kernel.  It seems that some system-call 
> return codes have changed from kernel version 2.4.x to 2.6.x.  I've 
> observed three cases:
> 
> 1.  Test shmdt02 expects EINVAL, but Linux 2.4.18 will alway return 
> success (zero).  Comparison with Linux 2.6.0 sources shows EINVAL was 
> recently added as a possible return code.
> 
> 2.  Test msync05 expects ENOMEM, but Linux 2.4.18 returns EFAULT. 
> Comparison with Linux 2.6.0 sources indicates ENOMEM was recently 
> added as a possible return code.
> 
> 3.  Test mprotect01 expects ENOMEM, but Linux 2.4.18 returns EFAULT. 
> Comparison with 2.6.0 sources indicates ENOMEM was recently added as a 
> possible return code.
> 
> Has anyone else seen this?
> 
> I would like to submit patches that check a kernel's version and 
> adjusts these tests' expected return codes appropriately.  Would these 
> patches be welcome?
> 
> Thanks.