[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F796581.1030302@openvz.org>
Date: Mon, 02 Apr 2012 12:38:25 +0400
From: Konstantin Khlebnikov <khlebnikov@...nvz.org>
To: Alan Cox <alan@...rguk.ukuu.org.uk>
CC: Alexey Dobriyan <adobriyan@...il.com>,
"akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
"drepper@...il.com" <drepper@...il.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
Cyrill Gorcunov <gorcunov@...nvz.org>
Subject: Re: [PATCH] nextfd(2)
Alan Cox wrote:
>> Can we add "pid" argument to be able to search next fd in other task?
>> Together with sys_kcmp() this will be very useful for checkpoint/restore.
>
> That would raise all sorts of security questions unless protected, plus
> its got races. If you want to do that and you have the rights you can do
> it via procfs anyway.
Don't worry, I just asked. =) Seems like crtools dumps fd in the target-task context,
so the current version is suitable.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists