Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 21 Jan 2002 04:07:26 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 21 Jan 2002 04:07:16 -0500 Received: from waldorf.cs.uni-dortmund.de ([129.217.4.42]:56513 "EHLO waldorf.cs.uni-dortmund.de") by vger.kernel.org with ESMTP id ; Mon, 21 Jan 2002 04:07:07 -0500 Message-Id: <200201210906.g0L96vT2001762@tigger.cs.uni-dortmund.de> To: Ville Herva cc: linux-kernel@vger.kernel.org Subject: Re: rm-ing files with open file descriptors In-Reply-To: Message from Ville Herva of "Sun, 20 Jan 2002 23:08:41 +0200." <20020120210841.GU51774@niksula.cs.hut.fi> Date: Mon, 21 Jan 2002 10:06:57 +0100 From: Horst von Brand Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Ville Herva said: > On Sun, Jan 20, 2002 at 09:44:31PM +0100, you [Andreas Ferber] claimed: > > On Sun, Jan 20, 2002 at 10:02:55PM +0200, Ville Herva wrote: > > > > > > Just out of interest (I'm not actually suggesting this would be useful, or > > > feasible): what about ilink(dev, inode_nr, "path") or iopen(dev, inode_nr)? > > > > > > Or /proc/inodes/dev/ ? > > > > ...which would successfully defeat any access control scheme based on > > directory permissions... > > Yeah - it could be root-only. > > But it's propably not useful anyway. There are filesystems around (MSDOS, VFAT) that haven't got fixed inode numbers for files. There are networked filesystems where this would need radical changes to the server side. Some even make up inode numbers on the fly IIRC. If in dire need, you could hack something together for by groveling over the disk image. e2fsprogs' libraries should come handy... -- Horst von Brand http://counter.li.org # 22616 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/