From: Li Zefan <lizf@cn.fujitsu.com>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
torvalds@linux-foundation.org,
lkml <linux-kernel@vger.kernel.org>,
stable@kernel.org, Pavel Emelyanov <xemul@openvz.org>,
Daniel Lezcano <dlezcano@fr.ibm.com>
Subject: Re: [PATCH 1/1] devices cgroup: allow mkfifo
Date: Sat, 13 Dec 2008 15:09:06 +0800 [thread overview]
Message-ID: <49435F92.5070102@cn.fujitsu.com> (raw)
In-Reply-To: <20081212143458.GC9571@us.ibm.com>
>> hm. I'd looked at your description and decided this was 2.6.29 material.
>>
>> But you think it's for 2.6.28 and even for 2.6.27. How come?
>>
>> (iow, your changelog sucked :)
>
> Sorry, I should have put the exchange between Li and I in there.
> (Ouch, and I didn't cc: Li this time! Sorry, Li.)
>
> Li thought it was 2.6.27/2.6.27 material. I thought not, but wanted
> to see what the -stable folks thought.
>
I was not sure about this.
> This is not a security hole, and since noone has complained before
> it doesn't appear to be too inconvenient. Until the fix goes
> up, container users can always create the fifos and socks on the
> root image while creating the container, before entering the
> device whitelist.
>
Now the explanation makes it clear for me, thx. :)
next prev parent reply other threads:[~2008-12-13 7:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-11 15:50 [PATCH 1/1] devices cgroup: allow mkfifo Serge E. Hallyn
2008-12-12 3:12 ` Andrew Morton
2008-12-12 14:34 ` Serge E. Hallyn
2008-12-13 7:09 ` Li Zefan [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-10 15:57 Serge E. Hallyn
2008-12-11 0:56 ` Li Zefan
2008-12-11 14:59 ` Serge E. Hallyn
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=49435F92.5070102@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=dlezcano@fr.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=stable@kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xemul@openvz.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