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: <20090507.113632.210373283.davem@davemloft.net>
Date:	Thu, 07 May 2009 11:36:32 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	dwmw2@...radead.org
Cc:	joerg.roedel@....com, fujita.tomonori@....ntt.co.jp,
	linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
	mingo@...hat.com, airlied@...ux.ie
Subject: Re: IOMMU and graphics cards

From: David Woodhouse <dwmw2@...radead.org>
Date: Thu, 07 May 2009 11:22:01 +0100

> On Thu, 2009-05-07 at 12:01 +0200, Joerg Roedel wrote:
>> > Looks like the DRM code uses the DMA API.
>> 
>> The proprietary drivers make problems so far. For the ATI one I am in
>> contact with the developers to try to fix it. But I can't do anything
>> about the other proprietary driver I am aware of :-(
> 
> I see no harm in "breaking" code which was already broken. If that's the
> only reason we're enabling the graphics workaround, let's turn it off.

Seriously, this is an enormous price to pay just for one bad apple
proprietary driver.

I can't believe the level of concessions some people are suggesting.

Let's not make IOMMU's basically useless by working around one broken
driver.

Proper interfaces for what this driver is trying to do have existed in
the kernel for 10+ years.  There are no excuses, and it's time for
Nvidia to get with the game plan.
--
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