From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Fri, 19 Jun 2015 12:06:36 +0200 (CEST) Received: from localhost.localdomain ([127.0.0.1]:53572 "EHLO linux-mips.org" rhost-flags-OK-OK-OK-FAIL) by eddie.linux-mips.org with ESMTP id S27006879AbbFSKGeMX4zq (ORCPT ); Fri, 19 Jun 2015 12:06:34 +0200 Received: from scotty.linux-mips.net (localhost.localdomain [127.0.0.1]) by scotty.linux-mips.net (8.15.1/8.14.8) with ESMTP id t5JA6Wj3031683; Fri, 19 Jun 2015 12:06:32 +0200 Received: (from ralf@localhost) by scotty.linux-mips.net (8.15.1/8.15.1/Submit) id t5JA6QWK031674; Fri, 19 Jun 2015 12:06:26 +0200 Date: Fri, 19 Jun 2015 12:06:26 +0200 From: Ralf Baechle To: Rich Felker Cc: Matthias Schiffer , musl@lists.openwall.com, linux-mips@linux-mips.org, "linux-kernel@vger.kernel.org" Subject: Re: [musl] musl-libc/MIPS: detached thread exit broken since kernel commit 46e12c07b Message-ID: <20150619100626.GB29960@linux-mips.org> References: <55837978.7020801@universe-factory.net> <20150619025032.GR1173@brightrain.aerifal.cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150619025032.GR1173@brightrain.aerifal.cx> User-Agent: Mutt/1.5.23 (2014-03-12) Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 47978 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: ralf@linux-mips.org Precedence: bulk List-help: List-unsubscribe: List-software: Ecartis version 1.0.0 List-Id: linux-mips X-List-ID: linux-mips List-subscribe: List-owner: List-post: List-archive: X-list: linux-mips 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. Ralf