[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20110704165137.1332c44f@maggie>
Date: Mon, 4 Jul 2011 16:51:37 +0200
From: Michael Büsch <m@...s.ch>
To: Eric Dumazet <eric.dumazet@...il.com>
Cc: Alexey Zaytsev <alexey.zaytsev@...il.com>,
Andrew Morton <akpm@...ux-foundation.org>,
netdev@...r.kernel.org, Gary Zambrano <zambrano@...adcom.com>,
bugme-daemon@...zilla.kernel.org,
"David S. Miller" <davem@...emloft.net>,
Pekka Pietikainen <pp@...oulu.fi>,
Florian Schirmer <jolt@...box.org>,
Felix Fietkau <nbd@...nwrt.org>, Michael Buesch <mb@...sch.de>
Subject: Re: [Bugme-new] [Bug 38102] New: BUG kmalloc-2048: Poison
overwritten
On Mon, 04 Jul 2011 16:45:05 +0200
Eric Dumazet <eric.dumazet@...il.com> wrote:
> Le lundi 04 juillet 2011 à 16:31 +0200, Michael Büsch a écrit :
> > On Mon, 04 Jul 2011 16:00:49 +0200
> > Eric Dumazet <eric.dumazet@...il.com> wrote:
> > > > And an other question. Why so we have the logic to work-around the 1Gb
> > > > DMA limit instead of just setting the dma mask?
> > >
> > > Your problem is in RX side : NIC actually writes to a buffer that is
> > > supposedly not its property.
> >
> > The problem is on both sides, because some Linux architectures simply
> > do not support any DMA mask less than 32. This applied to i386 (IA32) last
> > time I looked.
> > The b44 DMA engine can only address 30-bits.
>
>
> Michael, traces provided by Alexey are in the RX path.
>
> NIC does a DMA (Receives an UDP frame) into a 2048 bytes buffers that
> was freed.
Yeah sure. That's obvious from the logs.
By "the problem" I meant "the 30bit limitation".
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists