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=-13.4 required=3.0 tests=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 66E00C2D0BF for ; Thu, 5 Dec 2019 11:35:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3B7DB24654 for ; Thu, 5 Dec 2019 11:35:32 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=google.com header.i=@google.com header.b="VLVyGXFm" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729146AbfLELfb (ORCPT ); Thu, 5 Dec 2019 06:35:31 -0500 Received: from mail-qt1-f196.google.com ([209.85.160.196]:46090 "EHLO mail-qt1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729017AbfLELfb (ORCPT ); Thu, 5 Dec 2019 06:35:31 -0500 Received: by mail-qt1-f196.google.com with SMTP id 38so3158486qtb.13 for ; Thu, 05 Dec 2019 03:35:30 -0800 (PST) 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=XFj7/o8CY27u2EP/Ii6IWyV6V/qKCHo8NGPo9OoyP2o=; b=VLVyGXFmunojbceinV2tb/wrcOELq58HBQBO3PG1yIVJE9cJvQrEbuqEZfs1I80KNB NpsR6uAqwQ1je6sENpKTPDm/ZPRPYiyWVyhKhz0Gkvv7qxp0qEVtFkBBxA6A80T2TXsl X7m1sn9D0K3nhXLdO1yN+hrVDQu5/hiurh8lYBgW2BPj5Yycs6wAmQwzKT1tL8kEMsPy K0NR8MTeoPaHhZSlq8XJVOGWI8DaOELPIF19c03IuvUui/HejI8FD0EVyWCqT64GrbmK +X5RQyE6wCiiWL0oRAogajCglCRovqnXNNoySkGhPdL0ztR8wC2vD0Gl8PA4lCPMJHcV sd3A== 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=XFj7/o8CY27u2EP/Ii6IWyV6V/qKCHo8NGPo9OoyP2o=; b=PrcHHFgHrRLPq53oc/+izp31OJWRPzAANXmNq3Mjq9esHrPkF+iT6xjh2/4bbhGUiZ 9gr/rewNWokS4qwGnl3NRaTWHr6IcbCacWf1CM9Bedwg489lC4MHVPqv2OMitV77Asud vplEh6cj9A0UaIiLJFtGNYE4JdaCqSfXTZF5IeWxL7+Ami6ScjShxxmVqb/Ps2yzOb9o Eej1p2/b9CgDDjYTKdHop8YqN4LVMBTGlD5O5mT/P2sWPBg53xTcHfzA4J2wEwXNMdkd fn+d2YQhLckp97z/pnw+ATDwHZ1nkaNGqH46Rj9YYI1JQgT6kaFP7ij3+kKnYYXRevma 2/sA== X-Gm-Message-State: APjAAAVzIcCpxH+4911OhZY4gjUuwJUJllh8Wc19EgJBWVHzsHCVDoXl mLHPDErl2U6cfIa3n4YcFAM86fQQjMxLixcB82OFHA== X-Google-Smtp-Source: APXvYqywdNT7YtUlcyhBayK1c5G6KgoYnokHv4gbK83yKRI9KmJz2M3nmPsIV9emnEuu9bBpOrULeU5+4XFCmFaRuPs= X-Received: by 2002:ac8:2489:: with SMTP id s9mr7043538qts.257.1575545729972; Thu, 05 Dec 2019 03:35:29 -0800 (PST) MIME-Version: 1.0 References: <0000000000003e640e0598e7abc3@google.com> <41c082f5-5d22-d398-3bdd-3f4bf69d7ea3@redhat.com> <397ad276-ee2b-3883-9ed4-b5b1a2f8cf67@i-love.sakura.ne.jp> In-Reply-To: <397ad276-ee2b-3883-9ed4-b5b1a2f8cf67@i-love.sakura.ne.jp> From: Dmitry Vyukov Date: Thu, 5 Dec 2019 12:35:18 +0100 Message-ID: Subject: Re: KASAN: slab-out-of-bounds Read in fbcon_get_font To: Tetsuo Handa Cc: Paolo Bonzini , syzbot , Andrey Ryabinin , Bartlomiej Zolnierkiewicz , Daniel Thompson , Daniel Vetter , DRI , ghalat@redhat.com, Gleb Natapov , gwshan@linux.vnet.ibm.com, "H. Peter Anvin" , James Morris , kasan-dev , KVM list , Linux Fbdev development list , LKML , linux-security-module , Maarten Lankhorst , Ingo Molnar , Michael Ellerman , Russell Currey , Sam Ravnborg , "Serge E. Hallyn" , stewart@linux.vnet.ibm.com, syzkaller-bugs , Kentaro Takeda , Thomas Gleixner , "the arch/x86 maintainers" Content-Type: text/plain; charset="UTF-8" Sender: kvm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Thu, Dec 5, 2019 at 11:41 AM Tetsuo Handa wrote: > > On 2019/12/05 19:22, Paolo Bonzini wrote: > > Ah, and because the machine is a KVM guest, kvm_wait appears in a lot of > > backtrace and I get to share syzkaller's joy every time. :) > > > > This bisect result is bogus, though Tetsuo found the bug anyway. > > Perhaps you can exclude commits that only touch architectures other than > > x86? > > > > It would be nice if coverage functionality can extract filenames in the source > code and supply the list of filenames as arguments for bisect operation. What is the criteria for file name extraction? What will bisect operation do with the set of files? If you have a feature/improvement request, please file it at: https://github.com/google/syzkaller/issues/new