From: Wei Yongjun <yjwei@cn.fujitsu.com>
To: Sharyathi Nagesh <sharyath@in.ibm.com>
Cc: ltp-list@lists.sourceforge.net, mbeeraka@in.ibm.com
Subject: Re: [LTP] Issue observed with chmod05, fchmod05 test cases
Date: Mon, 29 Jun 2009 15:33:58 +0800 [thread overview]
Message-ID: <4A486E66.5050102@cn.fujitsu.com> (raw)
In-Reply-To: <4A48667F.9050101@in.ibm.com>
Sharyathi Nagesh wrote:
> Hi
> I am observing this anomaly with these 2 test cases chmod05.c and
> fchmod05.c.
> These 2 test cases are written to test the POSIX standard which says:
>
> "If the calling process is not privileged (Linux: does not
> have the
> CAP_FSETID capability), and the group of the file does not
> match the
> effective group ID of the process or one of its
> supplementary group
> IDs, the S_ISGID bit will be turned off, but this will not
> cause an
> error to be returned."
>
>
> So the test case will try to setup a file in which the GID of the
> test/tmp file will be different from the effective group ID of the
> running process. But this criterion is found to be not sufficient
> condition for the clearing the S_ISGID bit of the file
>
> ------------------------------------------------------------
> Ex:
> There are 2 users nobody (uid=99, gid=99) and bin (uid=1, gid=1)
> let as assume temporary file as /tmp/zxcv
>
> Test will Pass if
> Set UID/GID of /tmp/zxcv to nobody->uid & nobody->GID
> Set eUID/eGID of process to nobody->uid & bin->GID
>
> Test will Fail if
> Set UID/GID of /tmp/zxcv to nobody->uid & bin->GID
> Set eUID/eGID of process to nobody->uid & nobody->GID
>
> I verified supplementary group IDs for both 'nobody' and 'bin' and
> they are mutually exclusive and none of the other is supplementary
> group ID of the ID being tested
> ------------------------------------------------------------
>
> Should we treat this as Test case issue or kernel bug?
The different of 'nobody' and 'bin' is bin->GID has the CAP_FSETID
capability, but nobody->GID has not, I think.
Regards.
------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2009-06-29 7:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 7:00 [LTP] Issue observed with chmod05, fchmod05 test cases Sharyathi Nagesh
2009-06-29 7:33 ` Wei Yongjun [this message]
2009-06-29 10:30 ` Sharyathi Nagesh
2009-07-02 4:34 ` Sharyathi Nagesh
2009-07-20 11:25 ` Sharyathi Nagesh
2009-07-20 15:56 ` Garrett Cooper
2009-07-21 8:57 ` Sharyathi Nagesh
2009-07-30 18:28 ` Subrata Modak
2009-07-31 1:38 ` Sharyathi Nagesh
2009-07-31 1:54 ` Subrata Modak
2009-08-06 11:39 ` [LTP] [PATCH][RESEND] " Sharyathi Nagesh
2009-08-07 12:41 ` Subrata Modak
2009-09-15 10:27 ` Sharyathi Nagesh
2009-09-16 15:16 ` Subrata Modak
-- strict thread matches above, loose matches on Subject: below --
2009-07-21 9:35 [LTP] " Munipradeep Beerakam
2009-07-21 11:31 ` Sharyathi Nagesh
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=4A486E66.5050102@cn.fujitsu.com \
--to=yjwei@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=mbeeraka@in.ibm.com \
--cc=sharyath@in.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.