Linux M68K Architecture development
 help / color / mirror / Atom feed
From: Michael Schmitz <schmitzmic@gmail.com>
To: Daniel Palmer <daniel@thingy.jp>, Greg Ungerer <gerg@kernel.org>
Cc: geert@linux-m68k.org, linux-m68k@lists.linux-m68k.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Implement kernel memory protection
Date: Tue, 18 Nov 2025 06:41:08 +1300	[thread overview]
Message-ID: <126822f3-6f11-d02d-43f8-1b5e6bcc910a@gmail.com> (raw)
In-Reply-To: <CAFr9PXkzhEEsSUXWCtpHaX6DWEKzX=xCESSpzbSFoJgf8mrz4A@mail.gmail.com>

Daniel,

take a look at arch/m68k/kernel/head.S - 030 MMU setup uses early 
termination descriptors for kernel memory, _not_ regular page tables.

Cheers,

	Michael


Am 17.11.2025 um 22:42 schrieb Daniel Palmer:
> Hi Greg,
>
> On Mon, 17 Nov 2025 at 12:04, Greg Ungerer <gerg@kernel.org> wrote:
>> Seems to work fine on real ColdFire hardware (tested on an M5475 -
>> that is one that has an MMU):
>
> Thanks for testing. I just tried on my MVME147 (030) and the marking
> RO seems to work but it locks up starting init:
>
> [    6.520000] devtmpfs: mounted
> [    6.540000] Freeing unused kernel image (initmem) memory: 120K
> [    6.550000] Write protecting kernel text: 0x2000 - 0x3676f0
> [    6.560000] Write protecting kernel read-only data: 0x36a000 - 0x3be000
> [    6.580000] rodata_test: all tests were successful
> [    6.590000] Run /sbin/init as init process
> <dead>
>
> My 060 Amiga 4000 seems ok. So I guess some 030 mmu issue. I'll debug
> and send again..
>
> Thanks!
>
> Daniel
>

  reply	other threads:[~2025-11-17 17:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-16 22:05 [PATCH] m68k: Implement kernel memory protection Daniel Palmer
2025-11-17  3:04 ` Greg Ungerer
2025-11-17  9:42   ` Daniel Palmer
2025-11-17 17:41     ` Michael Schmitz [this message]
2025-11-17 22:01       ` Daniel Palmer
2025-11-17 23:14         ` Michael Schmitz
2025-11-18 10:55           ` Daniel Palmer

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=126822f3-6f11-d02d-43f8-1b5e6bcc910a@gmail.com \
    --to=schmitzmic@gmail.com \
    --cc=daniel@thingy.jp \
    --cc=geert@linux-m68k.org \
    --cc=gerg@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox