Received-SPF: pass (google.com: domain of linux-kernel+bounces-146720-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
From: Claudio Imbrenda <imbrenda@linux.ibm.com>
To: linux-s390@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, frankja@linux.ibm.com, nrb@linux.ibm.com,
        nsg@linux.ibm.com, borntraeger@de.ibm.com, hca@linux.ibm.com,
        gerald.schaefer@linux.ibm.com, david@redhat.com
Subject: [PATCH v1 0/2] s390/mm: fix improper use of __storage_key_init_range
Date: Tue, 16 Apr 2024 13:42:18 +0200
Message-ID: <20240416114220.28489-1-imbrenda@linux.ibm.com>
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

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(-)

-- 
2.44.0