netdev - Re: [PATCH RESEND] atl1: fix 4G memory corruption bug

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20080526150244.165fffdd@osprey.hogchain.net>
Date:	Mon, 26 May 2008 15:02:44 -0500
From:	Jay Cliburn <jacliburn@...lsouth.net>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Alexey Dobriyan <adobriyan@...il.com>, csnook@...hat.com,
	netdev@...r.kernel.org
Subject: Re: [PATCH RESEND] atl1: fix 4G memory corruption bug

On Thu, 22 May 2008 17:20:30 -0400
Jeff Garzik <jeff@...zik.org> wrote:

> Alexey Dobriyan wrote:
> > From: Alexey Dobriyan <adobriyan@...il.com>
> > 
> > When using 4+ GB RAM and SWIOTLB is active, the driver corrupts
> > memory by writing an skb after the relevant DMA page has been
> > unmapped.  Although this doesn't happen when *not* using bounce
> > buffers, clearing the pointer to the DMA page after unmapping
> > it fixes the problem.
> > 
> > http://marc.info/?t=120861317000005&r=2&w=2
> > 
> > 
> > Signed-off-by: Alexey Dobriyan <adobriyan@...il.com>
> > Signed-off-by: Jay Cliburn <jacliburn@...lsouth.net>
> > ---
> > 
> >  drivers/net/atlx/atl1.c |    1 +
> >  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> applied

Hi Jeff,

Where did you apply this patch?  I don't exclude the possibility that I
goofed when I fetched them, but I can't find it in any of the following
branches of your netdev tree.

	master
	net-2.6
	net-next
	upstream
	upstream-davem
	upstream-next
	upstream-next-davem

Thanks,
Jay
--
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