LTP result output for container-init

Rishikesh K. Rajak risrajak at linux.vnet.ibm.com
Wed Jan 16 08:39:46 PST 2008


On Wed, 2008-01-16 at 21:37 +0530, Balbir Singh wrote:

> * Rishikesh K. Rajak <risrajak at linux.vnet.ibm.com> [2008-01-16 20:57:48]:
> 
> Hi, Rishi,
> 
> > 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)

Yeah, something interesting, but It's true it is SUSE.

:~/rishi/result # cat /etc/issue
    Welcome to SUSE Linux Enterprise Server 10 SP2 Alpha2 (i586) -
Kernel \r (\l).

> 
> > 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?

This means i have reported this problem earlier also to concern
developer and i have heard that it is already a known problem for pidns.
So just wanted to know if it is being fix by someone.


> 
> > if someone is working on this still.
> 
> LTP mailing list would be a better place to ask


Yes CC'ing to ltp-list@ also.

> 
> > 
> >   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
> > container-init.
> > 
> > syslog01                       FAIL
> > 1                                        
> > syslog02                       FAIL
> > 1                                        
> > syslog08                       FAIL
> > 1                                        
> > 
> > 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
>    won't run)
> 


First case has already been taken care and i provided the attached
result. The mail text is diff of LTP result between parent namespace Vs
container-init.

Yes second case sounds good, result can be expected soon for this,
thanks balbir.

Rishi

> You could then try and get to the root cause of the failure(s) and
> report them.
> 
> It would be useful to post the same results to the LTP mailing list
> and I 
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.linux-foundation.org/pipermail/containers/attachments/20080116/dfa5d3b4/attachment.htm


More information about the Containers mailing list