From: sukadev-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org
To: Dave Hansen <haveblue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Poornima.Nayak-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org,
risrajak-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: LTP result output for container-init
Date: Wed, 16 Jan 2008 09:31:58 -0800 [thread overview]
Message-ID: <20080116173158.GA19456@us.ibm.com> (raw)
In-Reply-To: <1200502497.22674.163.camel@localhost>
Dave Hansen [haveblue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org] wrote:
| On Wed, 2008-01-16 at 20:57 +0530, Rishikesh K. Rajak wrote:
| > These failures are conceding with 2.6.23-mm1 itself. Just wanted to
| > know if someone is working on this still.
I think Rishi is referring to these failures when running LTP in
a child pid namespace. That is a known problem. Its not a regression
but a pending task in pid namespace cleanup.
| >
| > fcntl11 FAIL
| > fcntl14 FAIL
| > fcntl17 FAIL
| > fcntl19 FAIL
| > fcntl20 FAIL
| > fcntl21 FAIL
|
| Do you mean that these are happening with 2.6.23-mm1, even without any
| lxc patches?
|
| Have you reported these to LKML or to Andrew Morton? If not, please do.
| You can make sure to garner attention by putting something like,
|
| 2.6.23-mm1 fcntl regressions
|
| as the subject. But, please do make sure they're regressions, and
| pinpoint the versions where they occur. You should also be prepared to
| do a bisection of the patches in -mm to find it.
|
| -- Dave
next prev parent reply other threads:[~2008-01-16 17:31 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 [this message]
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=20080116173158.GA19456@us.ibm.com \
--to=sukadev-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=Poornima.Nayak-xthvdsQ13ZrQT0dZR+AlfA@public.gmane.org \
--cc=balbir-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=haveblue-r/Jw6+rmf7HQT0dZR+AlfA@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