From: Alan Maguire <alan.maguire@oracle.com>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: ast@kernel.org, daniel@iogearbox.net, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, brauner@kernel.org,
bboscaccy@linux.microsoft.com, ameryhung@gmail.com,
emil@etsalapatis.com, bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: more open-coded gettid syscall cleanup
Date: Thu, 11 Sep 2025 16:20:10 +0100 [thread overview]
Message-ID: <7d6aca1e-3997-4fa6-bbf4-d5afd058b7e1@oracle.com> (raw)
In-Reply-To: <CAEf4BzZ6+BgDQANDjU2BEwOj6oGf+GuvCN+3UmD7BYRh96K31A@mail.gmail.com>
On 11/09/2025 15:12, Andrii Nakryiko wrote:
> On Thu, Sep 11, 2025 at 3:33 AM Alan Maguire <alan.maguire@oracle.com> wrote:
>>
>> commit 0e2fb011a0ba ("selftests/bpf: Clean up open-coded gettid syscall invocations")
>>
>> addressed the issue that older libc may not have a gettid()
>> function call wrapper for the associated syscall. A few more
>> instances have crept into tests, use sys_gettid() instead.
>
> we can poison gettid() to avoid this in the future?
>
good idea; I'll send a v2 doing this. Thanks!
Alan
prev parent reply other threads:[~2025-09-11 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 7:33 [PATCH bpf-next] selftests/bpf: more open-coded gettid syscall cleanup Alan Maguire
2025-09-11 14:12 ` Andrii Nakryiko
2025-09-11 15:20 ` Alan Maguire [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=7d6aca1e-3997-4fa6-bbf4-d5afd058b7e1@oracle.com \
--to=alan.maguire@oracle.com \
--cc=ameryhung@gmail.com \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bboscaccy@linux.microsoft.com \
--cc=bpf@vger.kernel.org \
--cc=brauner@kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=emil@etsalapatis.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=martin.lau@linux.dev \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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