From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 3712 invoked from network); 20 May 2021 07:21:06 -0000 Received: from mother.openwall.net (195.42.179.200) by inbox.vuxu.org with ESMTPUTF8; 20 May 2021 07:21:06 -0000 Received: (qmail 17626 invoked by uid 550); 20 May 2021 07:21:03 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Reply-To: musl@lists.openwall.com Received: (qmail 17595 invoked from network); 20 May 2021 07:21:03 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:subject:to:cc:references:in-reply-to:mime-version :message-id:content-transfer-encoding; bh=1a8BUw6AmeU9jhk87302iJ+1G3wTSv+KqaggD9Jw1iM=; b=CKkNwQcLmL9XT1YxqvpiT4WQqkLq6fl1hYX4Xob56iKlCTwzeudFh6yA4JqDw/4gq5 q4PmUVIZMDmsWnktlag2cO+kRIUupe3EWQAdh0Gem92MgNjItFfQpEMUS1Guyvbjqyyz OS9ztbZmm/tU23FsNi2NFVFxt2CjJmNNNRMnYQhMqZ+vZGKiQQVN3glRMc3AbcNOqVN2 nMO+tqq1T1JKkUv6cnJfuc0AqgOxCSp5ndUC6ksSjljp8jmU2tFbsYEai0OXcQrRDt7p mgQAS2D1jQzqVVDsns0EbJnj0iHP0ScoV8y8qLBdxRs+O9pluoBgwl5IPHcc4V9wiAO3 Tz4w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:subject:to:cc:references:in-reply-to :mime-version:message-id:content-transfer-encoding; bh=1a8BUw6AmeU9jhk87302iJ+1G3wTSv+KqaggD9Jw1iM=; b=QDAeRANq6vTC+B16xKikn6nN373rs96bsKat5GIeyV3gwnGt3Y9mikkReCV75Sq2Uv +h22kz4r7JEyrMZanc5yw2larVwuzXPbk4pvMXzu7IX3DhlY9p5d29s6KgzyM2G5CO6a 5uT3ywVa4RvOFlvg1VAR4MceGHyXEtHXpqV89HF5S0+IaYT4Nao9a1zqoLcnucRSKxxe Yg5xBrN1k0djGALTznJR6sti0dkef2pXkrNDDggvxriYmpG++FuoSr55AnngpRKP2ErP cn7zc6q6LcWz2wLI0rH73r5yBz5zy6AM/losmOuHs/L9UPkMqyBDCG4VvCPcCULIQx5M L/pw== X-Gm-Message-State: AOAM533+NcGSPnTSEUbJXT4pUrrWRe7H1K+ZOA5J2+i+P7/RiCcznVA0 pDdAFgJKM1b8LlZIoilMT/E= X-Google-Smtp-Source: ABdhPJwVWmrn/1S+RJBq0TSn/TxhD0DfUJPNLQu3qiX7wTQBZhgAvAEp7yTpQcWX0uzXnRImCKzY1Q== X-Received: by 2002:a17:902:e812:b029:f0:aa50:2f1d with SMTP id u18-20020a170902e812b02900f0aa502f1dmr4167957plg.79.1621495250742; Thu, 20 May 2021 00:20:50 -0700 (PDT) Date: Thu, 20 May 2021 17:20:44 +1000 From: Nicholas Piggin To: "Dmitry V. Levin" Cc: Rich Felker , Joakim Tjernlund , linux-api@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, Michael Ellerman , musl@lists.openwall.com, Segher Boessenkool References: <1621410291.c7si38sa9q.astroid@bobo.none> <1621413143.oec64jaci5.astroid@bobo.none> <20210519143836.GJ10366@gate.crashing.org> <11d62aa2488e51ec00fe77f24a1d7cdcc21af0b8.camel@infinera.com> <20210519152205.GL10366@gate.crashing.org> <20210519234846.GS2546@brightrain.aerifal.cx> <20210520010612.GA25599@altlinux.org> <1621478448.743zqcrxza.astroid@bobo.none> <20210520025948.GA27081@altlinux.org> In-Reply-To: <20210520025948.GA27081@altlinux.org> MIME-Version: 1.0 Message-Id: <1621495199.91bc4mp4tb.astroid@bobo.none> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: [musl] Re: Linux powerpc new system call instruction and ABI Excerpts from Dmitry V. Levin's message of May 20, 2021 12:59 pm: > On Thu, May 20, 2021 at 12:45:57PM +1000, Nicholas Piggin wrote: >> Excerpts from Dmitry V. Levin's message of May 20, 2021 11:06 am: >> > On Wed, May 19, 2021 at 07:48:47PM -0400, Rich Felker wrote: >> >> On Wed, May 19, 2021 at 06:09:25PM +0000, Joakim Tjernlund wrote: >> > [...] >> >> > W.r.t breaking ABI, isn't that what PowerPC is trying to do with th= e new syscall I/F?=20 >> >>=20 >> >> No, it's a new independent interface. >> >=20 >> > Unfortunately, being a new independent interface doesn't mean it isn't >> > an ABI break. In fact, it was a severe ABI break, and this thread is >> > an attempt to find a hotfix. >>=20 >> It is an ABI break, that was known. The ptrace info stuff I fixed with=20 >> the patch earlier was obviously a bug in my initial implementation and=20 >> not intended (sorry my ptrace testing was not sufficient, and thanks for >> reporting it, by the way). >=20 > Could you check whether tools/testing/selftests/ptrace/get_syscall_info.c > passes again with your fix, please? It does. Thanks, Nick > If yes, then PTRACE_GET_SYSCALL_INFO is fixed. >=20 > By the way, kernel tracing and audit subsystems also use those functions > from asm/syscall.h and asm/ptrace.h, so your ptrace fix is likely to fix > these subsystems as well.