From: Andreas Schwab <schwab@linux-m68k.org>
To: Philippe De Muyter <phdm@macqel.be>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Greg Ungerer <gerg@snapgear.com>,
Gavin Lambert <gavinl@compacsort.com>,
uClinux development list <uclinux-dev@uclinux.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: [uClinux-dev] [PATCH] m68k: Merge mmu and non-mmu versions of sys_call_table
Date: Thu, 07 Apr 2011 10:39:33 +0200 [thread overview]
Message-ID: <m3vcyqbgl6.fsf@linux-m68k.org> (raw)
In-Reply-To: <20110407083519.GA10282@frolo.macqel> (Philippe De Muyter's message of "Thu, 7 Apr 2011 10:35:19 +0200")
Philippe De Muyter <phdm@macqel.be> writes:
> On Thu, Apr 07, 2011 at 10:29:54AM +0200, Andreas Schwab wrote:
>> Geert Uytterhoeven <geert@linux-m68k.org> writes:
>>
>> > Isn't there a reason it was read-write on m68k, like the table may be changed
>> > at runtime (to install rootkits :-)? Have to check what the other arches do...
>>
>> Initially the syscall_table in Linux has always been writable, bb152f53
>> ("x86/x86_64: mark rodata section read-only: make some datastructures
>> const") made it read-only on x86. Apparently nobody bothered to do the
>> equivalent change on m68k (I don't think anything makes the kernel text
>> segment write protected anyway).
>
> Except, of course, ld config files who put text and rodata in ROM/FLASH for XIP
> on embedded systems.
I'm only talking about m68k here, not m68knommu.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2011-04-07 8:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 20:33 [PATCH] m68k: Merge mmu and non-mmu versions of sys_call_table Geert Uytterhoeven
2011-04-06 22:05 ` [uClinux-dev] " Philippe De Muyter
[not found] ` <20110406220510.GA17350@frolo.macqel>
2011-04-07 0:53 ` Greg Ungerer
2011-04-07 2:12 ` Gavin Lambert
[not found] ` <000301cbf4c9$40339fc0$c09adf40$@com>
2011-04-07 2:43 ` Greg Ungerer
2011-04-07 3:13 ` Gavin Lambert
2011-04-07 4:14 ` Greg Ungerer
[not found] ` <4D9D3A28.9060104@snapgear.com>
2011-04-07 7:04 ` Geert Uytterhoeven
2011-04-07 8:29 ` Andreas Schwab
2011-04-07 8:35 ` Philippe De Muyter
2011-04-07 8:39 ` Andreas Schwab [this message]
2011-04-13 18:03 ` Geert Uytterhoeven
2011-04-07 1:53 ` Greg Ungerer
2011-04-13 18:16 ` Geert Uytterhoeven
2011-04-17 20:13 ` Arnd Bergmann
2011-04-19 4:32 ` Greg Ungerer
2011-04-19 8:21 ` Arnd Bergmann
2011-04-19 8:30 ` Geert Uytterhoeven
2011-04-19 8:52 ` Arnd Bergmann
2011-04-19 12:26 ` Greg Ungerer
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=m3vcyqbgl6.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=gavinl@compacsort.com \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=phdm@macqel.be \
--cc=uclinux-dev@uclinux.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