All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <lkml@tlinx.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: max symlink = 5? ?bug? ?feature deficit?
Date: Sun, 12 Feb 2006 16:54:23 -0800	[thread overview]
Message-ID: <43EFD8BF.1040205@tlinx.org> (raw)
In-Reply-To: <20060213000803.GY27946@ftp.linux.org.uk>

Al Viro wrote:
> On Sun, Feb 12, 2006 at 02:54:33PM -0800, Linda Walsh wrote:
>   
>> Al Viro wrote:
>>     
>>> Care to RTFS? I mean, really - at least to the point of seeing what's
>>> involved in that recursion.
>>>  
>>>       
>> Hmmm...that's where I got the original parameter numbers, but
>> I see it's not so straightforward.  I tried a limit of
>> 40, but I quickly get an OS hang when trying to reference a
>> 13th link.  Twelve works at the limit, but would take more testing
>> to find out the bottleneck.
>>     
>
> Sigh...  12 works at the limit on your particular config, filesystems
> being used and syscall being issued (hint: amount of stuff on stack
> before we enter mutual recursion varies; so does the amount of stuff
> on stack we get from function that are not part of mutual recursion,
> but are called from the damn thing).
>   
---
    Yeah, I sorta figured that.  Is there any easier way to
remove the recursion?  I dunno about you, but I was always taught
that recursion, while elegant, was not always the most efficient in
terms of time and space requirements and one could get similar
functionality using iteration and a stack.

    The GNU libraries _seem_ to indicate a max of 20 links supported
there.  Googling around, I see I'm not the first person to be surprised
by the low limit.  I don't recall running into such a limit on any
other Unixes, though I'm sure they had some limit.

    It can be useful for creating a shadow file-system where only
root needs to point to a "target source", and the "symlink" overlay
lies over the top of any real, underlying file.

    Why can't things just be easy sometimes...:-/
Linda

  reply	other threads:[~2006-02-13  0:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11  3:31 max symlink = 5? ?bug? ?feature deficit? Linda Walsh
2006-02-12 10:27 ` Jan Engelhardt
2006-02-12 20:46   ` [PATCH] Use one constant to control MAX SYMLINKS in a name Linda Walsh
2006-02-12 21:16     ` Al Viro
2006-02-12 18:06 ` max symlink = 5? ?bug? ?feature deficit? Al Viro
2006-02-12 19:19   ` Dave Jones
2006-02-12 19:36   ` Matthew Wilcox
2006-02-12 19:48     ` Al Viro
2006-02-12 21:18   ` Linda Walsh
2006-02-12 21:25     ` Al Viro
2006-02-12 22:54       ` Linda Walsh
2006-02-13  0:08         ` Al Viro
2006-02-13  0:54           ` Linda Walsh [this message]
2006-02-13  7:37             ` Willy Tarreau
2006-02-13  7:48               ` Arjan van de Ven
2006-02-13  8:03                 ` Willy Tarreau
2006-02-13  8:11                   ` Al Viro
2006-02-13 14:10                   ` Olivier Galibert
2006-02-13  8:20               ` Helge Hafting
  -- strict thread matches above, loose matches on Subject: below --
2006-02-12 15:16 linux

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=43EFD8BF.1040205@tlinx.org \
    --to=lkml@tlinx.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@ftp.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.