From: Joe Simmons-Talbott <josimmon@redhat.com>
To: libc-alpha@sourceware.org
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Szabolcs Nagy <szabolcs.nagy@arm.com>
Subject: Re: [PATCH v6 0/3] x86_64: aarch64: Set call number just before syscall
Date: Mon, 8 May 2023 10:13:02 -0400 [thread overview]
Message-ID: <20230508141302.GM2106608@oak> (raw)
In-Reply-To: <20230424150353.1469397-1-josimmon@redhat.com>
Is there anything further I need to do to get this patchset reviewed?
Thanks,
Joe
On Mon, Apr 24, 2023 at 11:03:50AM -0400, Joe Simmons-Talbott wrote:
> To make binary call tree analysis easier place the syscall number into
> the register just before the syscall is made. Only do this if the
> syscall number is a constant integer.
>
> Compiler optimizations can place quite a few instructions between the
> setting of the syscall number and the syscall instruction. During call
> tree analysis the number of instructions between the two can lead to
> more difficulty for both tools and humans in properly identifying the
> syscall number. Having the syscall number set in the prior instruction
> to the syscall instruction makes this task easier and less error prone.
> Being able to reliably identify syscalls made by a given API will make
> it easier to understand and verify the safety and security of glibc.
>
> Tested on x86_64 and aarch64.
>
> Chnages to v5:
> * aarch64: Remove '\n\t' from asm.
> * x86_64: Remove unused macros.
>
> Changes to v4:
> * aarch64: Move generated comment. Remove unused macros from earlier
> version.
>
> * Added patch
> - nptl: Convert indirect syscall numbers to compile time numeric
> values.
>
> Changes to v3:
> * x86_64: Combine two inline asms into one.
> - Suggested by "H.J. Lu" <hjl.tools@gmail.com>
>
> Changes to v2:
> * Add a more detailed commit message.
>
> Changes to v1:
> * aarch64: Combine two inline asms into one. Avoid loading name twice.
>
> Joe Simmons-Talbott (3):
> x86_64: Set the syscall register right before doing the syscall.
> aarch64: Set the syscall register right before doing the syscall.
> nptl: Use direct syscall numbers in setxid
>
> nptl/nptl_setxid.c | 136 ++++++++++++++++++++++-
> sysdeps/unix/sysv/linux/aarch64/sysdep.h | 29 +++--
> sysdeps/unix/sysv/linux/x86_64/sysdep.h | 24 ++--
> 3 files changed, 164 insertions(+), 25 deletions(-)
>
> --
> 2.39.2
>
prev parent reply other threads:[~2023-05-08 14:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 15:03 Joe Simmons-Talbott
2023-04-24 15:03 ` [PATCH v6 1/3] x86_64: Set the syscall register right before doing the syscall Joe Simmons-Talbott
2023-05-15 14:15 ` Joe Simmons-Talbott
2023-05-15 16:20 ` H.J. Lu
2023-05-25 18:07 ` Joe Simmons-Talbott
2023-05-25 18:40 ` Noah Goldstein
2023-05-26 7:04 ` Florian Weimer
2023-05-26 12:59 ` Joe Simmons-Talbott
2023-05-26 21:18 ` Noah Goldstein
2023-05-30 10:13 ` Florian Weimer
2023-05-31 18:23 ` Noah Goldstein
2023-06-28 19:17 ` Joe Simmons-Talbott
2023-04-24 15:03 ` [PATCH v6 2/3] aarch64: " Joe Simmons-Talbott
2023-05-09 7:47 ` Szabolcs Nagy
2023-04-24 15:03 ` [PATCH v6 3/3] nptl: Use direct syscall numbers in setxid Joe Simmons-Talbott
2023-04-24 15:17 ` Xi Ruoyao
2023-04-26 9:46 ` Szabolcs Nagy
2023-04-28 10:52 ` Florian Weimer
2023-04-26 12:39 ` Cristian Rodríguez
2023-04-26 13:24 ` Szabolcs Nagy
2023-05-25 18:07 ` Joe Simmons-Talbott
2023-05-08 14:13 ` Joe Simmons-Talbott [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=20230508141302.GM2106608@oak \
--to=josimmon@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=szabolcs.nagy@arm.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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).