From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com>
To: subrata@vnet.linux.ibm.com
Cc: ltp-list@lists.sourceforge.net
Subject: [LTP] : drop test pidns03 ?
Date: Thu, 5 Aug 2010 17:00:59 -0700 [thread overview]
Message-ID: <20100806000058.GA15483@us.ibm.com> (raw)
I am not sure about the original intent of pidns03 test case but I think
the test is expected to fail :-(
The header for this test says:
* Verify that:
* 1. When parent, clone a process with flag CLONE_NEWPID, see the
* process id of the parent is existing after mounting /proc
The test passes in the parent-pid from init-pid-ns and looks for that
pid in the child's mount of /proc.
But for the CLONE_NEWPID child, parent process should appear to have a
pid == 0. The pid of the parent in the initial pid namespace must NOT
be visible to the child - in fact a different process can have that pid.
I am not surprised the test fails - I am curious to know the version of
the kernel when this test reliably passed - if at all. I tried this on
2.6.29 and 2.6.34-rc5 and it fails reliably.
I dug through my history and see that this test was part of a 6-patch set,
We did have some comments on the coding style on the set, but we seem to
have missed the intent of this test :-(.
Do we have any other history of this test ? If not, I think we should either
drop the test or modify the test to verify the opposite (i.e. verify that
the opendir() in the test fails with ENOENT).
Sukadev
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2010-08-05 23:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 0:00 Sukadev Bhattiprolu [this message]
2010-08-16 14:41 ` [LTP] : drop test pidns03 ? 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=20100806000058.GA15483@us.ibm.com \
--to=sukadev@linux.vnet.ibm.com \
--cc=ltp-list@lists.sourceforge.net \
--cc=subrata@vnet.linux.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.