linux-kernel - Re: agpgart: when telling user you'll corrupt his data, at least do it at KERN

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:	Fri, 28 Mar 2008 13:51:21 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Pavel Machek <pavel@....cz>, Andi Kleen <andi@...stfloor.org>,
	kernel list <linux-kernel@...r.kernel.org>
Subject: Re: agpgart: when telling user you'll corrupt his data, at least
	do it at KERN_CRIT


* Jiri Kosina <jkosina@...e.cz> wrote:

> On Fri, 28 Mar 2008, Ingo Molnar wrote:
> 
> > > IOMMU off means very bad stuff may happen, like data corruption on 
> > > your hard drives. At least tells users this is serious...
> > ouch. Please at minimum lets turn this into a panic(), but best would be 
> > to trim memory in this case, hm?
> 
> Are you suggesting to panic on all 64bit machines having more than 4G 
> RAM without IOMMU turned on? Why, if swiotlb can still work nicely in 
> such situations?

no, but we should avoid Pavel's disk corruption scenario ;-)

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