| 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
| ||
|
Date: Sun, 12 Feb 2012 16:03:05 -0800 From: Yinghai Lu <yinghai@...nel.org> To: Bjorn Helgaas <bhelgaas@...gle.com> Cc: Jesse Barnes <jbarnes@...tuousgeek.org>, Benjamin Herrenschmidt <benh@...nel.crashing.org>, Tony Luck <tony.luck@...el.com>, Dominik Brodowski <linux@...inikbrodowski.net>, Andrew Morton <akpm@...ux-foundation.org>, Linus Torvalds <torvalds@...ux-foundation.org>, linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org Subject: Re: [PATCH 04/24] PCI: Add busn_res operation functions On Sun, Feb 12, 2012 at 3:51 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote: >> >>> >>> I think it would be better to remove the bus resource from the tree, >>> change its "end," then re-insert it. >> >> how about parent buses that have extended top? > > I don't understand your question. I assume you mean there's a case > where remove/update/reinsert doesn't work, but I don't see why that > would be a problem. Can you show an example? I mean parent busn_res already had several level's children busn_res. and every level may have some siblings. before remove will need to record those resources, to later to put them back. that just increase not necessary complexity. because we already know those resource could be extended safely. Yinghai -- 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/
Powered by blists - more mailing lists