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

From: Alexander Viro (
Date: Thu Jun 13 2002 - 13:26:54 EST

On 13 Jun 2002, Andi Kleen wrote:

> Alexander Viro <> writes:
> >
> > 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.
> Surely an analysis pass can detect recursive function chains and flag them
> (e.g. the global IPA alias analysis pass in open64 does this)

Ugh... OK, let me try again:

One bit of apriory information needed to get anything interesting from
this analysis: there is a set of mutually recursive functions (see above)
and there is a limit (5) on the depth of recursion in that loop.

It has to be known to checker. Explicitly, since
        a) automatically deducing it is not realistic
        b) cutting off the stuff behind that loop will cut off a _lot_ of
things - both in filesystems and in VFS (and in block layer, while we are
at it).

I'm not saying that checker can't be used for that analysis - it can, but
naive approach (find recursive stuff and cut it off) will not be too
interesting. One of the main stumbling blocks - see above. With explicit
knowledge of that one the thing will be definitely very interesting - no
arguments here.

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