linux-kernel - Re: [PATCH 4/4] PCI: pre-allocate additional resources to devices only after successful allocation of essential 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] [day] [month] [year] [list]

Date:	Fri, 4 Mar 2011 10:47:30 -0800
From:	Jesse Barnes <jbarnes@...tuousgeek.org>
To:	Ram Pai <linuxram@...ibm.com>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	clemens@...isch.de, Yinghai Lu <yinghai@...nel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Bjorn Helgaas <bjorn.helgaas@...com>
Subject: Re: [PATCH 4/4] PCI: pre-allocate additional resources to devices
 only after successful allocation of essential resources.

On Mon, 14 Feb 2011 17:43:20 -0800
Ram Pai <linuxram@...ibm.com> wrote:

> Linux tries to pre-allocate minimal resources to hotplug bridges. This
>     works fine as long as there are enough resources  to satisfy all other
>     genuine resource requirements. However if enough resources are not
>     available to satisfy any of these nice-to-have pre-allocations, the
>     resource-allocator reports errors and returns failure.
> 
>     This patch distinguishes between must-have resource from nice-to-have
>     resource.  Any failure to allocate nice-to-have resources are ignored.
> 
>     This behavior can be particularly useful to trigger automatic
>     reallocation when the OS discovers genuine allocation-conflicts
>     or genuine unallocated-requests caused by buggy allocation behavior
>     of the native BIOS/uEFI.
> 
>     https://bugzilla.kernel.org/show_bug.cgi?id=15960 captures the movitation
>     behind the patch. This patch is verified to resolve the above bug.

Ok, applied this series.  Everyone please test thoroughly as resource
changes always seem to bite us.

-- 
Jesse Barnes, Intel Open Source Technology Center
--
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/