Skip to content

s390/mm: fix improper use of __storage_key_init_range

Claudio Imbrenda linux-s390 lkml 1 version Applied

Status from this message: Applied, thanks!

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest2 patches 2 repliesApplied

Patches in v1 Applied

#Subject and filesSizeRepliesApplied
1/2s390/mm: fix storage key clearing for guest huge pagesarch/s390/mm/gmap.c+1 -10 replies
2/2s390/mm: fix clearing storage keys for huge pagesarch/s390/mm/hugetlbpage.c+1 -10 replies

Reviews trailers per patch

None of the 2 patches has a Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchHeiko Carstens
SeriesR-b
1/2
2/2

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH v1 0/2] s390/mm: fix improper use of __storage_key_init_range

The function __storage_key_init_range() expects the end address to be the first byte outside the range to be initialized. I.e. end - start should be the size of the area to be initialized.

This small series fixes two cases in which the last address in the range was passed as end address. This was still functionally correct, since __storage_key_init_range() will still loop over single pages and correctly clear the given range, but it will be slower than clearing the storage keys for the whole 1M block with a single instruction.

Claudio Imbrenda (2):
s390/mm: fix storage key clearing for guest huge pages s390/mm: fix clearing storage keys for huge pages

 arch/s390/mm/gmap.c        | 2 +-
 arch/s390/mm/hugetlbpage.c | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
Signature · 1 line
2.44.0