From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>
Subject: Re: V2 [PATCH 2/2] Add C wrappers for prctl/process_vm_readv/process_vm_writev [BZ #25810]
Date: Wed, 29 Apr 2020 17:35:04 +0200 [thread overview]
Message-ID: <87ees6qp93.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOraBmZBLgAiAJ2r4rVTz0cKMQYekb_2YzVrz-QYckJfng@mail.gmail.com> (H. J. Lu's message of "Wed, 29 Apr 2020 08:29:25 -0700")
* H. J. Lu:
> With
>
> extern int __prctl (int __option, ...);
> libc_hidden_proto (__prctl)
> libc_hidden_proto (prctl)
>
> and
>
> #include <unistd.h>
> #include <sysdep.h>
> #include <errno.h>
> #include <sys/prctl.h>
>
> int
> __prctl (int option, unsigned long int arg2, unsigned long int arg3,
> unsigned long int arg4, unsigned long int arg5)
> {
> return INLINE_SYSCALL_CALL (prctl, option, arg2, arg3, arg4, arg5);
> }
>
> libc_hidden_def (__prctl)
> weak_alias (__prctl, prctl)
> hidden_weak (prctl)
Please try:
extern int __prctl (int __option, ...);
libc_hidden_proto (__prctl)
And:
int
__prctl (int option, unsigned long int arg2, unsigned long int arg3,
unsigned long int arg4, unsigned long int arg5)
{
return INLINE_SYSCALL_CALL (prctl, option, arg2, arg3, arg4, arg5);
}
libc_hidden_def (__prctl)
strong_alias (__prctl, prctl)
Internal users should always use __prctl to avoid linknamespace
failures, so there are no callers of prctl and we don't need a hidden
alias for it.
>> > Since the the U marker can only be applied to 2 unsigned long arguments,
>> > add a C wrapper for prctl, process_vm_readv and process_vm_writev syscals
>> > which have more than 2 unsigned long arguments.
>>
>> Please add that syscalls.list reference. Thanks.
>>
>
> I have
>
> ---
> Since the the U marker can only be applied to 2 unsigned long arguments
> in syscalls.list files, add a C wrapper for prctl, process_vm_readv and
> process_vm_writev syscals which have more than 2 unsigned long arguments.
> ---
Nice.
Thanks,
Florian
next prev parent reply other threads:[~2020-04-29 15:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 14:47 [PATCH 1/2] Mark unsigned long arguments with U in more syscalls " H.J. Lu
2020-04-29 14:47 ` [PATCH 2/2] Add C wrappers for prctl/process_vm_readv/process_vm_writev " H.J. Lu
2020-04-29 14:55 ` Florian Weimer
2020-04-29 15:20 ` V2 " H.J. Lu
2020-04-29 15:22 ` Florian Weimer
2020-04-29 15:29 ` H.J. Lu
2020-04-29 15:35 ` Florian Weimer [this message]
2020-04-29 15:41 ` Florian Weimer
2020-04-29 15:32 ` Andreas Schwab
2020-04-29 15:36 ` H.J. Lu
2020-04-29 15:43 ` Florian Weimer
2020-04-29 15:52 ` Add C wrappers for process_vm_readv/process_vm_writev " H.J. Lu
2020-04-29 15:55 ` Florian Weimer
2020-04-29 14:58 ` [PATCH 2/2] Add C wrappers for prctl/process_vm_readv/process_vm_writev " Florian Weimer
2020-04-29 15:10 ` H.J. Lu
2020-04-29 15:18 ` Florian Weimer
2020-04-29 15:22 ` H.J. Lu
2020-04-29 15:25 ` Florian Weimer
2020-04-29 14:57 ` [PATCH 1/2] Mark unsigned long arguments with U in more syscalls " Florian Weimer
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=87ees6qp93.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.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.
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).