public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>, Pavel Emelyanov <xemul@openvz.org>,
	Manfred Spraul <manfred@colorfullife.com>,
	Michael Kerrisk <mtk.manpages@googlemail.com>,
	Nadia Derbey <Nadia.Derbey@bull.net>
Subject: Re: [PATCH 1/3] ipc: sysvsem: implement sys_unshare(CLONE_SYSVSEM)
Date: Thu, 17 Apr 2008 02:44:05 -0700	[thread overview]
Message-ID: <m13apkvmsa.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <20080416164232.GB22748@sergelap.austin.ibm.com> (Serge E. Hallyn's message of "Wed, 16 Apr 2008 11:42:32 -0500")

"Serge E. Hallyn" <serue@us.ibm.com> writes:

> (patches 1 and 2 were originally by Manfred Spraul)
>
> sys_unshare(CLONE_NEWIPC) doesn't handle the undo lists properly, this can
> cause a kernel memory corruption. CLONE_NEWIPC must detach from the existing
> undo lists.
>
> Fix, part 1: add support for sys_unshare(CLONE_SYSVSEM)
>
> The original reason to not support it was the potential (inevitable?)
> confusion due to the fact that sys_unshare(CLONE_SYSVSEM) has the
> inverse meaning of clone(CLONE_SYSVSEM).
>
> Our two most reasonable options then appear to be (1) fully support
> CLONE_SYSVSEM, or (2) continue to refuse explicit CLONE_SYSVSEM,
> but always do it anyway on unshare(CLONE_SYSVSEM).  This patch does
> (1).
>
> Changelog:
> 	Apr 16: SEH: switch to Manfred's alternative patch which
> 		removes the unshare_semundo() function which
> 		always refused CLONE_SYSVSEM.
>
> Signed-off-by: Manfred Spraul <manfred@colorfullife.com>
> Signed-off-by: Serge E. Hallyn <serue@us.ibm.com>

These patches look like the fix the core issue.

Acked-by: "Eric W. Biederman" <ebiederm@xmission.com>

Eric

  parent reply	other threads:[~2008-04-17 10:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-16 16:42 [PATCH 1/3] ipc: sysvsem: implement sys_unshare(CLONE_SYSVSEM) Serge E. Hallyn
2008-04-16 16:43 ` [PATCH 2/3] ipc: sysvsem: force unshare(CLONE_SYSVSEM) when CLONE_NEWIPC Serge E. Hallyn
2008-04-16 16:44 ` [PATCH 3/3] ipc: sysvsem: refuse clone(CLONE_SYSVSEM|CLONE_NEWIPC) Serge E. Hallyn
2008-04-17  9:44 ` Eric W. Biederman [this message]
2008-04-17 21:57 ` [PATCH 1/3] ipc: sysvsem: implement sys_unshare(CLONE_SYSVSEM) Andrew Morton

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=m13apkvmsa.fsf@frodo.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=Nadia.Derbey@bull.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    --cc=mtk.manpages@googlemail.com \
    --cc=serue@us.ibm.com \
    --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