On Tue, 2007-07-31 at 00:42 +0400, Alexey Dobriyan wrote:
> On Sun, Jul 29, 2007 at 03:33:20PM +0400, Alexey Dobriyan wrote:
> > I'm currently running random line shuffling test taking, ha-ha, advansys.i
> > as input.
> >
> > Here is first trimmed testcase on which valgrind says stack overflow and
> > sparse segfaults.
> >
> >
> > int a, struct b c);
> > typedef void (elevator_activate_req_fn)(foo *);
> > typedef void (elevator_activate_req_fn)(struct foo *);
> > struct sigaction {
> > static struct lock_class_key __key;
> >
> >
> >
> > So far the joy is spoiled by many infinite loops sparse gets into and
> > automatic testing is still semi-automatic, but stay tuned.
>
> Here is another:
>
> __asm__("l" : "i" (1)
>
> #0 0x080543e4 in mark_assigned (expr=0x1) at evaluate.c:1388
> #1 0x080544ba in evaluate_assign_to (left=0xb749c2cc, type=0x80da040) at evaluate.c:1421
> #2 0x08058556 in evaluate_asm_statement (stmt=0xb7582888) at evaluate.c:3160
> #3 0x08058c63 in evaluate_statement (stmt=0xb7582888) at evaluate.c:3342
> #4 0x08058093 in evaluate_symbol (sym=0xb747d20c) at evaluate.c:3041
> #5 0x080580e9 in evaluate_symbol_list (list=0xb7dac30c) at evaluate.c:3054
> #6 0x080510cf in sparse (filename=0xbf9ff164 "a.c") at lib.c:786
> #7 0x0804bdac in main
Fuzz testing on Sparse seems like an *excellent* idea; thank you for
doing this. Nice finds.
- Josh Triplett
-
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
