linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Upton <oliver.upton@linux.dev>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: open list <linux-kernel@vger.kernel.org>,
	kvm list <kvm@vger.kernel.org>,
	Linux ARM <linux-arm-kernel@lists.infradead.org>,
	Yu Zhao <yuzhao@google.com>, Reiji Watanabe <reijiw@google.com>,
	Marc Zyngier <maz@kernel.org>,
	Shaoqin Huang <shahuang@redhat.com>,
	rananta@google.com, Paolo Bonzini <pbonzini@redhat.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Anders Roxell <anders.roxell@linaro.org>
Subject: Re: kvm: arm64: WARNING: CPU: 3 PID: 1 at arch/arm64/kvm/hyp/pgtable.c:453 hyp_map_walker+0xa8/0x120
Date: Wed, 13 Sep 2023 16:46:46 +0000	[thread overview]
Message-ID: <ZQHndmjItuE7AOyz@linux.dev> (raw)
In-Reply-To: <CA+G9fYtC0iTRSRj8WSw5KMDwrx4Z3Djo89OXXdHjna9r3qy3Kg@mail.gmail.com>

Hi Naresh,

Can you cc the correct kvmarm mailing list in the future? We had to
migrate a few releases ago but the right address is in MAINTAINERS.

On Wed, Sep 13, 2023 at 05:33:28PM +0530, Naresh Kamboju wrote:
> Following kernel warning noticed on arm64 Raspberry Pi 4 Model B and
> Juno-r2 devices while booting the mainline 6.6.0-rc1 kernel.

Thanks for the report. This came up already and Marc has a fix queued up
that'll find its way to Linus' tree eventually:

https://lore.kernel.org/kvmarm/20230828153121.4179627-1-maz@kernel.org/

-- 
Thanks,
Oliver

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-09-13 16:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13 12:03 kvm: arm64: WARNING: CPU: 3 PID: 1 at arch/arm64/kvm/hyp/pgtable.c:453 hyp_map_walker+0xa8/0x120 Naresh Kamboju
2023-09-13 16:46 ` Oliver Upton [this message]

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=ZQHndmjItuE7AOyz@linux.dev \
    --to=oliver.upton@linux.dev \
    --cc=anders.roxell@linaro.org \
    --cc=arnd@arndb.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=naresh.kamboju@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=rananta@google.com \
    --cc=reijiw@google.com \
    --cc=shahuang@redhat.com \
    --cc=yuzhao@google.com \
    /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).