linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@transmeta.com>
To: Alexander Viro <viro@math.psu.edu>
Cc: Andreas Dilger <adilger@turbolinux.com>,
	"H. Peter Anvin" <hpa@zytor.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [Re: Inodes]
Date: Mon, 14 May 2001 15:49:19 -0700	[thread overview]
Message-ID: <3B0060EF.9A3CF364@transmeta.com> (raw)
In-Reply-To: <Pine.GSO.4.21.0105141735001.19333-100000@weyl.math.psu.edu>

Alexander Viro wrote:
> 
> On Mon, 14 May 2001, H. Peter Anvin wrote:
> 
> > Correct.  At least at one time it used the offset of the directory entry
> > when that particular inode was last "seen" by the kernel... meaning that
> > when it finally dropped out of the inode cache, it would change inode
> > numbers.  I thought that was a reasonable (by no means perfect, though)
> > solution to a very sticky problem.
> 
> Unfortunately it wasn't a solution. Look: you open a file and rename it
> away. Now you want to create something in the old directory. Woops - can't
> use the old entry of our file, since we'll get icache conflict that way.
> So we get this lovely notion of reserved entries and there lies the
> madness. It gets especially nasty when you consider rmdir of something
> that used to be non-empty, but everything had been renamed away from it.
> And stayes open. Moreover, at every moment you need both the "original"
> location (inumber) and current one (for write_inode()). Better yet, you
> get to deal with opened files that are not renamed, but removed. Yes,
> all of that can be dealt with. The old driver didn't.
> 

True enough.

-- 
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt

      reply	other threads:[~2001-05-14 22:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-14  7:35 [Re: Inodes] Blesson Paul
2001-05-14 16:04 ` H. Peter Anvin
2001-05-14 17:02   ` Alan Cox
2001-05-14 20:53   ` Andreas Dilger
2001-05-14 21:08     ` Alexander Viro
2001-05-14 21:18       ` H. Peter Anvin
2001-05-14 21:44         ` Alexander Viro
2001-05-14 22:49           ` H. Peter Anvin [this message]

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=3B0060EF.9A3CF364@transmeta.com \
    --to=hpa@transmeta.com \
    --cc=adilger@turbolinux.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@math.psu.edu \
    /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).