From: Finn Thain <fthain@linux-m68k.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Debian PowerPC <debian-powerpc@lists.debian.org>,
linuxppc-dev@lists.ozlabs.org, Stan Johnson <userm57@yahoo.com>
Subject: Re: Debian SID kernel doesn't boot on PowerBook 3400c
Date: Wed, 4 Aug 2021 10:34:25 +1000 (AEST) [thread overview]
Message-ID: <c535cc2b-3f45-2415-1e81-32ea24b4ec@linux-m68k.org> (raw)
In-Reply-To: <fac98e72-14a1-802e-8343-9bed9a6eaedc@csgroup.eu>
On Tue, 3 Aug 2021, Christophe Leroy wrote:
>
> Looks like the memory errors are linked to KUAP (Kernel Userspace Access
> Protection). Based on the places the problems happen, I don't think
> there are any invalid access, so there must be something wrong in the
> KUAP logic, probably linked to some interrupts happenning in kernel mode
> while the KUAP window is opened. And because is not selected by default
> on book3s/32 until 5.14, probably nobody ever tested it in a real
> environment before you.
>
> I think the issue may be linked to commit
> https://github.com/linuxppc/linux/commit/c16728835 which happened
> between 5.12 and 5.13.
The messages, "Kernel attempted to write user page (c6207c) - exploit
attempt? (uid: 0)", appear in the console logs generated by v5.13. Those
logs come from the Powerbook G3 discussion in the other thread. Could that
be the same bug?
next prev parent reply other threads:[~2021-08-04 0:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <60841a75-ed7c-8789-15db-272bf43055f5.ref@yahoo.com>
[not found] ` <60841a75-ed7c-8789-15db-272bf43055f5@yahoo.com>
2021-07-31 15:58 ` Debian SID kernel doesn't boot on PowerBook 3400c Christophe Leroy
2021-07-31 18:24 ` Stan Johnson
2021-08-02 14:41 ` Christophe Leroy
2021-08-02 17:32 ` Stan Johnson
2021-08-03 10:08 ` Christophe Leroy
2021-08-03 22:20 ` Stan Johnson
2021-08-04 0:02 ` Finn Thain
2021-08-04 0:34 ` Finn Thain [this message]
2021-08-04 6:28 ` Christophe Leroy
[not found] ` <f6a3746e-80ef-a6b3-925a-69aed01ba98c@linux-m68k.org>
[not found] ` <b6fe0c8e-8af5-e0e9-629b-fce61750ec2e@yahoo.com>
[not found] ` <4ac28304-4519-fb8a-a868-e8c79cb5f9e4@yahoo.com>
[not found] ` <7532219a-4fd0-416-6365-304033fa6abd@linux-m68k.org>
[not found] ` <9659419d-da9e-5aa6-ffbb-758748e2d6e9@linux-m68k.org>
[not found] ` <2eb2b452-51d5-c495-3ffe-896c62a1633f@yahoo.com>
[not found] ` <da9c16b4-70bc-6fe0-ad5c-8b226ca08b23@yahoo.com>
[not found] ` <cc5a203f-9df5-a0b-a4d7-bcaddde777d5@linux-m68k.org>
[not found] ` <6ea50cd7-84d3-5180-0430-1211aaf0e308@yahoo.com>
2021-08-06 1:06 ` Finn Thain
2021-08-06 6:09 ` Christophe Leroy
2021-08-06 9:43 ` Finn Thain
2021-08-06 9:58 ` Christophe Leroy
2021-08-07 2:05 ` Finn Thain
[not found] ` <06ddf5ab-b0c9-1c64-92ea-a9cfbfb9f3b0@yahoo.com>
2021-08-07 4:08 ` Finn Thain
2021-08-07 13:09 ` Stan Johnson
2021-08-07 14:35 ` Christophe Leroy
2021-08-07 16:26 ` Stan Johnson
2021-08-07 17:08 ` Christophe Leroy
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=c535cc2b-3f45-2415-1e81-32ea24b4ec@linux-m68k.org \
--to=fthain@linux-m68k.org \
--cc=christophe.leroy@csgroup.eu \
--cc=debian-powerpc@lists.debian.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=userm57@yahoo.com \
/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).