From: Eric Farman <farman@linux.ibm.com>
To: David Hildenbrand <david@redhat.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
Janosch Frank <frankja@linux.ibm.com>
Cc: Cornelia Huck <cohuck@redhat.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-s390@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] KVM: s390: Fix potential spectre warnings
Date: Wed, 17 Apr 2019 10:23:20 -0400 [thread overview]
Message-ID: <939b08f5-c1b8-c930-cacf-387be9f09f4a@linux.ibm.com> (raw)
In-Reply-To: <bdea8892-6818-93fa-fa2a-b2bad69a50d1@redhat.com>
On 4/17/19 3:49 AM, David Hildenbrand wrote:
> On 17.04.19 02:54, Eric Farman wrote:
>> Fix some warnings from smatch:
>>
>> arch/s390/kvm/interrupt.c:2310 get_io_adapter() warn: potential spectre issue 'kvm->arch.adapters' [r] (local cap)
>> arch/s390/kvm/interrupt.c:2341 register_io_adapter() warn: potential spectre issue 'dev->kvm->arch.adapters' [w]
>>
>> Signed-off-by: Eric Farman <farman@linux.ibm.com>
>> ---
>> A recent patch from Paolo [1] acted as a reminder (thanks, Christian!)
>> that I had one for the s390 KVM code after some code reviews [2].
>> Let's clean that up.
>>
>> [1] https://patchwork.kernel.org/patch/10895463/
>> [2] https://patchwork.kernel.org/patch/10788565/#22484223
>> ---
>> arch/s390/kvm/interrupt.c | 11 +++++++++--
>> 1 file changed, 9 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/s390/kvm/interrupt.c b/arch/s390/kvm/interrupt.c
>> index 82162867f378..bfd55ad34a3e 100644
>> --- a/arch/s390/kvm/interrupt.c
>> +++ b/arch/s390/kvm/interrupt.c
>> @@ -14,6 +14,7 @@
>> #include <linux/kvm_host.h>
>> #include <linux/hrtimer.h>
>> #include <linux/mmu_context.h>
>> +#include <linux/nospec.h>
>> #include <linux/signal.h>
>> #include <linux/slab.h>
>> #include <linux/bitmap.h>
>> @@ -2307,6 +2308,7 @@ static struct s390_io_adapter *get_io_adapter(struct kvm *kvm, unsigned int id)
>> {
>> if (id >= MAX_S390_IO_ADAPTERS)
>> return NULL;
>> + id = array_index_nospec(id, MAX_S390_IO_ADAPTERS);
>> return kvm->arch.adapters[id];
>
> return kvm->arch.adapters[array_index_nospec(id, MAX_S390_IO_ADAPTERS)];
>
> should exactly fit into a single line if I am not wrong.
Yeah, just. As Paolo pointed out, that's not common usage. Though of
the four other hits I see, only one of them is the same as this
instance, in that "id" is passed as a variable and then we immediately
return with an array entry (even if NULL) rather than doing something
else in that function. So maybe all-in-one-line here is a little cleaner.
>
>> }
>>
>> @@ -2320,8 +2322,13 @@ static int register_io_adapter(struct kvm_device *dev,
>> (void __user *)attr->addr, sizeof(adapter_info)))
>> return -EFAULT;
>>
>> - if ((adapter_info.id >= MAX_S390_IO_ADAPTERS) ||
>> - (dev->kvm->arch.adapters[adapter_info.id] != NULL))
>> + if (adapter_info.id >= MAX_S390_IO_ADAPTERS)
>> + return -EINVAL;
>> +
>> + adapter_info.id = array_index_nospec(adapter_info.id,
>> + MAX_S390_IO_ADAPTERS);
>
> I dislike that we are modifying adapter_info here. Can you use a local
> variable instead?
I guess, but adapter_info is a local variable too. So sanitization this
way seems fine to me. But if you dislike it more than I don't care,
I'll add another local variable. :)
>
>> +
>> + if (dev->kvm->arch.adapters[adapter_info.id] != NULL)
>> return -EINVAL;
>>
>> adapter = kzalloc(sizeof(*adapter), GFP_KERNEL);
>>
>
next prev parent reply other threads:[~2019-04-17 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-17 0:54 [PATCH] KVM: s390: Fix potential spectre warnings Eric Farman
2019-04-17 7:49 ` David Hildenbrand
2019-04-17 13:13 ` Paolo Bonzini
2019-04-17 14:23 ` Eric Farman [this message]
2019-04-17 14:24 ` David Hildenbrand
2019-04-17 13:09 ` Paolo Bonzini
2019-04-17 13:10 ` Christian Borntraeger
2019-04-18 7:19 ` Christian Borntraeger
2019-04-18 8:02 ` Cornelia Huck
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=939b08f5-c1b8-c930-cacf-387be9f09f4a@linux.ibm.com \
--to=farman@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=schwidefsky@de.ibm.com \
/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