From: Linda Walsh <lkml@tlinx.org>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: max symlink = 5? ?bug? ?feature deficit?
Date: Fri, 10 Feb 2006 19:31:07 -0800 [thread overview]
Message-ID: <43ED5A7B.7040908@tlinx.org> (raw)
The maximum number of followed symlinks seems to be set to 5.
This seems small when compared to other filesystem limits.
Is there some objection to it being raised? Should it be
something like Glib's '20' or '255'?
It would involve a change in include/namei.h and perhaps
a cleanup of the comment (which states the limit is '8') in
namei.c
There is some confusion with the shell utilities thinking
some links are valid, but other utilities giving an error:
> readlink -f cpu/args.t
/usr/src/packages/BUILD/perl-5.8.6/t/op/args.t
> cat cpu/args.t
cat: cpu/args.t: Too many levels of symbolic links
> namei cpu/args.t
f: cpu/args.t
d cpu
l args.t -> ../op/args.t
d ..
l op -> ../t/op/
d ..
l t -> perldir/t
l perldir -> perl-5.8.6
l perl-5.8.6 -> ../build/perl-5.8.6
d ..
l build -> BUILD
d BUILD
d perl-5.8.6
d t
d op
- args.t
next reply other threads:[~2006-02-11 3:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 3:31 Linda Walsh [this message]
2006-02-12 10:27 ` max symlink = 5? ?bug? ?feature deficit? 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
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=43ED5A7B.7040908@tlinx.org \
--to=lkml@tlinx.org \
--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