From: Florian Fainelli <f.fainelli@gmail.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>,
open list <linux-kernel@vger.kernel.org>,
LTP List <ltp@lists.linux.it>,
linux-arm-kernel@lists.infradead.org
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
Basil Eljuse <Basil.Eljuse@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
catalin.marinas@arm.com, Will Deacon <will@kernel.org>,
james.morse@arm.com, Bjorn Andersson <bjorn.andersson@linaro.org>,
saiprakash.ranjan@codeaurora.org, steven.price@arm.com,
suzuki.poulose@arm.com, Mark Rutland <mark.rutland@arm.com>,
ascull@google.com, Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: BUG: KASAN: global-out-of-bounds in is_affected_midr_range_list on arm64
Date: Wed, 8 Jul 2020 22:16:26 -0700 [thread overview]
Message-ID: <559c5a04-a2ab-bfa2-c26e-4fbbf6d273ed@gmail.com> (raw)
In-Reply-To: <CA+G9fYs3EavpU89-rTQfqQ9GgxAMgMAk7jiiVrfP0yxj5s+Q6g@mail.gmail.com>
On 7/8/2020 9:36 PM, Naresh Kamboju wrote:
> While running LTP cpuhotplug test on mainline 5.8.0-rc4 the kernel BUG noticed
> on arm64 Juno-r2 KASAN config enabled kernel.
>
> steps to reproduce:
> - boot KASAN enabled Juno-r2 device
> - cd /opt/ltp
> - ./runltp -f cpuhotplug
>
> metadata:
> git branch: master
> git repo: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> git commit: 63e1968a2c87e9461e9694a96991935116e0cec7
> kernel-config:
> https://builds.tuxbuild.com/wc75HkrGrWgQCdI-l_1jUw/kernel.config
> vmlinux: https://builds.tuxbuild.com/wc75HkrGrWgQCdI-l_1jUw/vmlinux.xz
> system.map: https://builds.tuxbuild.com/wc75HkrGrWgQCdI-l_1jUw/System.map
>
> Test log:
> Name: cpuhotplug02
> Date: Thu Jul 9 00:09:24 UTC 2020
> Desc: What happens to a process when its CPU is offlined?
>
Just sent a tentative fix:
https://lore.kernel.org/linux-arm-kernel/20200709051345.14544-1-f.fainelli@gmail.com/
--
Florian
prev parent reply other threads:[~2020-07-09 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 4:36 Naresh Kamboju
2020-07-09 5:16 ` Florian Fainelli [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=559c5a04-a2ab-bfa2-c26e-4fbbf6d273ed@gmail.com \
--to=f.fainelli@gmail.com \
--cc=Basil.Eljuse@arm.com \
--cc=arnd@arndb.de \
--cc=ascull@google.com \
--cc=bjorn.andersson@linaro.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ltp@lists.linux.it \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=naresh.kamboju@linaro.org \
--cc=saiprakash.ranjan@codeaurora.org \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=viresh.kumar@linaro.org \
--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
all inboxes | Powered by JetHome®