Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp3174975pxf; Mon, 15 Mar 2021 03:33:14 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw7gPsTKrg6XD4JNU5k9lLHjXWpCwSdryaxysqhuvroY+Q+wmvgIJhP6aEP8cZUMn5o2VXI X-Received: by 2002:a17:906:68c5:: with SMTP id y5mr22917957ejr.371.1615804394235; Mon, 15 Mar 2021 03:33:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1615804394; cv=none; d=google.com; s=arc-20160816; b=ibOlvOxzYiRGPh5uAiHfViajXKMb7e35LmX0WbVTNXGIQi4eC7v/pqYpSpGb6fCb4d N+X/FVRzT5++wU9FVrUlF9dy6QWlgRzb8xThSGrrOO3OeYM60ZGN/k3NDuiSDx80Tv7l AoMeNwsV5WNwz5+0NE4x5HaNaep3G6GBRAvUhOUvElTKVhIZ2IvUkUqIw2tKgf5XmzjR 9IKJGe4kW7ixGsfcDhJXrZbEo0MxMkuXiZ5FcsAksK9t0kY9ovM+I8CwTjnqXLa8Xwfl b4a7IzIE6nMXwcjDSwwSRKxhRvqlxsSPUso4zUuVVlcXI1hTG7/ybuGRNhoom2pUwq6z GxHw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=ihzTmq1DzCYfeFZPWFVAZ9LvCmeh4M6d07wbcpVEgM4=; b=mB+AItWG8ND+AXdYo5StPnq+8eqeyzY+s9Gcl8SyYiavvHw8wp0hltWG/3oQ/2LMx7 TbMr8f0yaIf8YTfmxYoMKne1Speed+RHM9rwl+IQ4NAb+8xrQqALoy1XWxnHk+jO2l5m U2kRWEIGXQQDQSd2IWoT1NZ3Rq38fBKlFfpt3wWjTOuTaFjzCgREhudSHMV+I4wz7Kuo /1NGoe5mroSoXip9HY1tdtcjMv87Oqh9G2m794SkzR4X+AUf7J3kGcuHWfB3/h9FggC8 5VyN5Z/1UzPZzN2DPbF06gKkU/qVO26btBQaXRO9kqQ7sEy3Ypvz/wxHvifXXj7kUpCE xoww== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c1si10293059edt.469.2021.03.15.03.32.51; Mon, 15 Mar 2021 03:33:14 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229907AbhCOKbZ (ORCPT + 99 others); Mon, 15 Mar 2021 06:31:25 -0400 Received: from frasgout.his.huawei.com ([185.176.79.56]:2695 "EHLO frasgout.his.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229720AbhCOKbR (ORCPT ); Mon, 15 Mar 2021 06:31:17 -0400 Received: from fraeml737-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DzXdw48HTz680Cl; Mon, 15 Mar 2021 18:26:44 +0800 (CST) Received: from lhreml724-chm.china.huawei.com (10.201.108.75) by fraeml737-chm.china.huawei.com (10.206.15.218) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 15 Mar 2021 11:31:15 +0100 Received: from [10.210.166.140] (10.210.166.140) by lhreml724-chm.china.huawei.com (10.201.108.75) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 15 Mar 2021 10:31:14 +0000 Subject: Re: arm64 syzbot instances To: Dmitry Vyukov CC: Arnd Bergmann , Mark Rutland , "Marc Zyngier" , Will Deacon , Ard Biesheuvel , Linux ARM , syzkaller , LKML , Peter Maydell , =?UTF-8?Q?Alex_Benn=c3=a9e?= , Jiahui Cen References: <48347b4d-9194-16f2-95a0-c3eb55ca9a80@huawei.com> From: John Garry Message-ID: <56d33822-e577-c8a8-673b-675d6920c379@huawei.com> Date: Mon, 15 Mar 2021 10:29:08 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.1.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.210.166.140] X-ClientProxiedBy: lhreml718-chm.china.huawei.com (10.201.108.69) To lhreml724-chm.china.huawei.com (10.201.108.75) X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 15/03/2021 10:01, Dmitry Vyukov wrote: > On Mon, Mar 15, 2021 at 10:45 AM John Garry wrote: >>>> It does not happen too often on syzbot so far, so let's try to do the >>>> right thing first. >>>> I've filed:https://bugs.launchpad.net/qemu/+bug/1918917 >>>> with a link to this thread. To be fair, I don't fully understand what >>>> I am talking about, I hope I proxied your description properly. >>> Thanks, looks good. I provided a little more detail in a comment there. >>> >>> Arnd >>> . >>> >> From looking at the bug report, my impression is that this is a qemu >> issue, as the logical IO space is mapped to the PCI host bridge IO >> space, and qemu does not handle accesses to that CPU addressable region >> at all. As Arnd said. >> >> However, we really should not be accessing logical IO ports 0 or 0x2f8 >> at all via ttyS3 if not enumerated from PCI device at that logical IO >> port. That is what I think anyway, as who knows what device - if any - >> really exists at that location. That is why I had this patch to just >> stop accesses to legacy IO port regions on arm64: >> >> https://lore.kernel.org/lkml/1610729929-188490-2-git-send-email-john.garry@huawei.com/ > Hi John, > > Thanks for the info. > > The patch is from January, but it's not merged yet, right? > It will fix the crash we see, right? > . It's not merged, and it probably would solve this issue. But following discussion with Arnd when it was originally posted, I still need to do some analysis whether it is the proper thing to do. However, as mentioned, the fundamental issue looks like qemu IO port access, so it would be good to check that first. On a related topic, I will cc colleague Jiahui Cen, who I think was doing some work arm on qemu support in a related area, so may share some experience here. Jiahui Cen did have a patch to fix logical PIO code from this work [0], which is not merged, but I don't think would help here. I will cc you on it. Thanks, John [0] https://lore.kernel.org/lkml/006ad6ce-d6b2-59cb-8209-aca3f6e53fec@huawei.com/