From: Christoph Hellwig <hch@lst.de>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-arch@vger.kernel.org,
Peter Maydell <peter.maydell@linaro.org>,
Vladimir Murzin <vladimir.murzin@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/6] syscalls: use uaccess_kernel in addr_limit_user_check
Date: Mon, 20 Jul 2020 12:01:04 +0200 [thread overview]
Message-ID: <20200720100104.GA20196@lst.de> (raw)
In-Reply-To: <fe1d4a6d-e32d-6994-a08b-40134000e988@roeck-us.net>
To try to reproduce your report I built a mps2_defconfig kernel
and then run the qemu command line manually extraced from your
script below, using a mainline qemu built for arm-softmmu, but it
crashes with the following message even for the baseline kernel.
qemu: fatal: Lockup: can't escalate 3 to HardFault (current priority -1)
R00=00000000 R01=00000000 R02=00000000 R03=00000000
R04=00000000 R05=00000000 R06=00000000 R07=00000000
R08=00000000 R09=00000000 R10=00000000 R11=00000000
R12=00000000 R13=ffffffe0 R14=fffffff9 R15=00000000
XPSR=40000003 -Z-- A handler
FPSCR: 00000000
Does anyone have an idea what this means?
---
/opt/qemu/bin/qemu-system-arm \
-M mps2-an385 \
-cpu cortex-m3 \
-dtb arch/arm/boot/dts/mps2-an385.dtb \
-kernel vmlinux \
-no-reboot \
-snapshot -m 16 \
-initrd ~/images/rootfs-arm-m3.cpio \
-append 'panic=-1' \
-bios ~/images/mps2-boot.axf \
-nographic -monitor null -serial stdio
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2020-07-20 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200714105505.935079-1-hch@lst.de>
[not found] ` <20200714105505.935079-2-hch@lst.de>
[not found] ` <20200718013849.GA157764@roeck-us.net>
[not found] ` <20200718094846.GA8593@lst.de>
[not found] ` <fe1d4a6d-e32d-6994-a08b-40134000e988@roeck-us.net>
2020-07-20 10:01 ` Christoph Hellwig [this message]
2020-07-20 14:55 ` [PATCH 1/6] syscalls: use uaccess_kernel in addr_limit_user_check Guenter Roeck
2020-07-20 15:28 ` 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=20200720100104.GA20196@lst.de \
--to=hch@lst.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=peter.maydell@linaro.org \
--cc=vladimir.murzin@arm.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).