summaryrefslogtreecommitdiffstats
path: root/include/linux/stackprotector.h
diff options
context:
space:
mode:
authorDavid Woodhouse <dwmw2@infradead.org>2016-09-12 10:49:11 +0800
committerDavid Woodhouse <dwmw2@infradead.org>2016-11-19 09:42:35 -0800
commit910170442944e1f8674fd5ddbeeb8ccd1877ea98 (patch)
tree0d3b866ec62df63888e0c747e724ccd6f4b6efdf /include/linux/stackprotector.h
parent1c387188c60f53b338c20eee32db055dfe022a9b (diff)
downloadop-kernel-dev-910170442944e1f8674fd5ddbeeb8ccd1877ea98.zip
op-kernel-dev-910170442944e1f8674fd5ddbeeb8ccd1877ea98.tar.gz
iommu/vt-d: Fix PASID table allocation
Somehow I ended up with an off-by-three error in calculating the size of the PASID and PASID State tables, which triggers allocations failures as those tables unfortunately have to be physically contiguous. In fact, even the *correct* maximum size of 8MiB is problematic and is wont to lead to allocation failures. Since I have extracted a promise that this *will* be fixed in hardware, I'm happy to limit it on the current hardware to a maximum of 0x20000 PASIDs, which gives us 1MiB tables — still not ideal, but better than before. Reported by Mika Kuoppala <mika.kuoppala@linux.intel.com> and also by Xunlei Pang <xlpang@redhat.com> who submitted a simpler patch to fix only the allocation (and not the free) to the "correct" limit... which was still problematic. Signed-off-by: David Woodhouse <dwmw2@infradead.org> Cc: stable@vger.kernel.org
Diffstat (limited to 'include/linux/stackprotector.h')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud