linux-kernel - Re: PROBLEM REMAINS: [sata_nv ADMA breaks ATAPI] Crash on accessing DVD-RAM

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]

Date:	Sun, 13 Jan 2008 09:38:45 -0600
From:	James Bottomley <James.Bottomley@...senPartnership.com>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Robert Hancock <hancockr@...w.ca>, Alexander <aledin@...l.ru>,
	linux-kernel@...r.kernel.org, ide <linux-ide@...r.kernel.org>,
	Jeff Garzik <jeff@...zik.org>, Tejun Heo <htejun@...il.com>
Subject: Re: PROBLEM REMAINS: [sata_nv ADMA breaks ATAPI]
	Crash	on	accessing DVD-RAM


On Sun, 2008-01-13 at 13:33 +0000, Alan Cox wrote:
> > Other than that, I guess the solutions would be to just set a 32-bit 
> > mask on the device if either port has an ATAPI device connected (which 
> > is fairly ugly, considering that you could do things like hotplug an 
> > ATAPI device when the other port was in use, for example), or do 
> > something to prevent requests from reaching this point with >4GB 
> > addresses in the first place..
> 
> With 2.6.24 almost released I think that is a must do for the moment and
> since we also have hotplugging fo devices it might be easier for .24 to
> just set a 32bit DMA mask and be done with it, then fix it later.

Yes, I concur for the short term.  The other two possible courses of
action either involve long discussions (the different device one) or
you'll never quite be sure you got all the paths (the GFP_DMA32 one).
At least with this one, you know everything will work.

James


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/