From: Valdis.Kletnieks@vt.edu
To: Daniel J Blueman <daniel.blueman@gmail.com>
Cc: 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, 04 Apr 2011 08:48:15 -0400 [thread overview]
Message-ID: <131751.1301921295@localhost> (raw)
In-Reply-To: Your message of "Mon, 04 Apr 2011 11:19:08 +0800." <BANLkTi=Mu70wYSM0sVRWZnQzTPBOvqt6xg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 339 bytes --]
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.
[-- Attachment #2: Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2011-04-04 12:48 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 [this message]
2011-04-04 14:56 ` Daniel J Blueman
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=131751.1301921295@localhost \
--to=valdis.kletnieks@vt.edu \
--cc=daniel.blueman@gmail.com \
--cc=linux-fsdevel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).