From: Bian Naimeng <biannm@cn.fujitsu.com>
To: Garrett Cooper <yanegomi@gmail.com>
Cc: ltp-list@lists.sourceforge.net, "當座 健市" <toza@ryobi.co.jp>,
Mitani <mitani@ryobi.co.jp>
Subject: Re: [LTP] [PATCH] fix "sched_getparam/6-1" and "sched_getscheduler/7-1" tests
Date: Tue, 25 Jan 2011 11:11:40 +0800 [thread overview]
Message-ID: <4D3E3F6C.9060808@cn.fujitsu.com> (raw)
In-Reply-To: <AANLkTinUjNU4z9GBqv=Mvf2vZF-0VTNzFDa89K_X3P7B@mail.gmail.com>
Garrett Cooper wrote:
> On Mon, Jan 24, 2011 at 1:58 AM, Bian Naimeng <biannm@cn.fujitsu.com> wrote:
>>
>> Mitani wrote:
>>> Hi,
>>>
>>>
>>> Following POSIX testsets failed:
>>> ------------
>>> conformance/interfaces/sched_getparam/6-1: execution: FAILED: Output:
>>> Testing with user 'bin' (euid: 1)(uid: 1)
>>> The function sched_getparam has successed.
>>> ------------
>>>
>>> ------------
>>> conformance/interfaces/sched_getscheduler/7-1: execution: FAILED: Output:
>>> Testing with user 'bin' (uid: 1)
>>> The function sched_getscheduler has successed.
>>> ------------
>>>
>>> The environments are as follows:
>>> - RHEL4.8 --- (x86, x86_64, ia64)
>>> - kernel --- kernel-2.6.9-89.EL
>>> - glibc --- glibc-2.3.4-2.43
>>>
>>> - RHEL5.5 --- (x86, x86_64, ia64)
>>> - kernel --- kernel-2.6.18-194.el5
>>> - glibc --- glibc-2.5-49
>>>
>>>
>>> They are permission tests.
>>>
>>> The comment of "sched_getparam/6-1" testset source is as follows:
>>> ------------
>>> * On Linux, e.g, the kernel makes no check on user permission to call this
>>> * API. So basically we don't know on what condition a system should return
>>> * EPERM. It is implementation defined.
>>> ------------
>>>
>> Hi Garrett,
>>
>> I think it's better to report UNRESOLVED, whatever the os is.
>
> It's not implementation defined according to 2008.1, and it's flat
> out a requirement failure (not UNRESOLVED):
>
> The sched_getparam() function shall fail if:
>
> [EPERM]
> The requesting process does not have permission to obtain the
> scheduling parameters of the specified process.
>
> `shall' -> `must' in POSIX terms.
Thanks very much for telling me this information.
But the spec does not point out the what condition a process does not
have permission to do it.
>
> The test is incorrect because it fails to setgid the group to the
> non-root user's group.
Ditto.
The POSIX spec does not point out non-root user(non-root group too) does not
have permission to obtain the scheduling parameters of the init process.
Maybe i miss something. If so, please tell me, thanks very much.
Thanks
Bian
> Thanks,
> -Garrett
>
>
--
Regards
Bian Naimeng
------------------------------------------------------------------------------
Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
Finally, a world-class log management solution at an even better price-free!
Download using promo code Free_Logger_4_Dev2Dev. Offer expires
February 28th, so secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsight-sfd2d
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2011-01-25 3:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 6:56 [LTP] [PATCH] fix "sched_getparam/6-1" and "sched_getscheduler/7-1" tests Mitani
2011-01-24 9:58 ` Bian Naimeng
2011-01-24 10:56 ` Garrett Cooper
2011-01-25 3:11 ` Bian Naimeng [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=4D3E3F6C.9060808@cn.fujitsu.com \
--to=biannm@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=mitani@ryobi.co.jp \
--cc=toza@ryobi.co.jp \
--cc=yanegomi@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