linux-kernel - Re: [Qemu-devel] Commit 34b9c07a3 (microblaze: Disable stack protection from bootloader) causing qemu crash

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>] [day] [month] [year] [list]

Message-ID: <20140210103148.187113o1jxn9inz4@67.228.131.205>
Date:	Mon, 10 Feb 2014 10:31:48 -0600
From:	linux@...ck-us.net
To:	Michal Simek <monstr@...str.eu>
Cc:	"Edgar E. Iglesias" <edgar.iglesias@...il.com>,
	microblaze-uclinux@...e.uq.edu.au,
	LKML <linux-kernel@...r.kernel.org>, qemu-devel@...gnu.org
Subject: Re: [Qemu-devel] Commit 34b9c07a3 (microblaze: Disable stack
 protection from bootloader) causing qemu crash

Quoting Michal Simek <monstr@...str.eu>:

> Hi Edgar and Guenter,
>
>
> 2014-02-08 Edgar E. Iglesias <edgar.iglesias@...il.com>:
>
>> On Fri, Feb 07, 2014 at 03:17:31PM -0800, Guenter Roeck wrote:
>> > Michal,
>> >
>> > commit 34b9c07a3 (microblaze: Disable stack protection from bootloader)
>> results
>> > in the following qemu crash in 3.14-rc1.
>> >
>> > /opt/buildbot/bin/qemu-system-microblaze -M petalogix-s3adsp1800 -kernel
>> arch/microblaze/boot/linux.bin -no-reboot -append "console=ttyUL0,115200 "
>> -nographic
>> > qemu: fatal: fetching nop sequence
>> >
>> > IN: PC=20
>> > rmsr=4300 resr=7 rear=c0389fe8 debug=0 imm=ffffffd0 iflags=0 fsr=0
>> > btaken=1 btarget=c03a9f24 mode=kernel(saved=kernel) eip=512 ie=0
>> > r00=00000000 r01=c0389fcc r02=c0386a52 r03=000000c0
>> > r04=00004100 r05=9052fab4 r06=00000000 r07=90530ab4
>> > r08=00000000 r09=00400000 r10=00400000 r11=c03a9f24
>> > r12=00621000 r13=40aef0c0 r14=00000000 r15=c0000294
>> > r16=00000000 r17=c03a9f28 r18=00000000 r19=00000000
>> > r20=00000000 r21=00000000 r22=00000000 r23=00000000
>> > r24=00000000 r25=00000000 r26=00000000 r27=00000000
>> > r28=00000000 r29=00400000 r30=00000300 r31=c03932d4
>> >
>>
>
> Can you please check that these 2 registers are not available when
> microblaze is configured with full MMU?
> Because I expect that you are testing MMU kernel but these two writes
> should be just nops.
>

Hi Michal,

I can send you my configuration if that is what you are
looking for. Other than that, I am pretty clueless when
it comes to Microblaze details - all I do is to build
an image and check if it boots with qemu. This is part of
my sanity tests of upcoming -stable kernel versions.

It will have to wait until tonight, though - my home internet
connection is down and I can not connect to the system right
now.

Guenter

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/