From: Colin Ian King via Bugspray Bot <bugbot@kernel.org>
To: deller@gmx.de, bugs@lists.linux.dev,
linux-parisc@vger.kernel.org,
James.Bottomley@HansenPartnership.com
Subject: Re: calling getcpu with misaligned address causes kernel panic
Date: Tue, 01 Oct 2024 15:00:13 +0000 [thread overview]
Message-ID: <20241001-b219339c1-77ccff4939f9@bugzilla.kernel.org> (raw)
In-Reply-To: <20241001-b219339c0-15109b153aef@bugzilla.kernel.org>
Colin Ian King writes via Kernel.org Bugzilla:
uname -a
./Linux hppa 6.10.6-parisc #1 SMP Debian 6.10.6-1 (2024-08-19) parisc GNU/Linux
cking@hppa:~$ ./crash
[ 991.661268] handle_unaligned: 190 callbacks suppressed
[ 991.661901] Kernel: unaligned access to 0xf8c00001 in sys_getcpu+0x30/0x6c (iir 0xf3cd280)
[ 991.677270] Backtrace:
[ 991.679232] [<10413c60>] handle_unaligned+0x598/0x758
[ 991.679232] [<10409854>] handle_interruption+0x1dc/0x7b8
[ 991.679232] [<10454dec>] sys_getcpu+0x30/0x6c
[ 991.679232]
[ 991.679232]
[ 991.679232] Page fault: bad address: Code=26 (Data memory access rights trap) at addr f8c00000
[ 991.679232] CPU: 2 PID: 725 Comm: crash Not tainted 6.10.6-parisc #1 Debian 6.10.6-1
[ 991.679232] Hardware name: 9000/778/B160L
[ 991.679232]
[ 991.679232] YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
[ 991.679232] PSW: 00000000000001101111111100001111 Not tainted
[ 991.679232] r00-03 0006ff0f 00000000 10413c60 12de83c0
[ 991.679232] r04-07 12de8080 17220940 fc000000 f8c00001
[ 991.679232] r08-11 00000000 0f3cd280 f8fd5c20 f8fd2e58
[ 991.679232] r12-15 00011008 00bdd7d8 00000000 00000001
[ 991.679232] r16-19 12de8080 00138428 00bd5730 ff000000
[ 991.679232] r20-23 00000000 00000000 00000000 12de86d8
[ 991.679232] r24-27 00000000 00000000 12de8080 11148ae8
[ 991.679232] r28-31 00000000 000003c0 12de8400 f8c00000
[ 991.679232] sr00-03 00000000 000003c0 00000000 000003c0
[ 991.679232] sr04-07 00000000 00000000 00000000 00000000
[ 991.679232]
[ 991.679232] IASQ: 00000000 00000000 IAOQ: 10413598 1041359c
[ 991.679232] IIR: 0ff45280 ISR: 000003c0 IOR: f8c00000
[ 991.679232] CPU: 2 CR30: 17220940 CR31: 00000000
[ 991.679232] ORIG_R28: 00000000
[ 991.679232] IAOQ[0]: emulate_stw+0x5c/0x90
[ 991.679232] IAOQ[1]: emulate_stw+0x60/0x90
[ 991.679232] RP(r2): handle_unaligned+0x598/0x758
[ 991.679232] Backtrace:
[ 991.679232] [<10413c60>] handle_unaligned+0x598/0x758
[ 991.679232] [<10409854>] handle_interruption+0x1dc/0x7b8
[ 991.679232] [<10454dec>] sys_getcpu+0x30/0x6c
[ 991.679232]
[ 991.679232] Kernel panic - not syncing: Page fault: bad address
View: https://bugzilla.kernel.org/show_bug.cgi?id=219339#c1
You can reply to this message to join the discussion.
--
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)
next prev parent reply other threads:[~2024-10-01 15:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 15:00 calling getcpu with misaligned address causes kernel panic Colin Ian King via Bugspray Bot
2024-10-01 15:00 ` Colin Ian King via Bugspray Bot [this message]
2024-10-01 16:05 ` Helge Deller via Bugspray Bot
2024-10-01 17:45 ` Colin Ian King via Bugspray Bot
2024-10-01 22:20 ` Helge Deller via Bugspray Bot
2024-10-02 2:45 ` Helge Deller via Bugspray Bot
2024-10-08 20:20 ` Helge Deller via Bugspray Bot
2024-10-14 19:00 ` Helge Deller via Bugspray Bot
2024-10-15 9:15 ` Colin Ian King via Bugspray Bot
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=20241001-b219339c1-77ccff4939f9@bugzilla.kernel.org \
--to=bugbot@kernel.org \
--cc=James.Bottomley@HansenPartnership.com \
--cc=bugs@lists.linux.dev \
--cc=deller@gmx.de \
--cc=linux-parisc@vger.kernel.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.