summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorDavid Hildenbrand <david@redhat.com>2017-11-10 16:18:05 +0100
committerChristian Borntraeger <borntraeger@de.ibm.com>2018-01-16 16:15:16 +0100
commit9696594158ec43d210137c1b93313efde8f7315a (patch)
treeb4f5560a0794b59a90cc2e060651a13f64077072 /crypto
parentLinux 4.15-rc3 (diff)
downloadlinux-9696594158ec43d210137c1b93313efde8f7315a.tar.xz
linux-9696594158ec43d210137c1b93313efde8f7315a.zip
s390x/mm: cleanup gmap_pte_op_walk()
gmap_mprotect_notify() refuses shadow gmaps. Turns out that a) gmap_protect_range() b) gmap_read_table() c) gmap_pte_op_walk() Are never called for gmap shadows. And never should be. This dates back to gmap shadow prototypes where we allowed to call mprotect_notify() on the gmap shadow (to get notified about the prefix pages getting removed). This is avoided by always getting notified about any change on the gmap shadow. The only real function for walking page tables on shadow gmaps is gmap_table_walk(). So, essentially, these functions should never get called and gmap_pte_op_walk() can be cleaned up. Add some checks to callers of gmap_pte_op_walk(). Signed-off-by: David Hildenbrand <david@redhat.com> Message-Id: <20171110151805.7541-1-david@redhat.com> Reviewed-by: Janosch Frank <frankja@linux.vnet.ibm.com> Acked-by: Cornelia Huck <cohuck@redhat.com> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions