From: cheung wall <zzqq0103.hey@gmail.com>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: Marc Zyngier <maz@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>, James Morse <james.morse@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: WARNING in kvm_age_gfn
Date: Wed, 13 Mar 2024 15:41:51 +0800 [thread overview]
Message-ID: <CAKHoSAsZRg5sTuLMTzSxmuP0_qBKrXvMYR2R1SZt_wNH9ONbLg@mail.gmail.com> (raw)
In-Reply-To: <ZfE41uSsTUmbtl6A@thinky-boi>
Thanks Oliver, I have confirmed the situation about the sha1 in the
path that is my fault. I will test this crash in the latest new linux
arm version. Meanwhile, more batches of the reports will be provided
after validation on the new experiment.
Best,
Cheung Wall
On Wed, Mar 13, 2024 at 1:25 PM Oliver Upton <oliver.upton@linux.dev> wrote:
>
> Hi,
>
> On Wed, Mar 13, 2024 at 01:02:10PM +0800, cheung wall wrote:
> > Hello,
> >
> > when using Syzkaller to fuzz the latest Linux Kernel arm64 version,
> > the following crash
>
> First, thank you. Glad to see folks are fuzzing KVM/arm64 now.
>
> > was triggered on:
> >
> > HEAD commit: 0dd3ee31125508cd67f7e7172247f05b7fd1753a (tag: v6.7)
>
> In order for these sorts of bug reports to be actionable, they really
> need to be against a close-to-upstream tree. 6.8 is out now, and 6.9-rc1
> is right around the corner.
>
> Having said that, I think there might be an issue or two with your bot
> because...
>
> > git tree: upstream
> >
> > console output: https://pastebin.com/raw/3NCyqPUn
> >
> > kernel config: https://pastebin.com/raw/mXEg4abU
> >
> > C reproducer: https://pastebin.com/raw/N0gEqk5x
>
> This reproducer doesn't work on upstream (tested kvmarm-6.9 tag), and
>
> > WARNING: CPU: 0 PID: 711 at arch/arm64/kvm/mmu.c:1592
> > kvm_age_gfn+0x64/0xdc
> > data/embfuzz/emblinux/linux-4a61839152cc3e9e00ac059d73a28d148d622b30/arch/arm64/kvm/mmu.c:1592
>
> The SHA1 in this path is suspiciously the same as 6.1.61. Are you
> certain the bot is working on the correct tree? Nevertheless, I think
> the WARN and associated bug were addressed in commit df6556adf27b
> ("KVM: arm64: Correctly handle page aging notifiers for unaligned
> memslot").
>
> Last thing -- I'm guessing your syzkaller runs will dredge up quite a bit
> of low-hanging bugs given how little exposure this code has had. Could
> you please aggregate the first batch of reports and send as a single
> series of email? Makes it much easier to keep track of.
>
> --
> Thanks,
> Oliver
prev parent reply other threads:[~2024-03-13 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 5:02 WARNING in kvm_age_gfn cheung wall
2024-03-13 5:25 ` Oliver Upton
2024-03-13 7:41 ` cheung wall [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=CAKHoSAsZRg5sTuLMTzSxmuP0_qBKrXvMYR2R1SZt_wNH9ONbLg@mail.gmail.com \
--to=zzqq0103.hey@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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 read-only IMAP folder(s) and NNTP newsgroup(s).