Junfeng Yang wrote:
>
> On Thu, 24 May 2001, Willem Riede wrote:
>
> > Dawson Engler wrote:
> > >
> > > Hi All,
> > >
> > > Enclosed are 103 potential errors where code gets a pointer from a
> > > possibly-failing routine (kmalloc, etc) and dereferences it without
> > >
> > > [BUG] osst_do_scsi
On Thu, 24 May 2001, Willem Riede wrote:
> Dawson Engler wrote:
> >
> > Hi All,
> >
> > Enclosed are 103 potential errors where code gets a pointer from a
> > possibly-failing routine (kmalloc, etc) and dereferences it without
> >
> > [BUG] osst_do_scsi will never return NULL if argument SRpnt is
At 22:09 24/05/2001, Dawson Engler wrote:
[snip]
>-
>[BUG]
>/u2/engler/mc/oses/linux/2.4.4-ac8/fs/ntfs/support.c:244:ntfs_dupuni2map:
>ERROR:NULL:243:244: Passing unknown ptr "buf"! as arg 0 to call "memcpy"!
>set by 'kmalloc':244 [nbytes =
Dawson Engler wrote:
>
> Hi All,
>
> Enclosed are 103 potential errors where code gets a pointer from a
> possibly-failing routine (kmalloc, etc) and dereferences it without
>
> [BUG] osst_do_scsi will never return NULL if argument SRpnt isn't NULL. But they
>copy SRpnt back by *aSRpnt, implies
Hi All,
Enclosed are 103 potential errors where code gets a pointer from a
possibly-failing routine (kmalloc, etc) and dereferences it without
checking. Many follow the simple pattern of alloc-memset:
private = kmalloc(sizeof(*private),GFP_KERNEL);
memset(private, 0, sizeof(stru
5 matches
Mail list logo