mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Markus Wichmann <nullplan@gmx.net>
To: musl@lists.openwall.com
Subject: Re: [musl] Bug in mmap_fixed()
Date: Wed, 16 Sep 2020 16:20:17 +0200	[thread overview]
Message-ID: <20200916142017.GB7854@voyager> (raw)
In-Reply-To: <edf21bae-73a9-f082-2cf2-d90b5e4e03bf@landley.net>

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

  parent reply	other threads:[~2020-09-16 14:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-04 19:52 Markus Wichmann
2020-09-05  3:41 ` Rich Felker
2020-09-05  6:44   ` Markus Wichmann
2020-09-16  5:15     ` Rob Landley
2020-09-16 12:04       ` Rich Felker
2020-09-16 14:20       ` Markus Wichmann [this message]
2020-09-05  8:39 ` Stefan O'Rear

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=20200916142017.GB7854@voyager \
    --to=nullplan@gmx.net \
    --cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/musl/

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).