From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 204479] KASAN hit at modprobe zram
Date: Mon, 12 Aug 2019 16:06:11 +0000 [thread overview]
Message-ID: <bug-204479-206035-z75WAkWKos@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-204479-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=204479
--- Comment #18 from Christophe Leroy (christophe.leroy@c-s.fr) ---
The Oops occurs at 0x3c8:
3b0: 81 21 00 88 lwz r9,136(r1)
3b4: 13 67 dc c4 vxor v27,v7,v27
3b8: 7d 11 a8 ce lvx v8,r17,r21
3bc: 11 5f 5b 06 vcmpgtsb v10,v31,v11
3c0: 11 6b 58 00 vaddubm v11,v11,v11
3c4: 81 41 00 8c lwz r10,140(r1)
>3c8: 7c 00 48 ce lvx v0,0,r9
This is because the value in r9 is most likely wrong.
r9 is loaded from the stack at 0x3b0
r9 was calculated and stored in the stack by the below code.
70: 3d 20 00 00 lis r9,0
72: R_PPC_ADDR16_HA .rodata.cst16
74: 3b b3 00 10 addi r29,r19,16
78: 39 29 00 00 addi r9,r9,0
7a: R_PPC_ADDR16_LO .rodata.cst16
7c: 91 21 00 88 stw r9,136(r1)
The value comes from .rodata.cst16
Two possibilities, either the value in .rodata.cst16 is wrong or the stack gets
corrupted.
Maybe you could try disabling KASAN in lib/raid6/Makefile for altivec8.o ? Or
maybe for the entire lib/raid6/ directory, just to see what happens ?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2019-08-12 16:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-204479-206035@https.bugzilla.kernel.org/>
2019-08-05 0:34 ` [Bug 204479] KASAN hit at modprobe zram bugzilla-daemon
2019-08-05 7:07 ` bugzilla-daemon
2019-08-05 14:00 ` bugzilla-daemon
2019-08-08 13:57 ` bugzilla-daemon
2019-08-08 21:55 ` bugzilla-daemon
2019-08-08 21:57 ` bugzilla-daemon
2019-08-08 21:58 ` bugzilla-daemon
2019-08-09 5:34 ` bugzilla-daemon
2019-08-09 5:38 ` bugzilla-daemon
2019-08-09 10:44 ` bugzilla-daemon
2019-08-09 14:08 ` bugzilla-daemon
2019-08-09 15:10 ` bugzilla-daemon
2019-08-09 17:50 ` bugzilla-daemon
2019-08-09 17:52 ` bugzilla-daemon
2019-08-09 20:31 ` bugzilla-daemon
2019-08-10 14:42 ` bugzilla-daemon
2019-08-12 16:01 ` bugzilla-daemon
2019-08-12 16:06 ` bugzilla-daemon [this message]
2019-08-13 11:12 ` bugzilla-daemon
2019-08-13 11:21 ` bugzilla-daemon
2019-08-13 11:49 ` bugzilla-daemon
2019-10-06 20:52 ` bugzilla-daemon
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=bug-204479-206035-z75WAkWKos@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).