public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ferber <aferber@techfak.uni-bielefeld.de>
To: linux-kernel@vger.kernel.org
Cc: Ville Herva <vherva@twilight.cs.hut.fi>
Subject: Re: rm-ing files with open file descriptors
Date: Sun, 20 Jan 2002 21:44:31 +0100	[thread overview]
Message-ID: <20020120214430.A4000@devcon.net> (raw)
In-Reply-To: <87lmevjrep.fsf@localhost.localdomain> <Pine.LNX.3.95.1020118163838.3008B-100000@chaos.analogic.com> <a2afsg$73g$2@ncc1701.cistron.net> <20020120152359.B326@localhost> <20020120200255.GG135220@niksula.cs.hut.fi>
In-Reply-To: <20020120200255.GG135220@niksula.cs.hut.fi>; from vherva@niksula.hut.fi on Sun, Jan 20, 2002 at 10:02:55PM +0200

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/<nr> ?

...which would successfully defeat any access control scheme based on
directory permissions...

Andreas
-- 
       Andreas Ferber - dev/consulting GmbH - Bielefeld, FRG
     ---------------------------------------------------------
         +49 521 1365800 - af@devcon.net - www.devcon.net

  reply	other threads:[~2002-01-20 20:44 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-18 21:11 rm-ing files with open file descriptors Doug Alcorn
2002-01-18 21:27 ` Xavier Bestel
2002-01-18 21:28 ` Ken Brownfield
2002-01-19 20:23   ` Rob Landley
2002-01-18 21:49 ` Richard B. Johnson
2002-01-19  0:50   ` Miquel van Smoorenburg
2002-01-19  2:29     ` H. Peter Anvin
2002-01-19 10:57       ` Xavier Bestel
2002-01-19 11:10       ` Miquel van Smoorenburg
2002-01-19 11:28         ` Alexander Viro
2002-01-19 12:01           ` Miquel van Smoorenburg
2002-01-23 12:18             ` Pavel Machek
2002-01-24  9:46               ` Herbert Xu
2002-01-19 17:44           ` Kai Henningsen
2002-01-20 15:30             ` Richard Kettlewell
2002-01-20 18:21               ` Doug McNaught
2002-01-20 23:10               ` Miquel van Smoorenburg
2002-01-20  3:55           ` Chris Wedgwood
2002-01-19 15:21         ` Horst von Brand
2002-01-19 15:32           ` Mr. James W. Laferriere
2002-01-19 20:26             ` Rob Landley
2002-01-19 17:53           ` Miquel van Smoorenburg
2002-01-20 15:48             ` Horst von Brand
2002-01-19 20:24           ` Rob Landley
2002-01-19 11:15       ` Ville Herva
2002-01-19 12:16       ` Matthias Schniedermeyer
2002-01-19 12:22         ` Xavier Bestel
2002-01-19 12:29           ` Alexander Viro
2002-01-19 12:46             ` Xavier Bestel
2002-01-19 13:18               ` Rogier Wolff
2002-01-19 15:24             ` Horst von Brand
2002-01-19 14:50     ` Horst von Brand
2002-01-20 14:23     ` Remi Turk
2002-01-20 20:02       ` Ville Herva
2002-01-20 20:44         ` Andreas Ferber [this message]
2002-01-20 21:08           ` Ville Herva
2002-01-21  9:06             ` Horst von Brand
2002-01-21  9:21               ` Ville Herva
2002-01-18 21:59 ` J Sloan
2002-01-19  4:18 ` Andreas Bombe
2002-01-19 14:51   ` christophe barbé
2002-01-19 18:01     ` Kai Henningsen
2002-01-20  3:43       ` christophe barbé
  -- strict thread matches above, loose matches on Subject: below --
2002-01-18 22:11 Hank Leininger

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=20020120214430.A4000@devcon.net \
    --to=aferber@techfak.uni-bielefeld.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vherva@twilight.cs.hut.fi \
    /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