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: <1167331040.3281.4363.camel@laptopd505.fenrus.org>
Date:	Thu, 28 Dec 2006 19:37:20 +0100
From:	Arjan van de Ven <arjan@...radead.org>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	linux-kernel <linux-kernel@...r.kernel.org>,
	Marcelo Tosatti <marcelo@...ck.org>
Subject: Re: [PATCH] introduce config option to disable DMA zone on i386

On Thu, 2006-12-28 at 12:34 -0600, Robert Hancock wrote:

Hi,

> > since one gets random corruption if a user gets this wrong, at least
> > make things like floppy and all CONFIG_ISA stuff conflict with this
> > option.... without that your patch feels like a walking time bomb...
> > (and please include all PCI drivers that only can do 24 bit or 28bit
> > or .. non-32bit dma as well)
> 
> That sounds like a bug if this can happen. Drivers should be failing to 
> initialize if they can't set the proper DMA mask, and the DMA API calls 
> should be failing if the requested DMA mask can't be provided.

...but Marcelo's patch doesn't implement anything of that kind....
In addition, many ISA bus drivers do not use the DMA API *at all*
currently. If you want to fix them all up, great! But somehow I doubt
those will get fixed in the next decade.. they've been like this for at
least half a decade or longer :-)

Greetings,
   Arjan van de Ven


-- 
if you want to mail me at work (you don't), use arjan (at) linux.intel.com
Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org

-
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