From: Nicholas Piggin <npiggin@gmail.com>
To: "Dmitry V. Levin" <ldv@altlinux.org>
Cc: Rich Felker <dalias@libc.org>,
Joakim Tjernlund <Joakim.Tjernlund@infinera.com>,
linux-api@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Michael Ellerman <mpe@ellerman.id.au>,
musl@lists.openwall.com,
Segher Boessenkool <segher@kernel.crashing.org>
Subject: [musl] Re: Linux powerpc new system call instruction and ABI
Date: Thu, 20 May 2021 17:20:44 +1000 [thread overview]
Message-ID: <1621495199.91bc4mp4tb.astroid@bobo.none> (raw)
In-Reply-To: <20210520025948.GA27081@altlinux.org>
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 the new syscall I/F?
>> >>
>> >> No, it's a new independent interface.
>> >
>> > 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.
>>
>> It is an ABI break, that was known. The ptrace info stuff I fixed with
>> the patch earlier was obviously a bug in my initial implementation and
>> not intended (sorry my ptrace testing was not sufficient, and thanks for
>> reporting it, by the way).
>
> 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.
>
> 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.
prev parent reply other threads:[~2021-05-20 7:21 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-11 8:12 [musl] " Nicholas Piggin
2020-06-11 8:12 ` [musl] [PATCH 1/2] powerpc/64s/exception: treat NIA below __end_interrupts as soft-masked Nicholas Piggin
2020-07-24 13:25 ` [musl] " Michael Ellerman
2020-06-11 8:12 ` [musl] [PATCH 2/2] powerpc/64s: system call support for scv/rfscv instructions Nicholas Piggin
2020-07-23 6:47 ` [musl] " Michael Ellerman
2020-07-23 16:48 ` Christophe Leroy
2020-07-24 10:45 ` Michael Ellerman
2020-06-11 21:02 ` [musl] Re: Linux powerpc new system call instruction and ABI Segher Boessenkool
2020-06-14 9:26 ` Nicholas Piggin
2021-05-18 23:13 ` Dmitry V. Levin
2021-05-19 2:50 ` Nicholas Piggin
2021-05-19 5:01 ` Nicholas Piggin
2021-05-21 19:40 ` Matheus Castanho
2021-05-21 19:52 ` Florian Weimer
2021-05-21 20:00 ` Matheus Castanho
2021-05-21 20:52 ` Dmitry V. Levin
2021-05-24 12:11 ` Matheus Castanho
2021-05-24 20:33 ` Matheus Castanho
2021-05-19 10:24 ` Dmitry V. Levin
2021-05-19 10:59 ` Nicholas Piggin
2021-05-19 12:39 ` Tulio Magno Quites Machado Filho
2021-05-19 13:26 ` Dmitry V. Levin
2021-05-19 22:51 ` Nicholas Piggin
2021-05-19 23:27 ` Dmitry V. Levin
2021-05-20 2:40 ` Nicholas Piggin
2021-05-20 3:06 ` Dmitry V. Levin
2021-05-20 5:12 ` Nicholas Piggin
2021-05-19 7:33 ` Joakim Tjernlund
2021-05-19 7:55 ` Nicholas Piggin
2021-05-19 8:08 ` Joakim Tjernlund
2021-05-19 8:42 ` Nicholas Piggin
2021-05-19 11:12 ` Nicholas Piggin
2021-05-19 14:38 ` Segher Boessenkool
2021-05-19 15:06 ` Joakim Tjernlund
2021-05-19 15:22 ` Segher Boessenkool
2021-05-19 15:36 ` Rich Felker
2021-05-19 18:09 ` Joakim Tjernlund
2021-05-19 23:48 ` Rich Felker
2021-05-20 1:06 ` Dmitry V. Levin
2021-05-20 2:45 ` Nicholas Piggin
2021-05-20 2:59 ` Dmitry V. Levin
2021-05-20 7:20 ` Nicholas Piggin [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=1621495199.91bc4mp4tb.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=Joakim.Tjernlund@infinera.com \
--cc=dalias@libc.org \
--cc=ldv@altlinux.org \
--cc=linux-api@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=musl@lists.openwall.com \
--cc=segher@kernel.crashing.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).