From: Balbir Singh <balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: risrajak-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org
Cc: Poornima.Nayak-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org,
containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org,
serue-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org
Subject: Re: LTP result output for container-init
Date: Wed, 16 Jan 2008 21:37:09 +0530 [thread overview]
Message-ID: <20080116160709.GA8716@balbir.in.ibm.com> (raw)
In-Reply-To: <1200497268.3999.17.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
* Rishikesh K. Rajak <risrajak-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org> [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)
> 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
> 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)
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
--
Warm Regards,
Balbir Singh
Linux Technology Center
IBM, ISTL
next prev parent reply other threads:[~2008-01-16 16:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-16 15:27 LTP result output for container-init Rishikesh K. Rajak
[not found] ` <1200497268.3999.17.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
2008-01-16 16:07 ` Balbir Singh [this message]
[not found] ` <20080116160709.GA8716-SINUvgVNF2CyUtPGxGje5AC/G2K4zDHf@public.gmane.org>
2008-01-16 16:39 ` Rishikesh K. Rajak
2008-01-16 16:54 ` Dave Hansen
2008-01-16 17:31 ` sukadev-r/Jw6+rmf7HQT0dZR+AlfA
2008-01-24 9:59 ` [Devel] " Pavel Emelyanov
[not found] ` <47986165.4050407-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-01-24 12:35 ` Rishikesh K Rajak
2008-01-28 14:35 ` Rishikesh K Rajak
2008-01-29 16:12 ` [Devel] LTP result output for container-init ( failure with 2.6.24 kernel ) Rishikesh K Rajak
2008-01-29 17:43 ` Serge E. Hallyn
2008-01-24 10:32 ` [Devel] LTP result output for container-init Pavel Emelyanov
[not found] ` <4798693E.5080801-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-01-24 12:43 ` Rishikesh K Rajak
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=20080116160709.GA8716@balbir.in.ibm.com \
--to=balbir-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
--cc=Poornima.Nayak-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=risrajak-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org \
--cc=serue-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=sukadev-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
/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