linux-kernel - Re: [PATCH 1/6] syscalls: use uaccess_kernel in addr_limit_user

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20200720100104.GA20196@lst.de>
Date:   Mon, 20 Jul 2020 12:01:04 +0200
From:   Christoph Hellwig <hch@....de>
To:     Guenter Roeck <linux@...ck-us.net>
Cc:     linux-arch@...r.kernel.org, linux-kernel@...r.kernel.org,
        Vladimir Murzin <vladimir.murzin@....com>,
        linux-arm-kernel@...ts.infradead.org,
        Peter Maydell <peter.maydell@...aro.org>
Subject: Re: [PATCH 1/6] syscalls: use uaccess_kernel in
 addr_limit_user_check

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