From: Alexey Dobriyan Subject: Re: [PATCH] nextfd(2) Date: Mon, 2 Apr 2012 00:30:13 +0300 Message-ID: <20120401213013.GA4408@p183.telecom.by> References: <20120401125741.GA7484@p183.telecom.by> <4F785F1D.4020503@openvz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "akpm@linux-foundation.org" , "viro@zeniv.linux.org.uk" , "torvalds@linux-foundation.org" , "drepper@gmail.com" , "linux-kernel@vger.kernel.org" , "linux-fsdevel@vger.kernel.org" To: Konstantin Khlebnikov Return-path: Received: from mail-bk0-f46.google.com ([209.85.214.46]:63563 "EHLO mail-bk0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753369Ab2DAVaT (ORCPT ); Sun, 1 Apr 2012 17:30:19 -0400 Content-Disposition: inline In-Reply-To: <4F785F1D.4020503@openvz.org> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Sun, Apr 01, 2012 at 05:58:53PM +0400, Konstantin Khlebnikov wrote: > Alexey Dobriyan wrote: > > So, don't add closefrom(2), add nextfd(2). > > > > int nextfd(int fd) > > 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. You've added /proc/*/map_files for C/R making proc mandatory, so you do have /proc/*/fd .