netdev - Re: atl1 64-bit => 32-bit DMA borkage (reproducible, bisected)

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20080420111453.GA4902@martell.zuzino.mipt.ru>
Date:	Sun, 20 Apr 2008 15:14:53 +0400
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	Jay Cliburn <jacliburn@...lsouth.net>
Cc:	Luca Tettamanti <kronos.it@...il.com>,
	Chris Snook <csnook@...hat.com>, Jeff Garzik <jeff@...zik.org>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
	Christoph Lameter <clameter@....com>, torvalds@...l.org
Subject: Re: atl1 64-bit => 32-bit DMA borkage (reproducible, bisected)

On Sat, Apr 19, 2008 at 09:54:44PM -0500, Jay Cliburn wrote:
> On Sat, 19 Apr 2008 18:45:35 +0400
> Alexey Dobriyan <adobriyan@...il.com> wrote:
> 
> > OK, nailed it.
> > 
> > It's commit 5f08e46b621a769e52a9545a23ab1d5fb2aec1d4 aka "atl1:
> > disable broken 64-bit DMA".
> > 
> > With this commit in tree, I can reproduce either
> > a) kmalloc-2048 corruption after initscripts shutdown eth0
> > 	http://marc.info/?l=linux-kernel&m=120820360221261&w=2
> > 
> > b) or oopses at filp_close() first reported long ago
> > 	(sorry, can't find that email)
> > 
> > c) or hard hang after initscripts shutdown eth0 with even SysRq not
> > working. http://marc.info/?l=linux-kernel&m=120795046008115&w=2
> > 
> > I have two boxes one with atl1, 4G RAM with 2G remapped after 4G
> > boundary, another with r8169 connected with just ethernet cable. NICs
> > agree on 1Gbps speed.
> > 
> > So, it's enough to scp 200 MB git archive and immediately start
> > rebooting sequence for horrors described above to appear. It's not
> > 100% reproducible but more like 90%.
> 
> Do I understand correctly that these failures occur only while the
> network interface is going down?

Yep. During up or running there were no problems with this card.

--
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