mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: [PATCH] symlink nesting level change
Date: Wed, 3 May 2006 04:08:49 +0100	[thread overview]
Message-ID: <20060503030849.GZ27946@ftp.linux.org.uk> (raw)
In-Reply-To: <e3966u$dje$1@terminus.zytor.com>

On Tue, May 02, 2006 at 07:57:34PM -0700, H. Peter Anvin wrote:
> Followup to:  <44580CF2.7070602@tlinx.org>
> By author:    Linda Walsh <lkml@tlinx.org>
> In newsgroup: linux.dev.kernel
> > Is this what you are looking for?
> > include/linux/namei.h    MAX_NESTED_LINKS = 5
> > (used in fs/namei.c, where comment claims MAX_NESTING is equal to 8)
> 
> Wonder if it would make sense to make this a sysctl...

No.  It's way past time to bump it to 8.  Everyone had been warned - for
months now.

Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
----
--- a/include/linux/namei.h	2006-03-31 20:08:42.000000000 -0500
+++ b/include/linux/namei.h	2006-05-02 23:06:46.000000000 -0400
@@ -11,7 +11,7 @@
 	struct file *file;
 };
 
-enum { MAX_NESTED_LINKS = 5 };
+enum { MAX_NESTED_LINKS = 8 };
 
 struct nameidata {
 	struct dentry	*dentry;

  reply	other threads:[~2006-05-03  3:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02 18:05 Too many levels of symbolic links Brian D. McGrew
2006-05-03  1:52 ` Linda Walsh
2006-05-03  2:57   ` H. Peter Anvin
2006-05-03  3:08     ` Al Viro [this message]
2006-05-04  1:35       ` [PATCH] symlink nesting level change Andrew Morton
2006-05-04  6:55         ` Arjan van de Ven
2006-05-04  7:19         ` Al Viro
2006-07-13 18:35         ` Tim Pepper
2006-07-13 21:27           ` Andrew Morton
2006-05-17 20:58     ` Too many levels of symbolic links Tim Pepper
2006-05-18 19:20       ` Tim Pepper

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=20060503030849.GZ27946@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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

Powered by JetHome