From: bugzilla-daemon@kernel.org
To: linuxppc-dev@lists.ozlabs.org
Subject: [Bug 216041] Stack overflow at boot (do_IRQ: stack overflow: 1984) on a PowerMac G4 DP, KASAN debug build
Date: Sat, 28 May 2022 18:50:12 +0000 [thread overview]
Message-ID: <bug-216041-206035-VofFoHiJIj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216041-206035@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216041
Arnd Bergmann (arnd@arndb.de) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |arnd@arndb.de
--- Comment #4 from Arnd Bergmann (arnd@arndb.de) ---
Setting it higher is probably a good idea, but there really isn't a safe limit
with KASAN, at least if KASAN_STACK is active, running with KASAN always has a
risk of running into stack overflow issues.
One thing that sticks out is that there is an interrupt on the same stack as
the task, in
[eaa1c800] [c0009258] do_IRQ+0x20/0x34
[eaa1c820] [c00045b4] HardwareInterrupt_virt+0x108/0x10c
[eaa1c920] [c0c59b2c] __schedule+0x3f0/0x9dc
[eaa1c9b0] [c0c5a18c] schedule+0x74/0x13c
It looks like on ppc32, as of 547db12fd8a0 ("powerpc/32: Use vmapped stacks for
interrupts"), you have either VMAP_STACK (to detect stack overflows) or IRQ
stacks (to make them less likely). I think you really want both instead, and
allocate the IRQ stacks from vmalloc space as well.
The ext4 read path is a bit wasteful with KASAN enabled, using 1776 bytes from
ext4_lookup to ext4_read_bh, but not excessively so.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-05-28 18:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-28 11:43 [Bug 216041] New: Stack overflow at boot (do_IRQ: stack overflow: 1984) on a PowerMac G4 DP, KASAN debug build bugzilla-daemon
2022-05-28 11:43 ` [Bug 216041] " bugzilla-daemon
2022-05-28 11:44 ` bugzilla-daemon
2022-05-28 17:59 ` bugzilla-daemon
2022-05-28 18:50 ` bugzilla-daemon [this message]
2022-05-29 8:06 ` bugzilla-daemon
2022-05-29 13:08 ` bugzilla-daemon
2022-06-08 22:54 ` bugzilla-daemon
2022-08-23 21:31 ` bugzilla-daemon
2023-04-12 0:47 ` bugzilla-daemon
2023-04-12 0:47 ` bugzilla-daemon
2023-04-12 0:47 ` 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-216041-206035-VofFoHiJIj@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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.