mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: Christoph Hellwig <hch@infradead.org>,
	Theodore Tso <tytso@MIT.EDU>, Dave Chinner <david@fromorbit.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [git pull] VFS - the first pile
Date: Wed, 16 Mar 2011 09:18:00 -0400	[thread overview]
Message-ID: <20110316131800.GA12175@infradead.org> (raw)
In-Reply-To: <20110316131502.GS22723@ZenIV.linux.org.uk>

On Wed, Mar 16, 2011 at 01:15:02PM +0000, Al Viro wrote:
> Yes.  See patch upthread (or in for-linus).  There are two parts in that
> test; *both* would actually trigger the b0rkage in the last commit of
> what got merged - the only reason why the first one (long chain) did not
> was that the limit got fixed and -ELOOP was no longer triggered.  Symlink
> to itself did, of course, trigger it - complete with oops.

Yes.  I have a patch to increase the limit tested in 005 and it now
passes fine.


  reply	other threads:[~2011-03-16 13:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 21:32 Al Viro
2011-03-15 22:02 ` Sam Ravnborg
2011-03-15 22:18 ` Al Viro
2011-03-15 22:47   ` Linus Torvalds
2011-03-15 23:02     ` Al Viro
2011-03-16  6:19 ` Dave Chinner
2011-03-16  6:51   ` Al Viro
2011-03-16  7:21     ` Al Viro
2011-03-16 11:46       ` Theodore Tso
2011-03-16 13:07         ` Christoph Hellwig
2011-03-16 13:15           ` Al Viro
2011-03-16 13:18             ` Christoph Hellwig [this message]
2011-03-16 13:05 ` Christoph Hellwig
2011-03-16 13:10   ` Christoph Hellwig

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=20110316131800.GA12175@infradead.org \
    --to=hch@infradead.org \
    --cc=david@fromorbit.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@MIT.EDU \
    --cc=viro@ZenIV.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 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®