linux-kernel - Re: Re: ioports 0x100-0x3af and iomem 0xd000-0xdffff, 0xa0000000-0xa0ffffff -- safe to use on x86 for pcmcia?

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] [day] [month] [year] [list]

Message-ID: <20091128164819.GB9797@isilmar.linta.de>
Date:	Sat, 28 Nov 2009 17:48:19 +0100
From:	Dominik Brodowski <linux@...inikbrodowski.net>
To:	Komuro <komurojun-mbn@...ty.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>, x86@...nel.org,
	linux-pcmcia@...ts.infradead.org, linux-kernel@...r.kernel.org
Cc:	Peter Stuge <peter@...ge.se>
Subject: Re: Re: ioports 0x100-0x3af and iomem 0xd000-0xdffff, 0xa0000000-0xa0ffffff -- safe to use on x86 for pcmcia?

Hey,

On Wed, Nov 25, 2009 at 08:56:50PM +0900, Komuro wrote:
> > Do you think it would be safe to enable these areas by (kernel) default on
> > x86? Of course, other entries in /proc/io{mem,ports} would be honoured, there
> > would be a boot option to disable this feature, and some tests are run on the
> > iomem and ioport resource areas.
> 
> The problem you have is that you change the ordering.
> 
> If you load the ne2k ISA driver before pcmcia (as occurs now because of
> it being done from user space) the resources get claimed first. If you do
> it the other way around and test then merely reading an I/O register
> mapped to an NE2K or most NE2K clones crashes the machine.

... and even adding a late_initcall() has its problems.

> Are there any modern systems where the PCI based autoconfig is
> insufficient, or is this just ancient stuff  ?

I'm not familiar with embedded stuff, but usually PCI-based autoconfig
should be sufficient nowadays. Therefore, the only workable way seems to be
an optional module parameter

rsrc_nonstatic.include_io=0x100,0x3af,0x3e0,0x4ff,0x800,0x820,0xc00,0xcf7,0xa00,0xaff
rsrc_nonstatic.include_mem=0xc0000,0xfffff,0xa0000000,0xa0ffffff,0x60000000,0x60ffffff

or something like that. Thanks for the input!

Best,
	Dominik
--
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/