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 X-Spam-Level: X-Spam-Status: No, score=-18.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS, USER_IN_DEF_DKIM_WL autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C4A63C47082 for ; Mon, 7 Jun 2021 10:35:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AE59E611BD for ; Mon, 7 Jun 2021 10:35:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230291AbhFGKhe (ORCPT ); Mon, 7 Jun 2021 06:37:34 -0400 Received: from mail-qk1-f177.google.com ([209.85.222.177]:39719 "EHLO mail-qk1-f177.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230266AbhFGKhd (ORCPT ); Mon, 7 Jun 2021 06:37:33 -0400 Received: by mail-qk1-f177.google.com with SMTP id j184so16084653qkd.6 for ; Mon, 07 Jun 2021 03:35:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=W1Z9gEhrO+dFGwff9bZiaB/Edk6g694l5FTvX8TnmqE=; b=iTtdkG5oAQc1PJs6q76R+08BA/t3w7Wq0B5q0H3ufJUid+AhdIEg3Y7fEh5tvg+XdW 59gjhb2UQezoRRcs6jsnQry+7KjS/8g6IMni8HGD16dE51trmOBjXRtipOnNlpsv21H/ 4gB311yqb4F57DW8p98BkOuLBxbWB/QMW/ct8ycdrOesNpXpOqGaHtOf//MeCDDjrH5q uF0ze7KA5EuIxV5OEmz2vTKb7IYQSVhse9ZIsA0utfTlmx1u3ZfETfQW9jpk4VhCu02/ unJalB4bnrHV3OiWEs7dCHEm4b8l0JftUBB4lDcwiHZZ79ZbMqv7OGCPzQTCU5xdEPmM dSig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=W1Z9gEhrO+dFGwff9bZiaB/Edk6g694l5FTvX8TnmqE=; b=qovYarC78GWRBh3iRErVpBauZqvjrg2qqEZ+LG2CC9gdqzCxV2KZEr9FGe+o3GBYAf REs1hicgGMRNV34XKjLZwOYw88P93L/unlnCr7pmQ1nKk+CNDHLnOF948LcwvKWqO3L/ m4ktKcYvT4GbxHdS0iyNl1oYzV8fJU9pK69+mg6LaY+s+sof6NGp3cOzDBNjTy/SrmZ2 S9RZQC5UC3gbMbDRGkt7etjPA3waCvH/6b+/8v7r1enItLUdC4j2W9624BHFhHn1iYo1 mqDW5rvhM9qKHYzzh4TKngeYkqfpobKt8hYqw/MgxxRZSTylptgS0bx4tKzeuyZ4QNSW caZw== X-Gm-Message-State: AOAM530/2wbbjjbqG8zaqdpWX+F+FA0VV0F8Wa/B3dpO3aA4SpGzhu27 MwHSV/4ouPjpa3A7ZSa7SgXnT154eGG+iVdiRIC8NQ== X-Google-Smtp-Source: ABdhPJzTaPg9Os78/lByEqsfjEnL/w2wMnrVZ00vCZM9WGJQ9q3qi9YoIFwEozZ90r1enDNg908KqoHmNpKV1LanaKs= X-Received: by 2002:a37:4694:: with SMTP id t142mr16089543qka.265.1623062081807; Mon, 07 Jun 2021 03:34:41 -0700 (PDT) MIME-Version: 1.0 References: <000000000000f3fc9305c2e24311@google.com> <87v9737pt8.ffs@nanos.tec.linutronix.de> <0f6e6423-f93a-5d96-f452-4e08dbad9b23@redhat.com> <87sg277muh.ffs@nanos.tec.linutronix.de> In-Reply-To: From: Dmitry Vyukov Date: Mon, 7 Jun 2021 12:34:30 +0200 Message-ID: Subject: Re: [syzbot] WARNING in x86_emulate_instruction To: Wanpeng Li , Thomas Gleixner , syzkaller Cc: Paolo Bonzini , syzbot , Borislav Petkov , Dave Hansen , "H. Peter Anvin" , jarkko@kernel.org, Jim Mattson , Joerg Roedel , kan.liang@linux.intel.com, kvm , LKML , linux-sgx@vger.kernel.org, Ingo Molnar , Peter Zijlstra , Sean Christopherson , steve.wahl@hpe.com, syzkaller-bugs , Vitaly Kuznetsov , Wanpeng Li , "the arch/x86 maintainers" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 28, 2021 at 2:34 AM Wanpeng Li wrote: > > On Fri, 28 May 2021 at 08:31, Thomas Gleixner wrote: > > > > On Fri, May 28 2021 at 01:21, Paolo Bonzini wrote: > > > On 28/05/21 00:52, Thomas Gleixner wrote: > > >> > > >> So this is stale for a week now. It's fully reproducible and nobody > > >> can't be bothered to look at that? > > >> > > >> What's wrong with you people? > > > > > > Actually there's a patch on list ("KVM: X86: Fix warning caused by stale > > > emulation context"). Take care. > > > > That's useful, but does not change the fact that nobody bothered to > > reply to this report ... > > Will do it next time. Have a nice evening, guys! There was an idea to do this automatically by syzbot: dashboard/app: notify bug report about fix patches https://github.com/google/syzkaller/issues/1574 Namely: if syzbot discovers a fix anywhere (by the hash), it could send a notification email to the bug report email thread. The downside is that the robot sends even more emails, so I am not sure how it will be accepted. Any opinions?