Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200916142017.GB7854@voyager>
Date: Wed, 16 Sep 2020 16:20:17 +0200
From: Markus Wichmann <nullplan@....net>
To: musl@...ts.openwall.com
Subject: Re: Bug in mmap_fixed()

On Wed, Sep 16, 2020 at 12:15:23AM -0500, Rob Landley wrote:
> Coldfire is also nommu and musl has had m68k support for years, is there no
> coldfire target? (That's been supported by qemu longer than proper m68k.)

As stated in the OP, whether the buggy code even runs depends on
DL_NOMMU_SUPPORT, which as of yet only Super-H defines to 1. Even
if the buggy code runs, it will only bug out if a read() on a shared
library fails with EINTR, which is impossible during initial load (since
no signal handler can be installed), and almost impossible at runtime,
since shared libraries tend to be regular files, and only regular files
on an NFS share that has been setup to do interrupting I/O can ever
return EINTR. Even then, the first read() (that reads the ELF header and
the program headers) has to go off without a hitch, or else we won't
even come that far.

As far as I can tell, there is no special Coldfire target. If Coldfire
is incompatible with the M68k ABI (and from what I've just read, they
stripped a lot of features out of M68k to make Coldfire), then no, there
is no support for Coldfire.

Ciao,
Markus

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.