LTP result output for container-init
balbir at linux.vnet.ibm.com
Wed Jan 16 08:07:09 PST 2008
* Rishikesh K. Rajak <risrajak at linux.vnet.ibm.com> [2008-01-16 20:57:48]:
> Hi All,
> Today i ran full LTP on kernel 2.6.24-rc6 inside container-init and also
> on parent namespace and got some observations.
> Here is the machine information:
> Linux rishi.in.ibm.com 2.6.18-53.el5 #1 SMP Wed Oct 10 16:34:02 EDT
> 2007 i686 i686 i386 GNU/Linux
> OS: SLES 10
Are you sure? Looks like this is a RHEL5 kernel (from your uname)
> I found these fcntl are failing inside container and it pass on parent
> namespace. I am attaching the log file with this mail.
> These failures are conceding with 2.6.23-mm1 itself. Just wanted to know
What do you mean by conceding with 2.6.23-mm1?
> if someone is working on this still.
LTP mailing list would be a better place to ask
> fcntl11 FAIL
> fcntl14 FAIL
> fcntl17 FAIL
> fcntl19 FAIL
> fcntl20 FAIL
> fcntl21 FAIL
> And also other observation was:
> syslog is failing inside parent namespace but pass inside
> syslog01 FAIL
> syslog02 FAIL
> syslog08 FAIL
> Please let me know your opinion on this.
These are good results, but analysis of the results will be very
useful. For example
1. You could list the diff with a LTP run in parent namespace vs
within the container
2. diff b/w LTP run in parent namespace vs a kernel without containers
enabled (this would obviously imply that the containers test cases
You could then try and get to the root cause of the failure(s) and
It would be useful to post the same results to the LTP mailing list
Linux Technology Center
More information about the Containers