All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Al Viro <viro@ftp.linux.org.uk>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [PATCH] symlink nesting level change
Date: Wed, 3 May 2006 18:35:54 -0700	[thread overview]
Message-ID: <20060503183554.87f0218d.akpm@osdl.org> (raw)
In-Reply-To: <20060503030849.GZ27946@ftp.linux.org.uk>

On Wed, 3 May 2006 04:08:49 +0100
Al Viro <viro@ftp.linux.org.uk> wrote:

> 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;

It's a non-back-compatible change which means that people will install
2.6.18+, will set stuff up which uses more that five nested links and some
will discover that they can no longer run their software on older kernels.

It'll only hurt a very small number of people, but for those people, it
will hurt a lot.  And I can't really think of anything we can do to help
them, apart from making the new behaviour runtime-controllable, defaulting
to "off", but add a once-off printk when we hit MAX_NESTED_LINKS, pointing
them at a document which tells them how to turn on the new behaviour and
which explains the problems.  Which sucks.

But I guess as major distros are 2.6.16-based, this is a good time to make
this change.

  reply	other threads:[~2006-05-04  1:36 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     ` [PATCH] symlink nesting level change Al Viro
2006-05-04  1:35       ` Andrew Morton [this message]
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=20060503183554.87f0218d.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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.