Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp512049ybb; Wed, 8 Apr 2020 04:35:34 -0700 (PDT) X-Google-Smtp-Source: APiQypJLMy8jKGAO/7/BYEyl0GgPCot+IpIo1anSNfQysKfGNvX6KoceT6TX3oJRkprRyzRuw6lg X-Received: by 2002:a4a:e495:: with SMTP id s21mr5529354oov.79.1586345734701; Wed, 08 Apr 2020 04:35:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1586345734; cv=none; d=google.com; s=arc-20160816; b=U5UFCWn0wgXRA+y6Tt+tYNQdFLVjW3WNrz6HSaTCRze+ioSgPVyHcoqxnzn6NAdQEC p2G3fwFAZcjt905Scd8aIl9t6oMbiW2/7RaoDJeyiNzoXZAnB+B4+aP5scMqiHtD40KP /dB5he4a4NGONecKS+MnKZvm2GAoX68PX/SnaKz0bVt3naOPDnXmg03lsSDn3QqvzBlU I9XZe01NWf/ZDp8juOuhHQR/xMTSiZebUnHghoGbYo5QO1OfDxfYbb22q9YxNcqVoKfG H6WXk3BHybazqjdOV78amtUwaWEWGMX7rCjzMq1mfssSTujKlfqQ3jjHkvNFVhpJAapC 6ejA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=iMpv1Tcf8msq6CIz6hAZaaOwWt8dkcRjoWBRfrYNwKk=; b=mtFgX2WiAKVXfivR3JdlKYIXhWS2bn34QZyFO9hlBtDJq4k6JQXNr3fcEr0SwpFSJ1 cbDYqsBSrD/9m3BTn4HZi2ZbPFicm5CtpfeV8rN4lTA+hX2cSZpnPsaWRIEA6TkvTVKT t5TYsIVdZxnUAFjoEF0KCgjeeZ5B9AxJqPKFBxpcgsLjzV6eNnT7AOy+nR5WY+rmWA1O 1aNzrFCYDHy/FbLVoD/y9wGlHeAQkiuYPnicITQbv93HQSKRDsU0IIDhfHgAxrsexqAu Y8zjXh9PpbhWzRlaphrPOYC4yXsEVf6UsoJ5QmcCVy1Vc+7uVM2ZperMdKhN3e2GJqSk MjdQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=RoRVKKv8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l62si808765oih.269.2020.04.08.04.35.20; Wed, 08 Apr 2020 04:35:34 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=RoRVKKv8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728497AbgDHLeC (ORCPT + 99 others); Wed, 8 Apr 2020 07:34:02 -0400 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:54358 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1727902AbgDHLeC (ORCPT ); Wed, 8 Apr 2020 07:34:02 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1586345641; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=iMpv1Tcf8msq6CIz6hAZaaOwWt8dkcRjoWBRfrYNwKk=; b=RoRVKKv8OqqSmOdsNBjN+SXCfrC6dR9pT5+lcHua/Ex+qQDyNWTC0wvqN/+IE349BXb7rJ DCBWeZFn9iUKNIQDUzuUtaAMAA6z9vlh4Ms9L0viXFQDWQe+SJ8B+CXWwQ2YaPz53qEI2N eXIJPskYhxi9bTFUGZ8VFpj3Vk0JCfc= Received: from mail-wr1-f70.google.com (mail-wr1-f70.google.com [209.85.221.70]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-50-LJQTftwPM5KjlQlkob7pvg-1; Wed, 08 Apr 2020 07:33:59 -0400 X-MC-Unique: LJQTftwPM5KjlQlkob7pvg-1 Received: by mail-wr1-f70.google.com with SMTP id o10so3805931wrj.7 for ; Wed, 08 Apr 2020 04:33:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=iMpv1Tcf8msq6CIz6hAZaaOwWt8dkcRjoWBRfrYNwKk=; b=DKmvBigkuLlNTY9IiGSUMqteaEQvjm73c8KR3NGQarPZKzDS0MKWab3Wv0VBu2tZsp 7xp3ldWCPKlBsqQ6ghs8ufH+0wi6DRsqgnrsIzVUr0+G4ckinUMemGKlRcVWJ7Zptz4B tkno2xTtzqHZitf3TAz4xQLP7IZW4XcI+ZmNqAMw3qogO7F0CTV5Bes5xFUSya/ngVxW ckYvPWoR+7DhC3ZsBoDf0dehonJOUG4f8vjqHMaakMULXVsypeTLEPoA36hK6GyKdNbv LO7fQ2BK7yiEKerCxXYlj/8gZvQlvAIM9I8Ta66yYSoNibvdFfZjaMQW2lTJv7lIqZfE YlOg== X-Gm-Message-State: AGi0PuYtRw0kqJfKOLObF6hJGq3hoGlLtbBWkpY39GUgjfbI/cAushlX +H1olVt1dFcfQ0MqZWAePPJ9UeQUCT4G+cLZ34HHkLt+3lEiO22zfSPH3UF/xu5qUP9BiDrmpYu WNZegaCfPw85wRo7pJDTUS74L X-Received: by 2002:a1c:3281:: with SMTP id y123mr4239285wmy.30.1586345637884; Wed, 08 Apr 2020 04:33:57 -0700 (PDT) X-Received: by 2002:a1c:3281:: with SMTP id y123mr4239265wmy.30.1586345637681; Wed, 08 Apr 2020 04:33:57 -0700 (PDT) Received: from [192.168.10.150] ([93.56.170.5]) by smtp.gmail.com with ESMTPSA id f63sm3148639wma.47.2020.04.08.04.33.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 Apr 2020 04:33:57 -0700 (PDT) Subject: Re: [PATCH 2/2] KVM: s390: Return last valid slot if approx index is out-of-bounds To: Claudio Imbrenda , Sean Christopherson Cc: Christian Borntraeger , Janosch Frank , David Hildenbrand , Cornelia Huck , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, syzbot+d889b59b2bb87d4047a2@syzkaller.appspotmail.com References: <20200408064059.8957-1-sean.j.christopherson@intel.com> <20200408064059.8957-3-sean.j.christopherson@intel.com> <20200408122138.71493308@p-imbrenda> From: Paolo Bonzini Message-ID: <40b325c7-ca24-3513-b2fa-1e9397c9e353@redhat.com> Date: Wed, 8 Apr 2020 13:33:52 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: <20200408122138.71493308@p-imbrenda> Content-Type: text/plain; charset=windows-1252 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/04/20 12:21, Claudio Imbrenda wrote: > on s390 memory always starts at 0; you can't even boot a system missing > the first pages of physical memory, so this means this situation would > never happen in practice. > > of course, a malicious userspace program could create an (unbootable) VM > and trigger this bug, so the patch itself makes sense. > > Reviewed-by: Claudio Imbrenda What about using KVM just for isolation and not just to run a full-blown OS (that is, you might even only have the guest run in problem state)? Would that be feasible on s390? Thanks, Paolo