public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Subrata Modak <subrata@linux.vnet.ibm.com>
To: Wang Yong <wangyong2009@cn.fujitsu.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] [PATCH] Fix failure of the utimes01 test
Date: Fri, 10 Jul 2009 16:16:27 +0530	[thread overview]
Message-ID: <1247222787.6630.26.camel@subratamodak.linux.ibm.com> (raw)
In-Reply-To: <4A559DB3.6030000@cn.fujitsu.com>

On Thu, 2009-07-09 at 15:35 +0800, Wang Yong wrote: 
> Whenever system called utimes, the error message returned was EINVAL,
> because the member variable of struct timeval was not initialized,
> so initialize it.
> 
> Signed-off-by: WangYong <wangyong2009@cn.fujitsu.com>
> 
> diff -Nurp ltp-full-20090630/testcases/kernel/syscalls/utimes/utimes01.c
> ltp-full-20090630.new/testcases/kernel/syscalls/utimes/utimes01.c
> --- ltp.orig/testcases/kernel/syscalls/utimes/utimes01.c 2009-07-01
> 17:20:12.000000000 +0800
> +++ ltp/testcases/kernel/syscalls/utimes/utimes01.c  2009-07-08
> 17:20:38.000000000 +0800
> @@ -248,6 +248,7 @@ static int do_test(struct test_case *tc)
>           /*
>            * Execute system call
>            */
> +        memset(tv, 0, 2 * sizeof(struct timeval));

Initializing this is good. But i do not find any visible difference in
running this test pre and post patching either on 2.6.29 or 2.6.18
kernels. The following output is generated each time:

# ./testcases/bin/utimes01 
utimes01    0  INFO  :  (case00) START
open failed.
utimes01    0  INFO  :  (case00) END => NG
utimes01    0  INFO  :  (case01) START
open failed.
utimes01    0  INFO  :  (case01) END => NG
utimes01    0  INFO  :  (case02) START
open failed.
utimes01    0  INFO  :  (case02) END => NG
utimes01    0  INFO  :  (case03) START
open failed.
utimes01    0  INFO  :  (case03) END => NG
utimes01    0  INFO  :  (case04) START
open failed.
utimes01    0  INFO  :  (case04) END => NG
utimes01    1  FAIL  :  utimes01 failed - errno = 2 : No such file or
directory
utimes01    0  INFO  :  NG

# echo $?
1

Regards--
Subrata

> tv[0].tv_sec = tc->a_sec;
>           tv[1].tv_sec = tc->m_sec;
>           TEST(len = strlen(fpath));
> 
> 
> 
> ------------------------------------------------------------------------------
> Enter the BlackBerry Developer Challenge  
> This is your chance to win up to $100,000 in prizes! For a limited time, 
> vendors submitting new applications to BlackBerry App World(TM) will have
> the opportunity to enter the BlackBerry Developer Challenge. See full prize  
> details at: http://p.sf.net/sfu/Challenge
> _______________________________________________
> Ltp-list mailing list
> Ltp-list@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/ltp-list


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2009-07-10 10:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-09  7:35 [LTP] [PATCH] Fix failure of the utimes01 test Wang Yong
2009-07-10 10:46 ` Subrata Modak [this message]
2009-07-16  1:03   ` Wang Yong
2009-07-19  4:53     ` Garrett Cooper
2009-07-19  4:54       ` Garrett Cooper
  -- strict thread matches above, loose matches on Subject: below --
2009-07-20  7:41 naresh kamboju
2009-07-21  2:25 Wang Yong
2009-07-21  2:55 Wang Yong
2009-07-21  4:24 ` Garrett Cooper
2009-07-21  6:16   ` Wang Yong

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=1247222787.6630.26.camel@subratamodak.linux.ibm.com \
    --to=subrata@linux.vnet.ibm.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=wangyong2009@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