From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 07601C83F11 for ; Mon, 28 Aug 2023 15:12:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232021AbjH1PMR (ORCPT ); Mon, 28 Aug 2023 11:12:17 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38450 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232604AbjH1PMJ (ORCPT ); Mon, 28 Aug 2023 11:12:09 -0400 Received: from mail-yb1-xb49.google.com (mail-yb1-xb49.google.com [IPv6:2607:f8b0:4864:20::b49]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 8FF21128 for ; Mon, 28 Aug 2023 08:11:45 -0700 (PDT) Received: by mail-yb1-xb49.google.com with SMTP id 3f1490d57ef6-d7494be34f8so4035981276.2 for ; Mon, 28 Aug 2023 08:11:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1693235505; x=1693840305; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=AgTfuJ+2SR7wHNk0wScsVJOKb9hSrrlOBi0oejIscH4=; b=HfCi+0j4q9UL5mmi0D0c0vIBnMfZ8sVJJnsmxNZYbaR0Ybr1N6e0ZQCYEwymlICUtr bcBrTLBd8dC1xc2OkUA7ey/hHRUI7Z7GMC/EYt/P1CvuYpQTJSKmbsudOLUhxPI3175+ pPXXItH3l1vV5sjno3lvfYnsux22sCmmr9PkW5oI2uYfLWkgtDFIz+VC+S9W2JvrIrby YMpZwKrKd1RsqLlOtdx1jblDVD22DsqrckU+l6Tcfdpc84H/yMwgLc0eHPQl5mU80bH0 GyyGXVxPaav503NLQyiroWVJuXGEBBEO1cGC+soz0rGCa3BEJXNKvQKXcHPlSOSdEM+1 PcSA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693235505; x=1693840305; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=AgTfuJ+2SR7wHNk0wScsVJOKb9hSrrlOBi0oejIscH4=; b=Fq10FHEWOrQBAFLIJGYgkUuOwiSWoX1ErDktQIXZPwt5FLYq0l5P1GruPeZfUuEIsl ZiAHoXBoGbacHajbVWTdcMXEf12Qf49dsqu2mOtu51uaTu6JOjq24lsGjsFF/40996Ao nlQewbtX6jKp5PCMzyE2G65jMYUDUb21BYm9B9pUnwIfVchqGpkxXQqAb8a4HrIKuJUi klBvdj+9GpT2GWYiqQn5DqugBbm0hzTlYkBpKNsPb53UvG59+H+9RfRw50rCuKs0d2Z5 +wpQKzqRaGONawtNZD4+PWTVMGpfRSy2SbfRpZ84HV5JjnXSk7scDgI4CrkHFr1WAOr6 BaHg== X-Gm-Message-State: AOJu0YzZE+ODZXVucUEoPDgbh7Fqtw4yJGqKYbd0+lytHRPC5fbaepVL SQJIlPU3u6kkyZL9UFiL52e8RMjoZEs= X-Google-Smtp-Source: AGHT+IFSfKyGlY1fJVyJDDAAQ2F/jDYjdtTldF9OG/AD25pzxWtoQEJJC/FkS5GCYAB4JJjrKDQknRmDUnM= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a25:d650:0:b0:d51:577e:425d with SMTP id n77-20020a25d650000000b00d51577e425dmr809965ybg.12.1693235504854; Mon, 28 Aug 2023 08:11:44 -0700 (PDT) Date: Mon, 28 Aug 2023 08:11:43 -0700 In-Reply-To: Mime-Version: 1.0 References: <00000000000099cf1805faee14d7@google.com> Message-ID: Subject: Re: [v5.15] WARNING in kvm_arch_vcpu_ioctl_run From: Sean Christopherson To: Muhammad Usama Anjum Cc: syzbot , syzkaller-lts-bugs@googlegroups.com, syzbot , Paolo Bonzini , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "H. Peter Anvin" , Jarkko Sakkinen , linux-kernel@vger.kernel.org, kvm@vger.kernel.org, x86@kernel.org, linux-sgx@vger.kernel.org Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Aug 28, 2023, Muhammad Usama Anjum wrote: > On 5/5/23 1:28 PM, syzbot wrote: > > syzbot has found a reproducer for the following issue on: > > > > HEAD commit: 8a7f2a5c5aa1 Linux 5.15.110 > This same warning has also been found on 6.1.21. > > > git tree: linux-5.15.y > > console output: https://syzkaller.appspot.com/x/log.txt?x=15f12318280000 > > kernel config: https://syzkaller.appspot.com/x/.config?x=ba8d5c9d6c5289f > > dashboard link: https://syzkaller.appspot.com/bug?extid=412c9ae97b4338c5187e > > compiler: Debian clang version 15.0.7, GNU ld (GNU Binutils for Debian) 2.35.2 > > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10e13c84280000 > > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=149d9470280000 > I've tried all the C and syz reproducers. I've also tried syz-crash which > launched multiple instances of VMs and ran syz reproducer. But the issue > didn't get reproduced. > > I don't have kvm skills. Can someone have a look at the the warning > (probably by static analysis)? > > > > > Downloadable assets: > > disk image: https://storage.googleapis.com/syzbot-assets/fc04f54c047f/disk-8a7f2a5c.raw.xz > > vmlinux: https://storage.googleapis.com/syzbot-assets/6b4ba4cb1191/vmlinux-8a7f2a5c.xz > > kernel image: https://storage.googleapis.com/syzbot-assets/d927dc3f9670/bzImage-8a7f2a5c.xz > > > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > > Reported-by: syzbot+412c9ae97b4338c5187e@syzkaller.appspotmail.com > > > > ------------[ cut here ]------------ > > WARNING: CPU: 0 PID: 3502 at arch/x86/kvm/x86.c:10310 kvm_arch_vcpu_ioctl_run+0x1d63/0x1f80 "Fixed" by https://lore.kernel.org/all/20230808232057.2498287-1-seanjc@google.com, in quotes because sadly the fix was to simply delete the sanity check :-(