Re: [CHECKER] Passing wrong size to memcpy/memset

• Next message: Christopher Hoover: "RE: [PATCH] 2.5.68 FUTEX support should be optional"
• Previous message: David Schwartz: "RE: The disappearing sys_call_table export."
• In reply to: Andrew Morton: "Re: [CHECKER] Passing wrong size to memcpy/memset"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Wed, 14 May 2003, Andrew Morton wrote:

> Ken Ashcraft <kash@stanford.edu> wrote:
> >
> > I'm with the Stanford Metacompilation research group and I wrote a checker
> > that looks for places where people use 'sizeof(ptr)' instead of
> > 'sizeof(*ptr)' as the length argument to memcpy/memset.
>
> Well they all look like genuine bugs. It could be that some code is just
> performing overly-paranoid memsets.
>
> I shall submit the below lot unless squeaked at.

No squeaks from me.

Ken, would you please try and Cc: maintainers for future reports?

- James

-- 
James Morris
<jmorris@intercode.com.au>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

• Next message: Christopher Hoover: "RE: [PATCH] 2.5.68 FUTEX support should be optional"
• Previous message: David Schwartz: "RE: The disappearing sys_call_table export."
• In reply to: Andrew Morton: "Re: [CHECKER] Passing wrong size to memcpy/memset"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu May 15 2003 - 22:00:54 EST