mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nikita Danilov <nikita@clusterfs.com>
To: "Joshua Hudson" <joshudson@gmail.com>
Cc: Linux Kernel Mailing List <Linux-Kernel@vger.kernel.org>
Subject: Re: what is necessary for directory hard links
Date: Mon, 24 Jul 2006 10:45:45 +0400	[thread overview]
Message-ID: <17604.27801.796726.164279@gargle.gargle.HOWL> (raw)
In-Reply-To: <bda6d13a0607221113s7e583492x783651eb9613b87f@mail.gmail.com>

Joshua Hudson writes:
 > On 7/22/06, Bodo Eggert <7eggert@elstempel.de> wrote:
 > > Horst H. von Brand <vonbrand@inf.utfsm.cl> wrote:
 > >
 > > > Joshua Hudson <joshudson@gmail.com> wrote:
 > > >> This patch is the sum total of all that I had to change in the kernel
 > > >> VFS layer to support hard links to directories
 > > >
 > > > Can't be done, as it creates the possibility of loops.
 > >
 > > Don't do that then?
 > Exactly.
 > 
 > > > Detecting unconnected subgraphs uses a /lot/ of memory; and much worse, you
 > > > have to stop (almost) all filesystem activity while doing it.
 > I know.
 > 
 > I just decided the price is worth it.
 > 
 > In my filesystem, any attempt to create a loop of hard links
 > is detected and cancelled. 

Can you elaborate a bit on this exciting mechanism? Obviously an ability
to efficiently detect loops would be a break-through in a
reference-counted garbage collection, somehow missed for last 40
years. :-)

 >                            Unlinking a directory requires it
 > to be empty if the last link is being removed. "." and ".."
 > links are counted separately from real links, so that is easy.

Nikita.


  reply	other threads:[~2006-07-24  6:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6ARGK-19L-5@gated-at.bofh.it>
     [not found] ` <6B8og-1iB-17@gated-at.bofh.it>
2006-07-22 16:59   ` Bodo Eggert
2006-07-22 18:13     ` Joshua Hudson
2006-07-24  6:45       ` Nikita Danilov [this message]
2006-07-24  7:25         ` Valdis.Kletnieks
2006-07-24 16:21           ` Joshua Hudson
2006-07-24 17:55             ` Horst H. von Brand
2006-07-24 18:22             ` Valdis.Kletnieks
2006-07-25  4:49               ` Joshua Hudson
2006-07-25 12:43                 ` Valdis.Kletnieks
2006-07-25 14:47                 ` Horst H. von Brand
2006-07-23  2:19     ` Horst H. von Brand
2006-07-23 22:27       ` Vernon Mauery
2006-07-25 23:43       ` Peter Chubb
     [not found] <6CcT1-1lH-39@gated-at.bofh.it>
     [not found] ` <6Cwov-5xl-5@gated-at.bofh.it>
2006-07-25 21:28   ` Bodo Eggert
2006-07-26  1:00     ` Horst H. von Brand
2006-07-26  9:13       ` Bodo Eggert
2006-07-21  1:04 Joshua Hudson
2006-07-21 18:49 ` Horst H. von Brand
2006-07-21 20:28 ` Rob Sims
2006-07-21 21:57   ` Joshua Hudson
2006-07-24  6:42     ` Nikita Danilov

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=17604.27801.796726.164279@gargle.gargle.HOWL \
    --to=nikita@clusterfs.com \
    --cc=Linux-Kernel@vger.kernel.org \
    --cc=joshudson@gmail.com \
    /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

all inboxes | Powered by JetHome®