From: Janosch Frank <frankja@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>
Subject: Re: [PATCH v1 5/5] KVM: s390: vsie: gmap_table_walk() simplifications
Date: Fri, 3 Apr 2020 15:03:04 +0200 [thread overview]
Message-ID: <99c824d1-88ca-c98d-c4e9-75a97c2a8a7b@linux.ibm.com> (raw)
In-Reply-To: <20200402184819.34215-6-david@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 1387 bytes --]
On 4/2/20 8:48 PM, David Hildenbrand wrote:
> Let's use asce_type where applicable. Also, simplify our sanity check for
> valid table levels and convert it into a WARN_ON_ONCE(). Check if we even
> have a valid gmap shadow as the very first step.
>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
> arch/s390/mm/gmap.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/arch/s390/mm/gmap.c b/arch/s390/mm/gmap.c
> index fd32ab566f57..3c801dae7988 100644
> --- a/arch/s390/mm/gmap.c
> +++ b/arch/s390/mm/gmap.c
> @@ -790,17 +790,18 @@ static inline unsigned long *gmap_table_walk(struct gmap *gmap,
> const int asce_type = gmap->asce & _ASCE_TYPE_MASK;
> unsigned long *table;
>
> - if ((gmap->asce & _ASCE_TYPE_MASK) + 4 < (level * 4))
> - return NULL;
> if (gmap_is_shadow(gmap) && gmap->removed)
> return NULL;
>
> + if (WARN_ON_ONCE(level > (asce_type >> 2) + 1))
> + return NULL;
> +
> if (WARN_ON_ONCE(asce_type != _ASCE_TYPE_REGION1) &&
> gaddr & (-1UL << (31 + (asce_type >> 2) * 11)))
> return NULL;
>
> table = gmap->table;
We could also initialize this variable at the top, no?
> - switch (gmap->asce & _ASCE_TYPE_MASK) {
> + switch (asce_type) {
> case _ASCE_TYPE_REGION1:
> table += (gaddr & _REGION1_INDEX) >> _REGION1_SHIFT;
> if (level == 4)
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-04-03 13:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-02 18:48 [PATCH v1 0/5] KVM: s390: vsie: fixes and cleanups David Hildenbrand
2020-04-02 18:48 ` [PATCH v1 1/5] KVM: s390: vsie: Fix region 1 ASCE sanity shadow address checks David Hildenbrand
2020-04-03 12:07 ` David Hildenbrand
2020-04-03 13:41 ` Janosch Frank
2020-04-02 18:48 ` [PATCH v1 2/5] KVM: s390: vsie: Fix delivery of addressing exceptions David Hildenbrand
2020-04-06 13:17 ` Christian Borntraeger
2020-04-06 13:22 ` David Hildenbrand
2020-04-06 13:24 ` Christian Borntraeger
2020-04-02 18:48 ` [PATCH v1 3/5] KVM: s390: vsie: Fix possible race when shadowing region 3 tables David Hildenbrand
2020-04-06 13:47 ` Christian Borntraeger
2020-04-02 18:48 ` [PATCH v1 4/5] KVM: s390: vsie: Move conditional reschedule David Hildenbrand
2020-04-02 18:48 ` [PATCH v1 5/5] KVM: s390: vsie: gmap_table_walk() simplifications David Hildenbrand
2020-04-03 13:03 ` Janosch Frank [this message]
2020-04-03 13:09 ` David Hildenbrand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99c824d1-88ca-c98d-c4e9-75a97c2a8a7b@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox