From: Cyrill Gorcunov <gorcunov@openvz.org>
To: Konstantin Khlebnikov <khlebnikov@openvz.org>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Alexey Dobriyan <adobriyan@gmail.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"drepper@gmail.com" <drepper@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH] nextfd(2)
Date: Mon, 2 Apr 2012 13:26:27 +0400 [thread overview]
Message-ID: <20120402092627.GC7607@moon> (raw)
In-Reply-To: <4F796581.1030302@openvz.org>
On Mon, Apr 02, 2012 at 12:38:25PM +0400, Konstantin Khlebnikov wrote:
> 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.
Kind of ;) At moment we drain fds from dumpee task context to
our tool context and then dump them.
Cyrill
next prev parent reply other threads:[~2012-04-02 9:26 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-01 12:57 [PATCH] nextfd(2) Alexey Dobriyan
2012-04-01 13:58 ` Konstantin Khlebnikov
2012-04-01 21:30 ` Alexey Dobriyan
2012-04-02 0:09 ` Alan Cox
2012-04-02 8:38 ` Konstantin Khlebnikov
2012-04-02 9:26 ` Cyrill Gorcunov [this message]
2012-04-01 15:43 ` Eric Dumazet
2012-04-01 21:31 ` Alexey Dobriyan
2012-04-01 21:36 ` Alan Cox
2012-04-01 17:20 ` Linus Torvalds
2012-04-01 18:28 ` Valentin Nechayev
2012-04-01 21:33 ` Alexey Dobriyan
2012-04-01 19:21 ` Arnd Bergmann
2012-04-01 21:35 ` Alexey Dobriyan
2012-04-01 22:05 ` H. Peter Anvin
2012-04-04 12:13 ` Arnd Bergmann
2012-04-01 22:03 ` H. Peter Anvin
2012-04-01 22:13 ` H. Peter Anvin
2012-04-02 0:08 ` Alan Cox
2012-04-30 9:58 ` Valentin Nechayev
2012-04-02 1:19 ` Kyle Moffett
2012-04-02 1:37 ` H. Peter Anvin
2012-04-02 11:37 ` Ulrich Drepper
2012-04-06 9:54 ` Alexey Dobriyan
2012-04-06 15:27 ` Colin Walters
2012-04-06 16:14 ` H. Peter Anvin
2012-04-06 20:16 ` Alexey Dobriyan
2012-04-06 20:33 ` H. Peter Anvin
2012-04-06 21:02 ` H. Peter Anvin
2012-04-12 10:54 ` Alexey Dobriyan
2012-04-12 11:11 ` Alan Cox
2012-04-12 13:35 ` Alexey Dobriyan
2012-04-12 13:51 ` H. Peter Anvin
2012-04-12 19:21 ` Alexey Dobriyan
2012-04-12 14:09 ` Eric Dumazet
2012-04-06 16:23 ` H. Peter Anvin
2012-04-07 21:21 ` Ben Pfaff
2012-04-11 0:12 ` KOSAKI Motohiro
2012-04-11 0:09 ` KOSAKI Motohiro
2012-04-11 17:58 ` H. Peter Anvin
2012-04-11 18:04 ` Linus Torvalds
2012-04-11 18:11 ` H. Peter Anvin
2012-04-11 19:46 ` KOSAKI Motohiro
2012-04-11 19:49 ` H. Peter Anvin
2012-04-11 20:23 ` KOSAKI Motohiro
2012-04-11 20:32 ` H. Peter Anvin
2012-04-17 18:12 ` KOSAKI Motohiro
2012-04-11 18:00 ` H. Peter Anvin
2012-04-11 19:20 ` KOSAKI Motohiro
2012-04-11 19:22 ` H. Peter Anvin
2012-04-11 19:26 ` KOSAKI Motohiro
2012-04-11 19:28 ` H. Peter Anvin
2012-04-11 19:31 ` KOSAKI Motohiro
2012-04-11 19:32 ` H. Peter Anvin
2012-04-02 23:17 ` KOSAKI Motohiro
2012-04-02 23:56 ` H. Peter Anvin
2012-04-04 11:51 ` Ulrich Drepper
2012-04-04 16:38 ` KOSAKI Motohiro
2012-04-04 16:43 ` Ulrich Drepper
2012-04-04 17:07 ` KOSAKI Motohiro
2012-04-04 17:49 ` Ulrich Drepper
2012-04-04 18:08 ` KOSAKI Motohiro
2012-04-04 16:31 ` KOSAKI Motohiro
2012-04-04 17:10 ` Colin Walters
2012-04-04 17:25 ` Colin Walters
2012-04-04 23:35 ` KOSAKI Motohiro
2012-04-04 18:44 ` H. Peter Anvin
2012-04-03 19:21 ` Colin Walters
2012-04-04 3:01 ` Al Viro
2012-04-04 17:10 ` KOSAKI Motohiro
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=20120402092627.GC7607@moon \
--to=gorcunov@openvz.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=drepper@gmail.com \
--cc=khlebnikov@openvz.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).