Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp5222538yba; Mon, 13 May 2019 07:23:34 -0700 (PDT) X-Google-Smtp-Source: APXvYqwD00jRCx56jCf+W2Xsn29PZT69iKFpnZIRqNRzccCKfyd1v4ALgP1bE6DfCsJD5NAaN4tt X-Received: by 2002:a17:902:bf44:: with SMTP id u4mr30575759pls.171.1557757414170; Mon, 13 May 2019 07:23:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557757414; cv=none; d=google.com; s=arc-20160816; b=U6KDitxtxga2WwwyZ/E3QldKexwFb4bbyzBQFojXioISfmKTURBt1/PPGId8lEv4a+ Ts4RRy8g2TI9P4jk49o3+u2/5NZZK8Mp1ko/NAl3hoZB7+1zlT8OubPiOOwyEz5/++CE EwgjFbRnVgze8x5qMg4kF46066+Y+56E4Sq6gXkQGjudyZGE7gFqbYrYIoEgaMNxHFfc A3PQ6qleIhd5gGKjgSPiaA3WJpN01LTqsVbovuACA42lXtCBL5lrshQBYxp7Ms7VW/NC 9oZUJRrRkEOFB4Kh+d+OVCDyNEAxNCfntMPj7GpEUzx/giRWPK8cq6ja2rjJWdAWiL98 fxNA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=uPgBr/VCEQjSCJdwAHli9TXLhbkEbm5qKDxB3hc1cEg=; b=Wlm6EIq1PyUrefxBJxdzmBWzr1c2IZfvmgWuayKTpfrLUqcIpCmdcyxoxAygsvLoTx ZWSg4stty9Lu6XNu+R8wcqP5e3W7OpME4dbhA/mNRhuf70M4BN9SeREaDKMeR+6f2Gkt 0hhEcHAo6/9Ja17bwNCkpmSFmNbU0Tr1eLCJ4GYlN3XU4llpRXe1blUkKwIGr+NXBDT4 6AWqCkgRcSeW1o8S2YvfSw/TgNBOv9fubje+rYZAb6BsbqJmBEvvbiopWv0CJMKyA1fl n11SgujfI/+MyILEgjlLra06BoQM9Uc9Zc+giuj6qrENjUZmzi9od0Rzbi/FI9uJEBcI Fsyw== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (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 v14si18601002pfa.252.2019.05.13.07.23.17; Mon, 13 May 2019 07:23: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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729005AbfEMOKi (ORCPT + 99 others); Mon, 13 May 2019 10:10:38 -0400 Received: from mx1.redhat.com ([209.132.183.28]:53710 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727640AbfEMOKi (ORCPT ); Mon, 13 May 2019 10:10:38 -0400 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 2AD28C02490D; Mon, 13 May 2019 14:10:38 +0000 (UTC) Received: from flask (unknown [10.40.205.238]) by smtp.corp.redhat.com (Postfix) with SMTP id 19B0969293; Mon, 13 May 2019 14:10:35 +0000 (UTC) Received: by flask (sSMTP sendmail emulation); Mon, 13 May 2019 16:10:35 +0200 Date: Mon, 13 May 2019 16:10:35 +0200 From: Radim =?utf-8?B?S3LEjW3DocWZ?= To: Marc Haber Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: Linux in KVM guest segfaults when hosts runs Linux 5.1 Message-ID: <20190513141034.GA13337@flask> References: <20190512115302.GM3835@torres.zugschlus.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190512115302.GM3835@torres.zugschlus.de> X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.32]); Mon, 13 May 2019 14:10:38 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 2019-05-12 13:53+0200, Marc Haber: > since updating my home desktop machine to kernel 5.1.1, KVM guests > started on that machine segfault after booting: [...] > Any idea short of bisecting? It has also been spotted by Borislav and the fix [1] should land in the next kernel update, thanks for the report. --- 1: https://patchwork.kernel.org/patch/10936271/