>
> If we keep it 10 times over head, my home computer can load the full linux
> kernel and have some spare for checking.
>
> I am still working on the bytecode loader and linker for merging symbols.
> It need to answer the question:
>
> Which file define which function.
> Which external
If we keep it 10 times over head, my home computer can load the full linux
kernel and have some spare for checking.
I am still working on the bytecode loader and linker for merging symbols.
It need to answer the question:
Which file define which function.
Which external symbol does
On Sun, Feb 11, 2007 at 05:50:15AM +, Al Viro wrote:
>
> I have some stuff in that direction, but it take some resurrecting...
OK, we should talk.
Here is what I have:
Linearize bytecode writer, which produce the binary linearized code.
The uncompress size is about 10 times the i386 .o
On Sat, Feb 10, 2007 at 06:33:25PM +0100, Andi Kleen wrote:
> Interesting. Did you find any kernel bugs with this?
In short, not very useful yet.
The current run of of sparse-0.2-cl2 on git default i386 config
will find about 6 place kernel using allocated memory without NULL
check. But Linus
On Sat, Feb 10, 2007 at 09:17:58PM -0800, Christopher Li wrote:
> e.g. sparse has not way to know some function only get called with interrupt
> disabled (or some lock already hold). So it assume interrupt is still
> enable and generate wrong warnings. Another example is that some helper
>
Christopher Li <[EMAIL PROTECTED]> writes:
>
> Change log in sparse-0.2-cl2:
> - adding pointer signedness fix
> - adding spinlock checking
Interesting. Did you find any kernel bugs with this?
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
On Sat, Feb 10, 2007 at 09:17:58PM -0800, Christopher Li wrote:
e.g. sparse has not way to know some function only get called with interrupt
disabled (or some lock already hold). So it assume interrupt is still
enable and generate wrong warnings. Another example is that some helper
function
On Sat, Feb 10, 2007 at 06:33:25PM +0100, Andi Kleen wrote:
Interesting. Did you find any kernel bugs with this?
In short, not very useful yet.
The current run of of sparse-0.2-cl2 on git default i386 config
will find about 6 place kernel using allocated memory without NULL
check. But Linus
On Sun, Feb 11, 2007 at 05:50:15AM +, Al Viro wrote:
I have some stuff in that direction, but it take some resurrecting...
OK, we should talk.
Here is what I have:
Linearize bytecode writer, which produce the binary linearized code.
The uncompress size is about 10 times the i386 .o file.
Christopher Li [EMAIL PROTECTED] writes:
Change log in sparse-0.2-cl2:
- adding pointer signedness fix
- adding spinlock checking
Interesting. Did you find any kernel bugs with this?
-Andi
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
Temporarily at:
http://userweb.kernel.org/~chrisl/sparse-0.2-cl2
Will appear later at:
http://ftp.kernel.org//pub/linux/kernel/people/chrisl/patches/sparse/sparse-0.2-cl2/
I have been play with sparse to add more Stanford checker style
of checking. The paper is "Checking System Rules
Temporarily at:
http://userweb.kernel.org/~chrisl/sparse-0.2-cl2
Will appear later at:
http://ftp.kernel.org//pub/linux/kernel/people/chrisl/patches/sparse/sparse-0.2-cl2/
I have been play with sparse to add more Stanford checker style
of checking. The paper is Checking System Rules
12 matches
Mail list logo