From: Daniel Lezcano <daniel.lezcano-GANU6spQydw@public.gmane.org>
To: Dan Smith <danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org
Subject: Re: [RFC] Payloads and transient filesystem support for user-cr
Date: Thu, 03 Mar 2011 19:18:25 +0100 [thread overview]
Message-ID: <4D6FDB71.7050603@free.fr> (raw)
In-Reply-To: <87vd005ks5.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
On 03/03/2011 03:41 PM, Dan Smith wrote:
> DL> Well a simple test program doing sem_* operations should have
> DL> spotted the problem.
>
> I know, can you believe that our stuff didn't test this specific case?
> I'll have to give the authors of our tests a hard time about this one
> for sure :)
Don't blame them. They may have missed the test case but you missed the
CR of the posix semaphore, far away from a couple of parsecs ;)
<javascript:void(0);>
next prev parent reply other threads:[~2011-03-03 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 21:35 [RFC] Payloads and transient filesystem support for user-cr Dan Smith
[not found] ` <1299101725-17603-1-git-send-email-danms-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2011-03-02 21:35 ` [PATCH 1/3] Make extract_headers.sh grab setns as well Dan Smith
2011-03-02 21:35 ` [PATCH 2/3] Export some things from restart.c Dan Smith
2011-03-02 21:35 ` [PATCH 3/3] [RFC] Add transient filesystem support to user-cr Dan Smith
2011-03-02 22:05 ` [RFC] Payloads and transient filesystem support for user-cr Daniel Lezcano
2011-03-03 0:23 ` Dan Smith
[not found] ` <877hch6oi2.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2011-03-03 8:35 ` Daniel Lezcano
2011-03-03 14:41 ` Dan Smith
[not found] ` <87vd005ks5.fsf-FLMGYpZoEPULwtHQx/6qkW3U47Q5hpJU@public.gmane.org>
2011-03-03 18:18 ` Daniel Lezcano [this message]
[not found] ` <4D6FDB71.7050603-GANU6spQydw@public.gmane.org>
2011-03-03 18:30 ` Dan Smith
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=4D6FDB71.7050603@free.fr \
--to=daniel.lezcano-ganu6spqydw@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=danms-r/Jw6+rmf7HQT0dZR+AlfA@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.