Re: [CHECKER] 37 stack variables >= 1K in 2.4.17

From: Alexander Viro (
Date: Thu Jun 13 2002 - 12:53:51 EST

On Thu, 13 Jun 2002, Daniel Phillips wrote:

> > I mean that due to the loop (link_path_walk->do_follow_link->foofs_follow_link
> > ->vfs_follow_link->link_path_walk) you will get infinite maximal depth
> > for everything that can be called by any of these functions. And that's
> > a _lot_ of stuff.
> Then at the point of recursion a dynamic check for stack space is
> needed, and [checker]'s role would be to determine the deepest static
> depth, to plug into the stack check. If we want to be sure about
> stack integrity there isn't any way around this.

Wrong. Check for stack _space_ will mean that maximal depth of nested
symlinks depends on syscall. Definitely not what you want to see.
There is a static limit (no more than 5 nested), but it must be
explicitly known to checker - deducing it from code is easy for a
human, but hopeless for anything automatic.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

This archive was generated by hypermail 2b29 : Sat Jun 15 2002 - 22:00:29 EST