From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933864AbXCFCiO (ORCPT ); Mon, 5 Mar 2007 21:38:14 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933866AbXCFCiN (ORCPT ); Mon, 5 Mar 2007 21:38:13 -0500 Received: from terminus.zytor.com ([192.83.249.54]:60490 "EHLO terminus.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933864AbXCFCiN (ORCPT ); Mon, 5 Mar 2007 21:38:13 -0500 Message-ID: <45ECD3D4.5020305@zytor.com> Date: Mon, 05 Mar 2007 18:37:08 -0800 From: "H. Peter Anvin" User-Agent: Thunderbird 1.5.0.9 (X11/20070212) MIME-Version: 1.0 To: Davide Libenzi CC: Linus Torvalds , Linux Kernel Mailing List , Andrew Morton , Eric Dumazet Subject: Re: [patch v2] epoll use a single inode ... References: <45ECD122.6020907@zytor.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Davide Libenzi wrote: > > Right now is using: > > this.len = sprintf(name, "[%u.%d]", current->pid, fd); > > That should be unique and not have the wraparound problem. Ack? > NAK, very much NAK. File descriptors aren't file structures, they're *pointers* to file structures. It's perfectly possible -- downright common -- for a file descriptor to be inherited by another process, and then the pid is recycled -- collision. -hpa