The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kaih@khms.westfalen.de (Kai Henningsen)
To: viro@math.psu.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: Question about ext2
Date: 14 Jul 2001 13:37:00 +0200	[thread overview]
Message-ID: <84pyH-xHw-B@khms.westfalen.de> (raw)
In-Reply-To: <Pine.GSO.4.21.0107140151420.19749-100000@weyl.math.psu.edu>
In-Reply-To: <Pine.GSO.4.21.0107140151420.19749-100000@weyl.math.psu.edu>

viro@math.psu.edu (Alexander Viro)  wrote on 14.07.01 in <Pine.GSO.4.21.0107140151420.19749-100000@weyl.math.psu.edu>:

> On 13 Jul 2001, Kai Henningsen wrote:
>
> > viro@math.psu.edu (Alexander Viro)  wrote on 13.07.01 in
> > <Pine.GSO.4.21.0107130623510.17323-100000@weyl.math.psu.edu>:
> >
> > > The only really obscure part is dropping an extra reference if victim is
> > > a directory - then we know that we are cannibalizing the last external
> > > link to it and the only link that remains is victim's ".". We don't want
> > > it to prevent victim's removal, so we drive i_nlink of victim to zero.
> >
> > Does this stuff work right with those cases which do linkcount=1 either
> > because the fs doesn't have a link count, or because the real link count
> > has grown too large?
>
> It doesn't. If fs doesn't have link count you are very likely to need
> other ways to deal with rename() anyway (e.g. you are pretty likely to
> have part of metadata stored in directory entry). If you are playing
> with "set i_nlink to 1 if it's too large" (which works only for directories,
> BTW) - change according to your encoding scheme for link count.

You are, of course, aware that ext2 (or at least current patches to ext2,  
I'm not sure if this particular thing has gone in yet) does use that  
scheme.

MfG Kai

      reply	other threads:[~2001-07-14 12:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-13  8:08 Question about ext2 malfet
2001-07-13  8:42 ` Andrew Morton
2001-07-13  9:57   ` Re[2]: " malfet
2001-07-13 10:23     ` Alexander Viro
2001-07-13 10:57   ` Alexander Viro
2001-07-13 20:22     ` Kai Henningsen
2001-07-14  5:58       ` Alexander Viro
2001-07-14 11:37         ` Kai Henningsen [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=84pyH-xHw-B@khms.westfalen.de \
    --to=kaih@khms.westfalen.de \
    --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