linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel J Blueman <daniel.blueman@gmail.com>
To: Valdis.Kletnieks@vt.edu, Nick Piggin <npiggin@kernel.dk>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [2.6.39-rc1] LTP hitting max (8) nested links...
Date: Mon, 4 Apr 2011 22:56:11 +0800	[thread overview]
Message-ID: <BANLkTikA8QXXCMPnigP6_cDJNpt2EWMagA@mail.gmail.com> (raw)
In-Reply-To: <131751.1301921295@localhost>

On 4 April 2011 20:48,  <Valdis.Kletnieks@vt.edu> wrote:
> On Mon, 04 Apr 2011 11:19:08 +0800, Daniel J Blueman said:
>
>> Re-reading everything, nested here is actually recursively nested, not
>> consecutively nested, so will never succeed, so we expect this from
>> the LTP test.
>
> We expect the LTP test to be handed an error, I suspect.  The LTP test
> probably shouldn't be able to provoke a BUG_ON.

In fact, since userspace does correctly return ELOOP [1], and I can't
reproduce it with 2.6.37, it does looks like a race in the RCU VFS
lookup, so adding Nick in the loop.

--- [1]

$ ln -s foo bar && ln -s bar foo
$ strace -e mkdir mkdir foo/a
mkdir("foo/a", 0777)                    = -1 ELOOP (Too many levels of
symbolic links)
mkdir: cannot create directory `foo/a': Too many levels of symbolic links
-- 
Daniel J Blueman

      reply	other threads:[~2011-04-04 14:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  3:13 [2.6.39-rc1] LTP hitting max (8) nested links Daniel J Blueman
2011-04-04  3:19 ` Daniel J Blueman
2011-04-04 12:48   ` Valdis.Kletnieks
2011-04-04 14:56     ` Daniel J Blueman [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=BANLkTikA8QXXCMPnigP6_cDJNpt2EWMagA@mail.gmail.com \
    --to=daniel.blueman@gmail.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@kernel.dk \
    /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;
as well as URLs for NNTP newsgroup(s).