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: Mon, 13 Apr 2020 14:12:10 +0000 [thread overview]
Message-ID: <bug-205099-206035-54mmoFn30H@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 #287621|0 |1
is obsolete| |
--- Comment #28 from Erhard F. (erhard_f@mailbox.org) ---
Created attachment 288411
--> https://bugzilla.kernel.org/attachment.cgi?id=288411&action=edit
dmesg (5.7-rc1, OUTLINE KASAN, PowerMac G4 DP)
Re-tested with v5.7-rc1 out of curiosity. Not much change here, the bug shows
up with OUTLINE KASAN but not with INLINE KASAN, everything else being equal.
[...]
Apr 13 16:01:11 T600 kernel: BUG: Unable to handle kernel data access on read
at 0x0050a0f0
Apr 13 16:01:11 T600 kernel: Faulting instruction address: 0xf1aa1564
Apr 13 16:01:11 T600 kernel: Oops: Kernel access of bad area, sig: 11 [#1]
Apr 13 16:01:11 T600 kernel: BE PAGE_SIZE=4K MMU=Hash SMP NR_CPUS=2 PowerMac
Apr 13 16:01:11 T600 kernel: Modules linked in: raid6_pq(+) zlib_inflate
firewire_ohci firewire_core ehci_pci(+) ohci_hcd crc_itu_t sr_mod cdrom
ehci_hcd snd_aoa_i2sbus snd_aoa_soundbus snd_pcm snd_timer snd ss>
Apr 13 16:01:11 T600 kernel: CPU: 0 PID: 149 Comm: modprobe Tainted: G W
5.7.0-rc1-PowerMacG4+ #1
Apr 13 16:01:11 T600 kernel: NIP: f1aa1564 LR: f1aa14e8 CTR: c0255b78
Apr 13 16:01:11 T600 kernel: REGS: f1963780 TRAP: 0300 Tainted: G W
(5.7.0-rc1-PowerMacG4+)
Apr 13 16:01:11 T600 kernel: MSR: 02009032 <VEC,EE,ME,IR,DR,RI> CR: 28228828
XER: 00000000
Apr 13 16:01:11 T600 kernel: DAR: 0050a0f0 DSISR: 40000000
GPR00: f19639d8 f1963838 ebd1de60 eb1dc070
00001000 00000003 f1aa14e8 00000000
GPR08: 00000000 0050a0f0 5d0dfdad fffffff0
c0255b78 00a48ff4 00000060 00000050
GPR16: eb1dc000 eb1df000 eb1de000 00000070
00000060 00000050 00000040 00000030
GPR24: 00000020 00000010 00000008 f1963a8c
f1963a78 eb1df010 eb1de010 00000000
Apr 13 16:01:11 T600 kernel: NIP [f1aa1564]
raid6_altivec8_gen_syndrome_real+0x3c4/0x480 [raid6_pq]
Apr 13 16:01:11 T600 kernel: LR [f1aa14e8]
raid6_altivec8_gen_syndrome_real+0x348/0x480 [raid6_pq]
Apr 13 16:01:11 T600 kernel: Call Trace:
Apr 13 16:01:11 T600 kernel: [f1963838] [0000000a] 0xa (unreliable)
Apr 13 16:01:11 T600 kernel: [f1963a28] [f1aa1654]
raid6_altivec8_gen_syndrome+0x34/0x58 [raid6_pq]
Apr 13 16:01:11 T600 kernel: [f1963a48] [f12603cc] init_module+0x3cc/0x530
[raid6_pq]
Apr 13 16:01:11 T600 kernel: [f1963b18] [c00058e4] do_one_initcall+0xb8/0x36c
Apr 13 16:01:11 T600 kernel: [f1963be8] [c0117f64] do_init_module+0xa8/0x2c4
Apr 13 16:01:11 T600 kernel: [f1963c18] [c011ae38] load_module+0x2bd8/0x2d5c
Apr 13 16:01:11 T600 kernel: [f1963e18] [c011b230] sys_finit_module+0x100/0x138
Apr 13 16:01:11 T600 kernel: [f1963f38] [c001a224] ret_from_syscall+0x0/0x34
Apr 13 16:01:11 T600 kernel: --- interrupt: c01 at 0x892988
LR = 0xa20a14
Apr 13 16:01:11 T600 kernel: Instruction dump:
Apr 13 16:01:11 T600 kernel: 1304c4c4 7d2048ce 39210090 1325ccc4 7d6048ce
1346d4c4 81210088 1367dcc4
Apr 13 16:01:11 T600 kernel: 8141008c 11284cc4 115f5b06 116b5800 <7c0048ce>
392100a0 7d8048ce 392100b0
Apr 13 16:01:11 T600 kernel: ---[ end trace ebe3b589d509d4f6 ]---
[...]
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-04-13 14:14 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 [this message]
2020-04-13 14:15 ` bugzilla-daemon
2020-09-04 22:50 ` bugzilla-daemon
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-54mmoFn30H@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.