All of lore.kernel.org
 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: Sat, 18 Jan 2020 20:06:34 +0000	[thread overview]
Message-ID: <bug-205099-206035-tTsJr5Mes8@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205099-206035@https.bugzilla.kernel.org/>

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

--- Comment #16 from Erhard F. (erhard_f@mailbox.org) ---
(In reply to Christophe Leroy from comment #15)
> Would be interesting to try and see if the VMAP_STACK series detects the
> stack overflow.
> Series at
> https://patchwork.ozlabs.org/project/linuxppc-dev/list/?series=149973
I just tried that, but in this case the G4 won't boot at all. The kernel loads
but booting gets stuck at a white display with only 2 lines visible where it
tells me it will open the display of the G4s Radeons offb display.

I applied your CONFIG_KASAN_VMALLOC on top of 5.5-rc6 and applied your
VMAP_STACK series afterwards.

 # grep -i kasan .config
CONFIG_HAVE_ARCH_KASAN=y
CONFIG_HAVE_ARCH_KASAN_VMALLOC=y
CONFIG_CC_HAS_KASAN_GENERIC=y
CONFIG_KASAN=y
CONFIG_KASAN_GENERIC=y
# CONFIG_KASAN_OUTLINE is not set
CONFIG_KASAN_INLINE=y
CONFIG_KASAN_STACK=1
CONFIG_KASAN_VMALLOC=y
# CONFIG_TEST_KASAN is not set
CONFIG_KASAN_SHADOW_OFFSET=0xe0000000

 # grep -i vmap .config
CONFIG_HAVE_ARCH_VMAP_STACK=y
CONFIG_VMAP_STACK=y

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

  parent reply	other threads:[~2020-01-18 20:08 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 [this message]
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
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-tTsJr5Mes8@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.