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:	Mon, 28 Apr 2008 18:28:13 +0200
From:	Mika Fischer <mika.fischer@...pnet.de>
To:	Gabriel C <nix.or.die@...glemail.com>
CC:	Arjan van de Ven <arjan@...radead.org>,
	Ingo Molnar <mingo@...e.hu>, yhlu.kernel@...il.com,
	Andrew Morton <akpm@...ux-foundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] x86: mtrr cleanup for converting continuous to discrete
   layout v2

Gabriel C schrieb:
>> Ah, so the new X will be able to use the video memory in write-combining
>> mode even if I have an MTRR saying this area is uncachable or write-back?
>>
>> If that is the case, then I agree that this patch is not really needed.

It seems not to be the case, so this is moot anyway :)

> I doubt there will be any usable Xorg release soon.
> And I doubt peoples will run Xorg , mesa , etc master HEAD to have that feature. 
> 
> I think this patch is needed for now but as Ingo said , it should not be default.
> Peoples with these sort problems could boot with some option to enables this workaround.

Well, if it is compiled but inactive by default and can be enabled with
a kernel boot option, this is fine too.

But if it's a compile-time option, I doubt that any distro-kernel would
touch it if it's really dangerous. They're probably more likely to
backport the Xorg stuff if the new Xorg does not get finished in time.

Regards,
 Mika
--
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