From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: rohit verma <rohit.170309@gmail.com>
Cc: ltp-list <ltp-list@lists.sf.net>
Subject: Re: [LTP] utimes01 test case issue
Date: Sat, 15 Aug 2009 10:34:10 +0800 [thread overview]
Message-ID: <4A861EA2.6070701@cn.fujitsu.com> (raw)
In-Reply-To: <d51f89b0908140134g18b7b34cr9858edad1242373a@mail.gmail.com>
rohit verma wrote:
> Hi Wang Yong,
>
> I am getting following O/P for case02 :
>
> As root user:
>
> utimes01 0 TINFO : (case02) START
> EXPECT: return value(ret)=-1 errno=13 (Permission denied)
> RESULT: return value(ret)=-1 errno=1 (Operation not permitted)
> utimes01 0 TINFO : (case02) END => NG
>
> As non-root user:
> utimes01 0 TINFO : (case02) START
> seteuid failed.
> utimes01 0 TINFO : (case02) END => OK
>
> Are you getting the same?
>
>
>
yes, the same result.
>
> On Fri, Aug 14, 2009 at 12:03 PM, Wei Yongjun<yjwei@cn.fujitsu.com> wrote:
>
>> rohit verma wrote:
>>
>>> Hi Wang Yong,
>>>
>>> I have observed the following thing in case02 of the test case
>>> utimes01 in latest ltp release.
>>>
>>> Expected error value is EACCES (In the code below)
>>> But the actual error value is EPERM.I have checked this on 2.6.27 and
>>> 2.6.29 kernel.
>>>
>>>
>> You can try root user and noroot user, the return error is different.
>>
>>
>>> static struct test_case tcase[] = {
>>>
>>> { // case00
>>> ...
>>> },
>>> { // case01
>>> ...
>>> },
>>> { // case02
>>> .ttype = NORMAL,
>>> .a_sec = 1000,
>>> .m_sec = 2000,
>>> .user = "nobody",
>>> .ret = -1,
>>> .err = EACCES, // RHEL4U1 + 2.6.18 returns EPERM
>>> },
>>> { // case03
>>> ...
>>> },
>>>
>>> { // case04
>>> ...
>>> },
>>> };
>>>
>>> Kindly confirm whether you are facing the same issue at your end.
>>>
>>>
>>>
>>
>>
>
>
>
>
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-08-15 3:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-13 8:31 [LTP] utimes01 test case issue rohit verma
2009-08-14 6:33 ` Wei Yongjun
2009-08-14 8:34 ` rohit verma
2009-08-15 2:34 ` Wei Yongjun [this message]
2009-08-21 5:14 ` rohit verma
2009-08-27 8:39 ` rohit verma
2009-08-27 10:20 ` Subrata Modak
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=4A861EA2.6070701@cn.fujitsu.com \
--to=yjwei@cn.fujitsu.com \
--cc=ltp-list@lists.sf.net \
--cc=rohit.170309@gmail.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