mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Steve Youngs <sryoungs@bigpond.net.au>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Increase recursive symlink limit from 5 to 8
Date: Sun, 11 Jan 2004 13:10:28 +0100	[thread overview]
Message-ID: <1073823028.1095.1.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <microsoft-free.87isjj0y1e.fsf@eicq.dnsalias.org>

On Sun, 2004-01-11 at 08:01, Steve Youngs wrote:
> * Petter Reinholdtsen <pere@hungry.com> writes:
> 
>   >   Linux:         Symlink limit seem to be 6 path entities.
>   >   AIX:           Symlink limit seem to be 21 path entities.
>   >   HP-UX:         Symlink limit seem to be 21 path entities.
>   >   Solaris:       Symlink limit seem to be 21 path entities.
>   >   Irix:          Symlink limit seem to be 31 path entities.
>   >   Mac OS X:      Symlink limit seem to be 33 path entities.
>   >   Tru64 Unix:    Symlink limit seem to be 65 path entities.
> 
>   > I really think this limit should be increased in Linux.  Not sure
>   > how high it should go, but from 5 to somewhere between 20 and 64
>   > seem like a good idea to me.
> 
> 6 does seem pretty low.  What was the reason for setting it there?  Is
> there a downside to increasing it?

I think we cannot set this value much higher due to constraints in
kernel stack size, and this limits maximum recursion levels.


      parent reply	other threads:[~2004-01-11 12:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 23:12 Petter Reinholdtsen
2004-01-11  1:03 ` Petter Reinholdtsen
2004-01-11  7:01   ` Steve Youngs
2004-01-11  9:37     ` Peter Osterlund
2004-01-11  9:49     ` Arjan van de Ven
2004-01-16  0:45       ` GOTO Masanori
2004-01-16  0:56         ` Måns Rullgård
2004-01-16  1:25         ` viro
2004-01-16 15:46           ` Andries Brouwer
2004-01-16  3:08         ` Steve Youngs
2004-01-11 12:10     ` Felipe Alfaro Solana [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=1073823028.1095.1.camel@teapot.felipe-alfaro.com \
    --to=felipe_alfaro@linuxmail.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sryoungs@bigpond.net.au \
    /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®