Re: [CHECKER] 120 potential dereference to invalid pointers errors forlinux 2.4.1

2001-03-19 Thread Andreas Dilger
Jeff Garzic writes: > > [BUG] init_etherdev could return NULL > > /u2/acc/oses/linux/2.4.1/drivers/net/3c515.c:604:corkscrew_found_device: >ERROR:NULL:603:604: Using unknown ptr "dev" illegally! set by 'init_etherdev':603 > > > > Start ---> > > dev = init_etherdev(dev, sizeof(struct cork

Re: [CHECKER] 120 potential dereference to invalid pointers errors forlinux 2.4.1

2001-03-18 Thread Keith Owens
On Sun, 18 Mar 2001 06:29:50 -0500, Jeff Garzik <[EMAIL PROTECTED]> wrote: >Junfeng Yang wrote: >> Start ---> >> busy = kmalloc(sizeof(erase_busy_t), GFP_KERNEL); >> Error ---> > >This sizeof() construct may be a special case for your checker, but it's >a common one for the kernel...

Re: [CHECKER] 120 potential dereference to invalid pointers errors forlinux 2.4.1

2001-03-18 Thread Jeff Garzik
Junfeng Yang wrote: > [BUG] dev_alloc_skb can return NULL > /u2/acc/oses/linux/2.4.1/drivers/net/3c505.c:619:receive_packet: ERROR:NULL:598:619: >Using NULL ptr "skb" illegally! set by 'dev_alloc_skb':598 Fixed. > [BUG] init_etherdev could return NULL > /u2/acc/oses/linux/2.4.1/drivers/net/3c5

[CHECKER] 120 potential dereference to invalid pointers errors forlinux 2.4.1

2001-03-17 Thread Junfeng Yang
Hi, This checker warns when the pointer returned by a "plausibly" failing routine is not checked before being used. It automatically builds up the list of failing routines by examining all callsites. If a function's returned pointer is checked at more than one callsite, the checker ensures it i