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 30CDFC001B0 for ; Mon, 10 Jul 2023 20:29:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231760AbjGJU3C (ORCPT ); Mon, 10 Jul 2023 16:29:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41416 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230464AbjGJU26 (ORCPT ); Mon, 10 Jul 2023 16:28:58 -0400 Received: from mail-pl1-x64a.google.com (mail-pl1-x64a.google.com [IPv6:2607:f8b0:4864:20::64a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D7B57195 for ; Mon, 10 Jul 2023 13:28:57 -0700 (PDT) Received: by mail-pl1-x64a.google.com with SMTP id d9443c01a7336-1b9de135bddso20441365ad.3 for ; Mon, 10 Jul 2023 13:28:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1689020937; x=1691612937; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=rF29GRgI8hOW8jLROF4KwGHDbjmxwt4c6jNir/qrBzs=; b=jOkorrw1678EU4ez642rTZ8VfFOAcxpduo03I2ahHvbcWtPyX1J9zaxk9/HdnXV5NF +8NbcVqbXxIEETOSio0rxJoqfOFcya+Q2zzEYN8/fNNNZhZr/koS7KObNfEFEr4edCYG g2otY5bdgkOa+0E7RELb6lFzySFZIP8voBrD4PR9VBD7ILLRAclviplJxyOQPaXuKSMn ANzmrhcTL3RD0Tl5DGWR/knsa+xTrfDSUDkyKz9aCBjL3LiPBp9HFz9nayULGVFla0nc 80PIUiTW0WSKogKnyAAfCYQjdVEQaXl8YbAY/SrRBlKDsx/fX9G5/KTdHoV2xrgWvcBg +Pvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1689020937; x=1691612937; 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=rF29GRgI8hOW8jLROF4KwGHDbjmxwt4c6jNir/qrBzs=; b=R/X1HDD0YRRsaDd7BE/mi/9enEWAr2DKc6rIS7ukmtxRfSn8BUzkUKon2NHAeF5B7k JftvXte/kRxDACLgHUTPXaQVYqOPB94GZuC0MQHGq1hEEpFkGp4a4cnRyx/RIBpOPXqB syRaIh7byuxy223fRSJDdGvqunxLzyNP17EmKt4WclRI+vH8tkuDS56f/Kh95P4vbI1F OhKhhSFhSL9CIQabQPW44Y4cUpiqdJNKkHAV6EVGW2rQyK6lN3kb7DDwoZ6qFr6GldX1 OtvbZgBTjcHw/mZs8otpryaUGjklhSowdM+rWS6dk79t+kKSNdDgi5dymhbzKWhZdVCV oC7g== X-Gm-Message-State: ABy/qLaZaWx3aGHeRupfCcm/ygu/Jng8K/leM0zCMyWwr2INdqhC7Sah NcNZ4iy2MzG53lP3Sr+bKOJlxh/wm8k= X-Google-Smtp-Source: APBJJlG5lGHrhxyvgWQtaCd0VQa2a0kqO4lf9RNKbEuXXJ+s8Ne6YR8onYAvNGQVdSMH3WQ+Q13aPcYpSQc= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:902:c1cd:b0:1b8:8fe2:6627 with SMTP id c13-20020a170902c1cd00b001b88fe26627mr11923948plc.8.1689020937323; Mon, 10 Jul 2023 13:28:57 -0700 (PDT) Date: Mon, 10 Jul 2023 13:28:55 -0700 In-Reply-To: <000000000000c7224e06001eb4b1@google.com> Mime-Version: 1.0 References: <000000000000c7224e06001eb4b1@google.com> Message-ID: Subject: Re: [syzbot] Monthly kvm report (Jul 2023) From: Sean Christopherson To: syzbot Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com Content-Type: text/plain; charset="us-ascii" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jul 10, 2023, syzbot wrote: > Hello kvm maintainers/developers, > > This is a 31-day syzbot report for the kvm subsystem. > All related reports/information can be found at: > https://syzkaller.appspot.com/upstream/s/kvm > > During the period, 2 new issues were detected and 0 were fixed. > In total, 5 issues are still open and 111 have been fixed so far. > > Some of the still happening issues: > > Ref Crashes Repro Title > <1> 138 Yes WARNING in kvm_arch_vcpu_ioctl_run (5) > https://syzkaller.appspot.com/bug?extid=5feef0b9ee9c8e9e5689 This will *hopefully* be resolved when the unrestricted guest patches[*] are applied. This WARN is a bit of a catch-all. The upside is that it detects a lot of bugs, the downside is completely unrelated bugs can have the same signature, i.e. there may be more bugs lurking. [*] https://lore.kernel.org/all/20230613203037.1968489-1-seanjc@google.com > <2> 89 Yes WARNING in handle_exception_nmi (2) > https://syzkaller.appspot.com/bug?extid=4688c50a9c8e68e7aaa1 This is likely a bug in the underlying GCE kernel, i.e. in L0. Not sure how to bin this one. > <3> 58 No WARNING in kthread_bind_mask > https://syzkaller.appspot.com/bug?extid=087b7effddeec0697c66 This is more than likely a bug in either the workqueues or in sched, e.g. btrfs hit the same WARN a while back with a similarly innocuous alloc_workqueue() call. I'll (try to) re-label to "kernel".