linux-kernel - Re: [RFC PATCH 1/1] PCI: skip release and reallocation of io port resources

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:	Wed, 30 Jun 2010 16:59:49 -0700
From:	Ram Pai <linuxram@...ibm.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Ram Pai <linuxram@...ibm.com>, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org, clemens@...isch.de,
	Yinghai Lu <yinghai@...nel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [RFC PATCH 1/1] PCI: skip release and reallocation of io port
	resources

On Wed, Jun 30, 2010 at 04:10:26PM -0700, Linus Torvalds wrote:
> On Wed, Jun 30, 2010 at 2:15 PM, Ram Pai <linuxram@...ibm.com> wrote:
> >       PCI: skip release and reallocation of io port resources
> 
> Gaah. This still looks like just total ad-hoc hackery. The logic for
> it all seems very fragile, just a random case made up from the one
> failing issue. There's no underlying logic or design to it.
> 
> I still think that we should just make people explicitly ask for a
> blank slate if the bios allocations don't work out. 

and interactively allocate resource?

> Rather than trying
> to fix it up automatically, which has been a total rats nest of random
> crud.

Can Yinghai Lu's patch 'pci=try=' be some temporary middle ground till
a more elaborate patch is found?

His suggestion partly meets your suggestion. It does not automatically 
reassign unless the user explicitly asks for it. Hence should not
break any working systems, at the same time can handle system like 
mine.

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