public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: Adhemerval Zanella Netto <adhemerval.zanella@linaro.org>
Cc: enh <enh@google.com>,  Florian Weimer <fweimer@redhat.com>,
	 Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>,
	 Stafford Horne <shorne@gmail.com>
Subject: Re: [PATCH 3/6] linux: Implement mremap in C
Date: Fri, 07 Jun 2024 09:51:02 +0100	[thread overview]
Message-ID: <8734ppnnk9.fsf@gentoo.org> (raw)
In-Reply-To: <878qzhno15.fsf@gentoo.org> (Sam James's message of "Fri, 07 Jun 2024 09:40:54 +0100")

[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]

Sam James <sam@gentoo.org> writes:

> Adhemerval Zanella Netto <adhemerval.zanella@linaro.org> writes:
>
>> On 06/06/24 16:38, enh wrote:
>>> On Thu, Jun 6, 2024 at 12:01 PM enh <enh@google.com> wrote:
>>>>
>>>> On Thu, Jun 6, 2024 at 11:15 AM Florian Weimer <fweimer@redhat.com> wrote:
>>>>>
>>>>> * Adhemerval Zanella via Libc-alpha:
>>>>>
>>>>>> Variadic function calls in syscalls.list does not work for all ABIs
>>>>>> (for instance where the argument are passed on the stack instead of
>>>>>> registers) and might have underlying issues depending of the variadic
>>>>>> type (for instance if a 64-bit argument is used).
>>>>>>
>>>>>> Checked on x86_64-linux-gnu.
>>>>>
>>>>> Where exactly does this break?
>>
>> I don't really recall to be honest.
>
> The only tangentially recent incident I remember is in Asahi Linux:
> * https://bugzilla.mozilla.org/show_bug.cgi?id=1832770
> * https://issues.webrtc.org/issues/42225490
>
> (We also had a few cases in Gentoo, but that was on Darwin with Apple's
> ARM64 ABI.)

Oh, nevermind, I see Florian mentioned this.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

  reply	other threads:[~2024-06-07  8:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-22 18:54 [PATCH 0/6] linux: Some syscall refactors Adhemerval Zanella
2021-11-22 18:54 ` [PATCH 1/6] linux: Add fanotify_mark C implementation Adhemerval Zanella
2021-11-24 21:45   ` Stafford Horne
2021-11-25 12:55     ` Adhemerval Zanella
2021-11-22 18:54 ` [PATCH 2/6] linux: Add prlimit64 " Adhemerval Zanella
2021-11-25 23:39   ` Stafford Horne
2021-11-30 11:51     ` Adhemerval Zanella
2021-11-22 18:54 ` [PATCH 3/6] linux: Implement mremap in C Adhemerval Zanella
2021-11-26  0:26   ` Stafford Horne
2021-11-30 11:55     ` Adhemerval Zanella
2024-06-06 15:15   ` Florian Weimer
2024-06-06 16:01     ` enh
2024-06-06 19:38       ` enh
2024-06-06 20:26         ` Adhemerval Zanella Netto
2024-06-07  8:40           ` Sam James
2024-06-07  8:51             ` Sam James [this message]
2024-06-07  9:06           ` Xi Ruoyao
2021-11-22 18:54 ` [PATCH 4/6] linux: Implement pipe in terms of __NR_pipe2 Adhemerval Zanella
2021-11-26 23:03   ` Stafford Horne
2021-11-30 14:53     ` Adhemerval Zanella
2021-11-22 18:54 ` [PATCH 5/6] linux: Add generic syscall implementation Adhemerval Zanella
2021-11-22 18:54 ` [PATCH 6/6] linux: Add generic ioctl implementation Adhemerval Zanella
2021-12-04  7:50   ` Stafford Horne

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=8734ppnnk9.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=enh@google.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=shorne@gmail.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).