public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Frank van Maarseveen <F.vanMaarseveen@inter.NL.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: isofs hardlink bug (inode numbers different)
Date: Tue, 04 Feb 2003 13:52:53 -0800	[thread overview]
Message-ID: <3E403635.9050303@zytor.com> (raw)
In-Reply-To: 20030204212812.GA32465@iapetus.localdomain

Frank van Maarseveen wrote:
> 
> Suppose that the root of a iso9660 has entries such as '/', '.' and '..'
> all with inode 2 and maybe that there are  some other indications that
> the creator applied UNIX style inode numbering, wouldn't it be reasonable
> to assume that inode numbers should be trusted?
> 

The thing is, RockRidge attributes are a file-by-file thing.  You can
have it on half the files if you want.

Of course, since Linux isn't dependent on the inode numbers to find the
directory entries anymore (since we now have dentries), one could
rewrite the iso9660 filesystem so that it doesn't matter.  This is a
major rewrite, however.  It wouldn't be unwelcome; the current code is
pretty awful.

	-hpa


  reply	other threads:[~2003-02-04 21:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-26 23:55 isofs hardlink bug (inode numbers different) Volker Kuhlmann
2003-02-04  3:48 ` H. Peter Anvin
2003-02-04 21:28   ` Frank van Maarseveen
2003-02-04 21:52     ` H. Peter Anvin [this message]
2003-02-05 11:30   ` Kasper Dupont
2003-02-05 19:41     ` H. Peter Anvin
  -- strict thread matches above, loose matches on Subject: below --
2003-02-10 21:16 James Pearson

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=3E403635.9050303@zytor.com \
    --to=hpa@zytor.com \
    --cc=F.vanMaarseveen@inter.NL.net \
    --cc=linux-kernel@vger.kernel.org \
    /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