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-next>] [day] [month] [year] [list]
Message-id: <478702C7.80401@shaw.ca>
Date:	Thu, 10 Jan 2008 23:46:47 -0600
From:	Robert Hancock <hancockr@...w.ca>
To:	Alexander <aledin@...l.ru>
Cc:	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

Alexander wrote:
> Hello!
> 
> The problem described at https://bugzilla.redhat.com/show_bug.cgi?id=351451 and
> at http://ubuntuforums.org/showthread.php?t=655772 and supposedly fixed by the
> patch http://kerneltrap.org/mailarchive/linux-kernel/2007/11/25/445094 is still
> there. I have compiled 2.6.24-rc7 kernel and booted my PC with it just to find
> out that my SATA DVD-RW is

There's this patch which was intended to fix it:

http://lkml.org/lkml/2007/11/22/148

which hasn't been merged yet. I see now that there was some further 
discussion from someone saying that didn't fix the problem for them, 
which I wasn't CCed on.. It looks like in their case, libata is 
receiving SGs with DMA addresses above 4GB even though the block layer 
bounce limit is set to 32-bit. That's the mechanism that sata_nv depends 
on to ensure that it gets proper addresses when accessing ATAPI devices 
where it is limited to 32-bit DMA.. Could that be breaking or 
insufficient somehow?

-- 
Robert Hancock      Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@...pamshaw.ca
Home Page: http://www.roberthancock.com/

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ