linux-kernel - Re: [patch] ioremap sanity check to catch mapping requests exceeding the BAR sizes

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:	Sat, 27 Sep 2008 17:25:46 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Suresh Siddha <suresh.b.siddha@...el.com>,
	jbarnes@...tuousgeek.org, mingo@...e.hu, tglx@...utronix.de,
	hpa@...or.com, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, arjan@...ux.intel.com,
	linux-kernel@...r.kernel.org
Subject: Re: [patch] ioremap sanity check to catch mapping requests
 exceeding the BAR sizes

On Sat, 27 Sep 2008 07:43:55 -0700
Jeremy Fitzhardinge <jeremy@...p.org> wrote:

> Alan Cox wrote:
> >> Any attempt to use ioremap on memory is a bug, so you should warn about
> >> that too.
> >>     
> >
> > We use it to ioremap things like the BIOS...
> 
> Yeah, that's fine.  I mean using ioremap on system memory is a bug.

On system memory mapped by the kernel which I assume is what you mean -
the BIOS is often shadowed system memory and we have platforms where
memory pages not mapped into or managed the OS are ioremap() targets.

That however is getting pedantic - I just didn't want anyone to overdo
the sanity checks

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