From: clg@fr.ibm.com
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, xemul@openvz.org, serue@us.ibm.com,
Cedric Le Goater <clg@fr.ibm.com>
Subject: [patch 2/3] add do_unshare()
Date: Mon, 11 Feb 2008 10:58:08 +0100 [thread overview]
Message-ID: <20080211095847.396005856@fr.ibm.com> (raw)
In-Reply-To: <20080211095806.585883882@fr.ibm.com>
[-- Attachment #1: clone64-add-do_unshare.patch --]
[-- Type: text/plain, Size: 935 bytes --]
From: Cedric Le Goater <clg@fr.ibm.com>
This patch adds a do_unshare() routine which will be common
to the unshare() and unshare64() syscall.
Signed-off-by: Cedric Le Goater <clg@fr.ibm.com>
---
kernel/fork.c | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
Index: 2.6.24-mm1/kernel/fork.c
===================================================================
--- 2.6.24-mm1.orig/kernel/fork.c
+++ 2.6.24-mm1/kernel/fork.c
@@ -1694,7 +1694,7 @@ static int unshare_semundo(u64 unshare_f
* constructed. Here we are modifying the current, active,
* task_struct.
*/
-asmlinkage long sys_unshare(unsigned long unshare_flags)
+static long do_unshare(u64 unshare_flags)
{
int err = 0;
struct fs_struct *fs, *new_fs = NULL;
@@ -1788,3 +1788,8 @@ bad_unshare_cleanup_thread:
bad_unshare_out:
return err;
}
+
+asmlinkage long sys_unshare(unsigned long unshare_flags)
+{
+ return do_unshare(unshare_flags);
+}
--
next prev parent reply other threads:[~2008-02-11 9:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-11 9:58 [patch 0/3] clone64() and unshare64() syscalls clg
2008-02-11 9:58 ` [patch 1/3] change clone_flags type to u64 clg
2008-02-11 9:58 ` clg [this message]
2008-02-11 9:58 ` [patch 3/3] add the clone64() and unshare64() syscalls clg
2008-02-12 17:28 ` [patch 0/3] " Serge E. Hallyn
2008-04-09 22:26 [PATCH 0/3] clone64() and unshare64() system calls sukadev
2008-04-09 22:34 ` [PATCH 2/3] add do_unshare() sukadev
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=20080211095847.396005856@fr.ibm.com \
--to=clg@fr.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®