public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Wanlong Gao <gaowanlong@cn.fujitsu.com>
To: Om Prakash PAL <omprakash.pal@stericsson.com>
Cc: "ltp-list@lists.sourceforge.net" <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] Failure of syscalls in kernel version 3.4
Date: Tue, 31 Jul 2012 11:45:05 +0800	[thread overview]
Message-ID: <501754C1.904@cn.fujitsu.com> (raw)
In-Reply-To: <3ED83A9DB3B6D94CA68BF7C03F2981D35B18E7912E@EXDCVYMBSTM006.EQ1STM.local>

On 07/02/2012 02:49 PM, Om Prakash PAL wrote:
> Hi,
> 
> I am currently using ltp-full-20110915.bz2.
> 
> When I switched to  kernel 3.4(from kernel 3.0)  then these syscalls ltp are failing.
> 
> [1].*get_robust_list01*
> 
> *get_robust_list01    1  TPASS  :  get_robust_list failed as expected with EFAULT *
> 
> *get_robust_list01    2  TPASS  :  get_robust_list failed as expected with EFAULT *
> 
> *get_robust_list01    3  TPASS  :  get_robust_list failed as expected with ESRCH *
> 
> *get_robust_list01    4  TFAIL  :  get_robust_list succeeded unexpectedly *

This is already fixed, please refer to this commit
https://github.com/linux-test-project/ltp/commit/d28ecfa1f14b62ad779db38164ce54d3adfc7425

> 
> *get_robust_list01    5  TPASS  :  get_robust_list succeeded *
> 
> * *
> 
> *[2].**gettimeofday02*
> 
> *gettimeofday02    0  TINFO  :  checking if gettimeofday is monotonous, takes 30s *
> 
> *gettimeofday02    1  TFAIL  :  Time is going backwards: old 946*
> 
> * *
> 
> *[3].**lseek03*
> 
> *lseek03     1  TFAIL  :  lseek(tfile_16887, 1, 4) Failed, errno=6 No such device or address, expected 22(EINVAL) *
> 
> *lseek03     2  TPASS  :  lseek(tfile_16887, 1, -1) Failed, errno=22 : Invalid argument *
> 
> *lseek03     3  TPASS  :  lseek(tfile_16887, 1, 7) Failed, errno=22 : Invalid argument *
> 

This is fixed by commit https://github.com/linux-test-project/ltp/commit/423e636a4c8f2b04cd0407e91d7b7091f37e47b4


> * *
> 
> *[4].**readlink03*
> 
> *readlink03    1  TPASS  :  readlink(), No Search permissions to process, returned errno 13 *
> 
> *readlink03    2  TPASS  :  readlink(), No Search permissions to process, returned errno 13 *
> 
> *readlink03    3  TPASS  :  readlink(), Buffer size is not positive, returned errno 22 *
> 
> *readlink03    4  TPASS  :  readlink(), Buffer size is not positive, returned errno 22 *
> 
> *readlink03    5  TPASS  :  readlink(), File is not symbolic link, returned errno 22 *
> 
> *readlink03    6  TPASS  :  readlink(), File is not symbolic link, returned errno 22 *
> 
> *readlink03    7  TPASS  :  readlink(), Symlink path too long, returned errno 36 *
> 
> *readlink03    8  TPASS  :  readlink(), Symlink path too long, returned errno 36 *
> 
> *readlink03    9  TFAIL  :  readlink() failed, Symlink Pathname is empty, errno=2, expected errno=22 *

This is fixed by commit https://github.com/linux-test-project/ltp/commit/dc9df862a95db96b7046623659ceaf911a583ce7


and so on, if you meet further FAIL like these, please use upstream version of LTP,
you can get from git://github.com/linux-test-project/ltp.git .
And, if the upstream version also has problems, please feel free to send a patch here.

Thanks,
Wanlong Gao

> 
> * *
> 
> *[5]**shmat01*
> 
> *shmat01     1  TFAIL  :  shmat call failed: TEST_ERRNO=EINVAL(22): Invalid argument *
> 
> * *
> 
> *[6]**sysctl01*
> 
> *sysctl01    1  TFAIL  :  sysctl(2) failed unexpectedly errno:38 *
> 
> *sysctl01    2  TFAIL  :  sysctl(2) failed unexpectedly errno:38 *
> 
> *sysctl01    3  TFAIL  :  sysctl(2) failed unexpectedly errno:38 *
> 
> * *
> 
> *any idea why these testcases are failing now?.*
> 
> *How can I resolve it?.*
> 
> * *
> 
> *Best Regards,*
> 
> *Om Prakash Pal*
> 
>  
> 
> 
> 
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and 
> threat landscape has changed and how IT managers can respond. Discussions 
> will include endpoint security, mobile security and the latest in malware 
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> 
> 
> 
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list
> 


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

      parent reply	other threads:[~2012-07-31  3:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-02  6:49 [LTP] Failure of syscalls in kernel version 3.4 Om Prakash PAL
2012-07-27  8:59 ` Jan Stancek
2012-07-27  9:12   ` Om Prakash PAL
2012-07-27 10:34     ` Jan Stancek
2012-07-31  3:45 ` Wanlong Gao [this message]

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=501754C1.904@cn.fujitsu.com \
    --to=gaowanlong@cn.fujitsu.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=omprakash.pal@stericsson.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