mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Matthias Schiffer <mschiffer@universe-factory.net>,
	musl@lists.openwall.com, linux-mips@linux-mips.org,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: musl-libc/MIPS: detached thread exit broken since kernel commit 46e12c07b
Date: Fri, 19 Jun 2015 10:35:39 -0400	[thread overview]
Message-ID: <20150619143539.GU1173@brightrain.aerifal.cx> (raw)
In-Reply-To: <20150619100626.GB29960@linux-mips.org>

On Fri, Jun 19, 2015 at 12:06:26PM +0200, Ralf Baechle wrote:
> On Thu, Jun 18, 2015 at 10:50:32PM -0400, Rich Felker wrote:
> 
> > This is kernel ABI breakage that should be fixed -- people running old
> > kernel versions with old musl binaries might suffer a regression when
> > upgrading, and perhaps more importantly the failure mode is just
> > really bad. But I think we can also work around it on the userspace
> > side in musl by pointing the stack pointer at some rodata (or even at
> > pc, e.g. copying $25 to $sp) before making the syscall.
> 
> Just to be on the safe side, make sure it is something that's readable.  Core
> might me mapped execute-only, that is not readable and that is a feature
> which the affected kernels do support on suitable hardware.

How would that happen? Do you have ELF files with 3 PT_LOAD segments?
Normally there are two and their permissions are r-x and rw-.

Rich


      reply	other threads:[~2015-06-19 14:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19  2:07 Matthias Schiffer
2015-06-19  2:50 ` Rich Felker
2015-06-19 10:06   ` [musl] " Ralf Baechle
2015-06-19 14:35     ` Rich Felker [this message]

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=20150619143539.GU1173@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=mschiffer@universe-factory.net \
    --cc=musl@lists.openwall.com \
    --cc=ralf@linux-mips.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.
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).