linux-kernel - Re: [PowerPC][next-20170324][kselftest] kernel Oops when running tm/tm-signal-context-chk-vsx

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]

Date:   Thu, 25 May 2017 16:23:39 +0530
From:   Abdul Haleem <abdhalee@...ux.vnet.ibm.com>
To:     Michael Ellerman <mpe@...erman.id.au>
Cc:     Cyril Bur <cyrilbur@...il.com>,
        sachinp <sachinp@...ux.vnet.ibm.com>,
        linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PowerPC][next-20170324][kselftest] kernel Oops when running
 tm/tm-signal-context-chk-vsx

On Wed, 2017-05-24 at 21:50 +1000, Michael Ellerman wrote:
> Abdul Haleem <abdhalee@...ux.vnet.ibm.com> writes:
> > Hi Cyril,
> >
> > I see a similar trace, but with 'tm-signal-stack' test for mainline
> > kernel 4.12.0-rc1 on PowerVM LPAR.
> 
> I can't reproduce this here.
It is not reproducible all the times.
> 
> Can you please retest on rc2.

With rc2, I see a similar call trace for the test
'tm_signal_context_chk_fpu'

I tried running tm-signal-stack alone, but no luck.
> 
> Also please include the exact version of the test (it prints it), and
> what toolchain you built it with.

test: tm_signal_context_chk_fpu
tags: git_version:v4.12-rc2-62-g2426125
success: tm_signal_context_chk_fpu

toolchain : gcc version 5.2.1


latest trace:
[ 1953.024563] Bad kernel stack pointer 7fffe0a1ddc0 at c00000000000b660
[ 1953.024582] Oops: Bad kernel stack pointer, sig: 6 [#1]
[ 1953.024585] SMP NR_CPUS=2048 
[ 1953.024585] NUMA 
[ 1953.024587] pSeries
[ 1953.024590] Modules linked in: rtc_generic vmx_crypto pseries_rng
autofs4
[ 1953.024597] CPU: 14 PID: 27145 Comm: tm-signal-conte Not tainted
4.12.0-rc2-00062-g2426125-dirty #1
[ 1953.024601] task: c0000007699f8600 task.stack: c00000076a24c000
[ 1953.024603] NIP: c00000000000b660 LR: 0000000010001aac CTR:
0000000000000000
[ 1953.024608] REGS: c00000000ebdbd40 TRAP: 0700   Not tainted
(4.12.0-rc2-00062-g2426125-dirty)
[ 1953.024610] MSR: 8000000102a03031 <SF,VEC,VSX,FP,ME,IR,DR,LE,TM[E]>
[ 1953.024615]   CR: 42000822  XER: 00000000
[ 1953.024618] CFAR: c00000000000b5b4 SOFTE: 0 
               GPR00: 0000000000000025 00007fffe0a1ddc0 0000000010028200
0000000000000000 
               GPR04: 000000000000000a 0000000000000000 0000000000000000
0000000000000000 
               GPR08: 00000000000000f8 0000000000000000 0000000000000000
0000000000000000 
               GPR12: 0000000000000000 00007fff8878c440 ffffffffffffffff
fffffffffffffffe 
               GPR16: fffffffffffffffd fffffffffffffffc fffffffffffffffb
fffffffffffffffa 
               GPR20: fffffffffffffff9 fffffffffffffff8 fffffffffffffff7
fffffffffffffff6 
               GPR24: fffffffffffffff5 fffffffffffffff4 fffffffffffffff3
fffffffffffffff2 
               GPR28: fffffffffffffff1 fffffffffffffff0 ffffffffffffffef
ffffffffffffffee 
[ 1953.024652] NIP [c00000000000b660] fast_exception_return+0x90/0x98
[ 1953.024655] LR [0000000010001aac] 0x10001aac
[ 1953.024657] Call Trace:
[ 1953.024658] Instruction dump:
[ 1953.024661] 7c40e3a6 e9a100d8 7c7b03a6 e84101a0 7c4ff120 e8410170
7c5a03a6 e8010070 
[ 1953.024666] e8410080 e8610088 e8810090 e8210078 <4c000024> 48000000
e8610178 88ed02bb 
[ 1953.024671] ---[ end trace 3e1eeb3cfb1260c1 ]---

> 
> cheers
> 


-- 
Regard's

Abdul Haleem
IBM Linux Technology Centre