diff options
author | Linus Torvalds <torvalds@linux-foundation.org> | 2015-10-22 06:32:48 +0900 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2015-10-22 06:32:48 +0900 |
commit | 8a70dd2669200ce83255ed8c5ebef7e59f9e8707 (patch) | |
tree | 7bcac17bcd7004c54f762a018e6dc749ea79b28c /mm/truncate.c | |
parent | 7f67786330ba500ebd7c62ff52b5f7cc6336358f (diff) | |
parent | ba2374fd2bf379f933773811fdb06cb6a5445f41 (diff) |
Merge tag 'for-linus-20151021' of git://git.infradead.org/intel-iommu
Pull intel-iommu bugfix from David Woodhouse:
"This contains a single fix, for when the IOMMU API is used to overlay
an existing mapping comprised of 4KiB pages, with a mapping that can
use superpages.
For the *first* superpage in the new mapping, we were correctly¹
freeing the old bottom-level page table page and clearing the link to
it, before installing the superpage. For subsequent superpages,
however, we weren't. This causes a memory leak, and a warning about
setting a PTE which is already set.
¹ Well, not *entirely* correctly. We just free the page table pages
right there and then, which is wrong. In fact they should only be
freed *after* the IOTLB is flushed so we know the hardware will no
longer be looking at them.... and in fact I note that the IOTLB
flush is completely missing from the intel_iommu_map() code path,
although it needs to be there if it's permitted to overwrite
existing mappings.
Fixing those is somewhat more intrusive though, and will probably
need to wait for 4.4 at this point"
* tag 'for-linus-20151021' of git://git.infradead.org/intel-iommu:
iommu/vt-d: fix range computation when making room for large pages
Diffstat (limited to 'mm/truncate.c')
0 files changed, 0 insertions, 0 deletions