linux-kernel - Re: [2.6.39-rc1] LTP hitting max (8) nested links...

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 4 Apr 2011 11:19:08 +0800
From:	Daniel J Blueman <daniel.blueman@...il.com>
To:	Linux Kernel <linux-kernel@...r.kernel.org>,
	linux-fsdevel@...r.kernel.org
Subject: Re: [2.6.39-rc1] LTP hitting max (8) nested links...

On 4 April 2011 11:13, Daniel J Blueman <daniel.blueman@...il.com> wrote:
> When a test from the Linux Test Project [1] with 2.6.39-rc1 while
> trying to reproduce another fileystem issue, I quickly hit the 8
> nested link limit [2]:
> BUG_ON(nd->depth >= MAX_NESTED_LINKS)
>
> It seems a mutually exclusive condition to have such a technical limit
> in-kernel and a test in LTP which triggers that, unless there is a bug
> of course.
>
> Though 8 seems reasonable in most cases, it looks like an artificial
> and not technical limit which feels more broken - perhaps a WARN_ON or
> higher limit before BUG() is called makes sense?

Re-reading everything, nested here is actually recursively nested, not
consecutively nested, so will never succeed, so we expect this from
the LTP test.
-- 
Daniel J Blueman
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/