| 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
| ||
|
Message-ID: <CAE9FiQVc=knLngJ9=oAi9NP4AQzu5hWGh_mkxsB2TqD_posL8g@mail.gmail.com> Date: Mon, 9 Dec 2013 12:44:58 -0800 From: Yinghai Lu <yinghai@...nel.org> To: Bjorn Helgaas <bhelgaas@...gle.com> Cc: Joseph Salisbury <joseph.salisbury@...onical.com>, "linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "stable@...r.kernel.org" <stable@...r.kernel.org> Subject: Re: [PATCH 2/2] PCI: Only enable realloc auto when root bus has 64bit mmio On Mon, Dec 9, 2013 at 12:20 PM, Bjorn Helgaas <bhelgaas@...gle.com> wrote: > Yes, I agree. I didn't say it would be simple. The quick fix would > be easy for now, but adding nonsensical code makes our lives harder > long into the future. If the old kernel is working, and user update kernel then we should not request them to append "pci=realloc=off" for booting. other user that would have "pci=realloc=on" works, they could always keep that. For now, we just reduce auto enable scope, as very beginning we are doing that esp for SRIOV..., and now SRIOV would require huge range esp when num_VF could be 64. we are easy to hit the case that realloc code mess up the bios allocation when there is not above 4G 64bit mmio. 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