linux-kernel - Re: [PATCH 28/36] PCI: Add pci_bus_extend/shrink

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, 16 Mar 2012 15:04:19 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>,
	Tony Luck <tony.luck@...el.com>,
	David Miller <davem@...emloft.net>, x86 <x86@...nel.org>,
	Dominik Brodowski <linux@...inikbrodowski.net>,
	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arch@...r.kernel.org
Subject: Re: [PATCH 28/36] PCI: Add pci_bus_extend/shrink_top()

On Fri, Mar 16, 2012 at 2:42 PM, Yinghai Lu <yinghai@...nel.org> wrote:
> On Fri, Mar 16, 2012 at 12:36 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
>> I've objected to this before on the grounds that it's not safe to
>> update res->end because res is already linked into the resource tree,
>> but I just noticed another problem.
>>
>> Tree updates are protected by resource_lock, but we don't hold that
>> here.  I'm sure you "know" that this update can't race with any other
>> conflicting resource operations, but its safety certainly is not
>> obvious from the patch.
>>
>> I think a better implementation would be to add something like
>> "resource_extend()" that could live in kernel/resource.c so it could
>> do the appropriate locking and checking.  Such an interface could also
>> be independent of the resource type, which may be useful when doing
>> mem/io resource reassignment.
>
> Thanks for point it out.
>
> Let me thinking about it.
>
>>
>> This patch is already in Jesse's linux-next branch (commit
>> c901d4c0407), so I'm leaving it up to you and Jesse to figure out
>> what, if anything, to do about this.
>
> No, this patch is one in busn_alloc patchset. Jesse did NOT pick that
> patchset yet.

Ah, right you are.  I guess I still had your for-pci-root-bus-hotplug
branch checked out when this occurred to me.  Sorry for the confusion.

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