netdev
[Top] [All Lists]

Re: [PATCH] bio_uncopy_user mem leak

To: Andrew Morton <akpm@xxxxxxxx>
Subject: Re: [PATCH] bio_uncopy_user mem leak
From: sandr8 <sandr8@xxxxxxxxxxxx>
Date: Fri, 20 Aug 2004 22:28:34 +0200
Cc: Con Kolivas <kernel@xxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, kernel@xxxxxxxxxx, lartc@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
In-reply-to: <20040819233155.68c1411e.akpm@xxxxxxxx>
References: <1092909598.8364.5.camel@localhost> <412489E5.7000806@xxxxxxxxxxx> <1092923494.12138.1667.camel@xxxxxxxxxxxxx> <20040819195521.GC12363@xxxxxxxxxxxxxxxxx> <41256DC9.7070500@xxxxxxxxxxx> <20040819233155.68c1411e.akpm@xxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)
Andrew Morton wrote:

Con Kolivas <kernel@xxxxxxxxxxx> wrote:

Uh, I guess that depends on how rested Linus feels when he returns.  I
think there's a fairly significant networking fix too.  As I said: we'll see

is that the one related to the qdisc private data alignment? if not, that one would be a urgent one too imho... i got many oops from the ext3 commit and this because all of the schedulers in the 2.6.8 and 2.6.8.1 traffic control suite are accessing data at slightly wrong positions. this because if any discipline different from pfifo fast is used, the kmalloc()ed memory is aligned in the old way, but then it is used in the new one. the results could be catastrophic whenever the accessed data is a pointer and the memory referenced is written to. :-\

Alessandro Salvatori

<Prev in Thread] Current Thread [Next in Thread>
  • Re: [PATCH] bio_uncopy_user mem leak, sandr8 <=