linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 205099] KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d
Date: Fri, 04 Sep 2020 22:50:12 +0000	[thread overview]
Message-ID: <bug-205099-206035-mDU4pUp7bJ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205099-206035@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=205099

Erhard F. (erhard_f@mailbox.org) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 Attachment #287625|0                           |1
        is obsolete|                            |
 Attachment #288411|0                           |1
        is obsolete|                            |

--- Comment #30 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 292345
  --> https://bugzilla.kernel.org/attachment.cgi?id=292345&action=edit
dmesg (5.9-rc3, OUTLINE KASAN, PowerMac G4 DP)

Re-tested with v5.9-rc3 out of curiosity. Not much change here, the bug shows
up with OUTLINE KASAN but not with INLINE KASAN, everything else being equal:

==================================================================
BUG: KASAN: user-memory-access in raid6_altivec8_gen_syndrome_real+0x2b0/0x480
[raid6_pq]
Read of size 4 at addr 5764b118 by task modprobe/126

CPU: 1 PID: 126 Comm: modprobe Tainted: G        W         5.9.0-rc3-PowerMacG4
#2
Call Trace:
[e32cb7b8] [c0517aac] dump_stack+0xc4/0xf8 (unreliable)
[e32cb7e8] [c026e73c] kasan_report+0x16c/0x170
[e32cb828] [b02004e0] raid6_altivec8_gen_syndrome_real+0x2b0/0x480 [raid6_pq]
[e32cba18] [b02006fc] raid6_altivec8_gen_syndrome+0x4c/0x88 [raid6_pq]
[e32cba38] [b021a42c] init_module+0x42c/0x590 [raid6_pq]
[e32cbb08] [c00058a0] do_one_initcall+0xb8/0x3dc
[e32cbbd8] [c011c0fc] do_init_module+0xa8/0x2c4
[e32cbc08] [c011f02c] load_module+0x2b98/0x2d4c
[e32cbe18] [c011f448] sys_finit_module+0x100/0x138
[e32cbf38] [c001a1cc] ret_from_syscall+0x0/0x34
--- interrupt: c01 at 0x3d2068
    LR = 0x506104
==================================================================
BUG: Unable to handle kernel data access on read at 0x5764b118
Faulting instruction address: 0xb02004e0
Oops: Kernel access of bad area, sig: 11 [#1]

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-09-04 22:52 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-06 17:49 [Bug 205099] New: KASAN hit at raid6_pq: BUG: Unable to handle kernel data access at 0x00f0fd0d bugzilla-daemon
2019-10-06 17:49 ` [Bug 205099] " bugzilla-daemon
2019-10-09 21:19 ` bugzilla-daemon
2019-12-10 23:51 ` bugzilla-daemon
2019-12-10 23:52 ` bugzilla-daemon
2019-12-10 23:54 ` bugzilla-daemon
2019-12-11 19:22 ` bugzilla-daemon
2019-12-14 13:49 ` bugzilla-daemon
2019-12-15 16:01 ` bugzilla-daemon
2019-12-21 17:42 ` bugzilla-daemon
2019-12-21 17:43 ` bugzilla-daemon
2020-01-17 21:16 ` bugzilla-daemon
2020-01-17 21:19 ` bugzilla-daemon
2020-01-17 21:22 ` bugzilla-daemon
2020-01-17 21:25 ` bugzilla-daemon
2020-01-18  8:47 ` bugzilla-daemon
2020-01-18 20:06 ` bugzilla-daemon
2020-01-20 12:40 ` bugzilla-daemon
2020-01-20 22:56 ` bugzilla-daemon
2020-01-21  5:52 ` bugzilla-daemon
2020-01-21 12:20 ` bugzilla-daemon
2020-01-21 12:24 ` bugzilla-daemon
2020-01-21 13:00 ` bugzilla-daemon
2020-01-21 13:00 ` bugzilla-daemon
2020-01-21 13:31 ` bugzilla-daemon
2020-02-26 15:49 ` bugzilla-daemon
2020-02-26 15:52 ` bugzilla-daemon
2020-02-26 16:17 ` bugzilla-daemon
2020-04-13 14:12 ` bugzilla-daemon
2020-04-13 14:15 ` bugzilla-daemon
2020-09-04 22:50 ` bugzilla-daemon [this message]
2020-09-04 22:54 ` bugzilla-daemon
2021-06-19  6:27 ` bugzilla-daemon
2021-06-19  8:25 ` bugzilla-daemon
2021-11-26  1:47 ` bugzilla-daemon
2021-11-26  1:48 ` bugzilla-daemon
2021-11-26  1:49 ` bugzilla-daemon
2021-11-26  9:03 ` bugzilla-daemon
2021-11-26  9:14 ` bugzilla-daemon
2021-11-26  9:20 ` bugzilla-daemon
2021-11-26 11:33 ` bugzilla-daemon
2021-11-29  0:32 ` bugzilla-daemon
2021-11-29  0:32 ` bugzilla-daemon
2021-11-29  0:34 ` bugzilla-daemon
2021-11-29  6:51 ` bugzilla-daemon
2021-11-29 19:46 ` bugzilla-daemon
2021-11-29 19:46 ` bugzilla-daemon
2021-11-30 13:58 ` bugzilla-daemon
2021-11-30 13:58 ` bugzilla-daemon
2021-11-30 15:39 ` 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-205099-206035-mDU4pUp7bJ@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).