summaryrefslogtreecommitdiff
path: root/crypto/ccm.c
diff options
context:
space:
mode:
authorAlex Williamson <alex.williamson@redhat.com>2024-03-01 01:35:40 +0300
committerAlex Williamson <alex.williamson@redhat.com>2024-03-05 02:11:07 +0300
commit5b992412776cdf2ec88b5b5138112e6b36e47995 (patch)
tree0f42d6ffbf689dbac9fcbe555627ab437264ff54 /crypto/ccm.c
parent81617c17bf58f008a57da74b97e60a0bf8e971fd (diff)
downloadlinux-5b992412776cdf2ec88b5b5138112e6b36e47995.tar.xz
Revert "vfio/type1: Unpin zero pages"
This reverts commit 873aefb376bbc0ed1dd2381ea1d6ec88106fdbd4. This was a heinous workaround and it turns out it's been fixed in mm twice since it was introduced. Most recently, commit c8070b787519 ("mm: Don't pin ZERO_PAGE in pin_user_pages()") would have prevented running up the zeropage refcount, but even before that commit 84209e87c696 ("mm/gup: reliable R/O long-term pinning in COW mappings") avoids the vfio use case from pinning the zeropage at all, instead replacing it with exclusive anonymous pages. Remove this now useless overhead. Suggested-by: David Hildenbrand <david@redhat.com> Reviewed-by: David Hildenbrand <david@redhat.com> Reviewed-by: Kevin Tian <kevin.tian@intel.com> Link: https://lore.kernel.org/r/20240229223544.257207-1-alex.williamson@redhat.com Signed-off-by: Alex Williamson <alex.williamson@redhat.com>
Diffstat (limited to 'crypto/ccm.c')
0 files changed, 0 insertions, 0 deletions