From: John Garry <john.garry@huawei.com>
To: Arnd Bergmann <arnd@arndb.de>, Dmitry Vyukov <dvyukov@google.com>
Cc: "Mark Rutland" <mark.rutland@arm.com>,
"Marc Zyngier" <maz@kernel.org>, "Will Deacon" <will@kernel.org>,
"Ard Biesheuvel" <ardb@kernel.org>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
syzkaller <syzkaller@googlegroups.com>,
LKML <linux-kernel@vger.kernel.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: arm64 syzbot instances
Date: Mon, 15 Mar 2021 09:43:02 +0000 [thread overview]
Message-ID: <48347b4d-9194-16f2-95a0-c3eb55ca9a80@huawei.com> (raw)
In-Reply-To: <CAK8P3a221xG9dM1UZXNGhjkVyxn6sjscSYdsFwWO6CVB_HQhXw@mail.gmail.com>
On 12/03/2021 10:52, Arnd Bergmann wrote:
> On Fri, Mar 12, 2021 at 11:38 AM Dmitry Vyukov <dvyukov@google.com> wrote:
>> On Fri, Mar 12, 2021 at 11:11 AM Arnd Bergmann <arnd@arndb.de> 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/
Thanks,
John
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-03-15 9:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 11:38 arm64 syzbot instances Dmitry Vyukov
2021-03-11 12:33 ` Mark Rutland
2021-03-11 16:56 ` Dmitry Vyukov
2021-03-17 18:45 ` Mark Rutland
2021-03-18 8:32 ` Dmitry Vyukov
2021-03-11 17:11 ` Dmitry Vyukov
2021-03-11 13:30 ` Arnd Bergmann
2021-03-11 17:25 ` Dmitry Vyukov
2021-03-12 6:42 ` Dmitry Vyukov
2021-03-11 17:57 ` Dmitry Vyukov
2021-03-12 8:39 ` Arnd Bergmann
2021-03-12 8:46 ` Dmitry Vyukov
2021-03-12 9:16 ` Arnd Bergmann
2021-03-12 9:21 ` Dmitry Vyukov
2021-03-12 10:10 ` Arnd Bergmann
2021-03-12 10:38 ` Dmitry Vyukov
2021-03-12 10:52 ` Arnd Bergmann
2021-03-15 9:43 ` John Garry [this message]
2021-03-15 10:01 ` Dmitry Vyukov
2021-03-15 10:29 ` John Garry
2021-03-15 10:34 ` Dmitry Vyukov
2021-03-15 11:11 ` Arnd Bergmann
2021-03-20 20:43 ` Peter Maydell
2021-03-21 11:52 ` Arnd Bergmann
2021-03-21 11:55 ` Arnd Bergmann
2021-03-21 18:59 ` Arnd Bergmann
2021-03-22 13:51 ` Peter Maydell
2021-03-22 15:42 ` Arnd Bergmann
2021-03-22 16:34 ` John Garry
2021-03-22 16:49 ` Peter Maydell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48347b4d-9194-16f2-95a0-c3eb55ca9a80@huawei.com \
--to=john.garry@huawei.com \
--cc=alex.bennee@linaro.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=dvyukov@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=peter.maydell@linaro.org \
--cc=syzkaller@googlegroups.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).