From: Pavel Emelyanov <xemul-GEFAQzZX7r8dnm+yROfE0A@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,
balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org
Subject: Re: [Devel] LTP result output for container-init
Date: Thu, 24 Jan 2008 12:59:01 +0300 [thread overview]
Message-ID: <47986165.4050407@openvz.org> (raw)
In-Reply-To: <1200497268.3999.17.camel-bi+AKbBUZKY6gyzm1THtWbp2dZbC/Bob@public.gmane.org>
Rishikesh K. Rajak wrote:
> 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
>
> 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
> if someone is working on this still.
>
> fcntl11 FAIL
> fcntl14 FAIL
> fcntl17 FAIL
> fcntl19 FAIL
> fcntl20 FAIL
> fcntl21 FAIL
As I already said, these are fixed in -mm tree with the
pid-namespaces-vs-locks-interaction.patch patch.
> 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
What really bothers me in this case is that in the "output"
file you attached I see
<<<test_output>>>
syslog08 0 INFO : Test all the facilities at a particular level.
syslog08 0 INFO : Facilities available are: LOG_KERN, LOG_USER, LOG_MAIL
syslog08 0 INFO : LOG_DAEMON, LOG_AUTH, LOG_LPR.
syslog08 0 INFO : Don't know how to send kernel messages from syslog()
syslog08 0 INFO : o Create seperate entries in config file for each facility.
syslog08 0 INFO : o Send the message and grep for the entry in log file.
syslog08 0 INFO : syslog: Testing all the facilities
syslog08 0 INFO : Doing facility: user...
syslog08 0 INFO : Restart /etc/init.d/syslog
syslog08 0 INFO : Facility user passed
syslog08 0 INFO : Doing facility: mail...
syslog08 0 INFO : Restart /etc/init.d/syslog
syslog08 0 INFO : Facility mail failed
syslog08 0 INFO : Doing facility: daemon...
syslog08 0 INFO : Restart /etc/init.d/syslog
syslog08 0 INFO : Facility daemon passed
syslog08 0 INFO : Doing facility: auth...
syslog08 0 INFO : Restart /etc/init.d/syslog
syslog08 0 INFO : Facility auth passed
syslog08 0 INFO : Doing facility: lpr...
syslog08 0 INFO : Restart /etc/init.d/syslog
syslog08 0 INFO : Facility lpr passed
syslog08 1 PASS : some facilities failed to work
syslog08 0 INFO : restart /etc/init.d/syslog
The says it passed, but the status is "some facilities failed to
work" and the log file says that the test failed %)
I launched ltp on my box but the 01, 02 and 08 syslog tests
passed... I have a CentOS 4 setup on this node, maybe this
is a SuSE issue? Rishikesh, can you try this on another OS?
> Please let me know your opinion on this.
>
> Thanks
>
> Rishi
> IBM LTC
> Bangalore
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Devel mailing list
> Devel-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org
> https://openvz.org/mailman/listinfo/devel
next prev parent reply other threads:[~2008-01-24 9:59 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
[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 ` Pavel Emelyanov [this message]
[not found] ` <47986165.4050407-GEFAQzZX7r8dnm+yROfE0A@public.gmane.org>
2008-01-24 12:35 ` [Devel] " 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=47986165.4050407@openvz.org \
--to=xemul-gefaqzzx7r8dnm+yrofe0a@public.gmane.org \
--cc=Poornima.Nayak-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org \
--cc=balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@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 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.