On Tue, 5 Apr 2005 17:37:24 +1000
Stephen Rothwell <[EMAIL PROTECTED]> wrote:
> On Mon, 4 Apr 2005 22:44:09 -0700 "David S. Miller" <[EMAIL PROTECTED]> wrote:
> >
> > I have no idea how a bug like this lasted so long.
>
> Probably because very few programs pass sigevents into the kernel ...
On Mon, 4 Apr 2005 22:44:09 -0700 "David S. Miller" <[EMAIL PROTECTED]> wrote:
>
> I have no idea how a bug like this lasted so long.
Probably because very few programs pass sigevents into the kernel ...
> - memset(, 0, sizeof(*event));
> + memset(event, 0, sizeof(*event));
Blush :-)
On Mon, 4 Apr 2005 22:44:09 -0700 David S. Miller [EMAIL PROTECTED] wrote:
I have no idea how a bug like this lasted so long.
Probably because very few programs pass sigevents into the kernel ...
- memset(event, 0, sizeof(*event));
+ memset(event, 0, sizeof(*event));
Blush :-)
--
On Tue, 5 Apr 2005 17:37:24 +1000
Stephen Rothwell [EMAIL PROTECTED] wrote:
On Mon, 4 Apr 2005 22:44:09 -0700 David S. Miller [EMAIL PROTECTED] wrote:
I have no idea how a bug like this lasted so long.
Probably because very few programs pass sigevents into the kernel ...
Perhaps, but
I have no idea how a bug like this lasted so long.
Anyways, obvious memset()'ing of incorrect pointer.
Please apply, thanks.
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
= kernel/compat.c 1.46 vs edited =
--- 1.46/kernel/compat.c2005-03-13 15:29:47 -08:00
+++
I have no idea how a bug like this lasted so long.
Anyways, obvious memset()'ing of incorrect pointer.
Please apply, thanks.
Signed-off-by: David S. Miller [EMAIL PROTECTED]
= kernel/compat.c 1.46 vs edited =
--- 1.46/kernel/compat.c2005-03-13 15:29:47 -08:00
+++
6 matches
Mail list logo