Re: Kernel code analysis (was Re: "movb" for spin-unlock (was Re:namei() query))

From: Jeff Garzik (jgarzik@mandrakesoft.com)
Date: Sat Apr 22 2000 - 12:17:21 EST


Tigran Aivazian wrote:
> On Sat, 22 Apr 2000, Jeff Garzik wrote:
> > It is too much to ask "kernel-lint" to puzzle through page cache flag
> > arcana for example, but I can think of a ton of simple things that a
> > kernel-lint tool could scan for that would be useful..
> > [...]
> > It's still a tall order to handle simple stuff like this..

> indeed a tall order.

I just remembered that Antlr, successor to PCCTS, takes regex-like code
as input, and allows you to walk/parse the semantic tree using
regex-like constructs. Its power makes writing a kernel-lint much
easier. But then, that requires fleshing out Antlr's current C grammar
before any useful tree parsing can be done. :)

> But what is more simple is perhaps to put these rules
> in a text file Documentation/CodingRules and let humans regularly go
> through the file and tidy/fix kernel code up if they have time.

Not a bad idea

> which are not bugs like on your list, but are there to maintain coherent
> and uniform state of the kernel code despite it being written by different
> humans.

FWIW the list of things for which kernel-lint would check includes your
list, as well :)

Regards,

        Jeff

-- 
Jeff Garzik              | Nothing cures insomnia like the
Building 1024            | realization that it's time to get up.
MandrakeSoft, Inc.       |        -- random fortune

- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sun Apr 23 2000 - 21:00:21 EST