unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fweimer@redhat.com>,
	Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
Cc: "Alexandra Hájková" <ahajkova@redhat.com>
Subject: Re: [PATCH] Linux: Add execveat system call wrapper
Date: Fri, 27 Nov 2020 14:38:50 -0300	[thread overview]
Message-ID: <27f7a855-f3b6-62b8-0ffb-99603f72009d@linaro.org> (raw)
In-Reply-To: <871rgeiu2s.fsf@oldenburg2.str.redhat.com>



On 27/11/2020 14:32, Florian Weimer wrote:
> * Adhemerval Zanella via Libc-alpha:
> 
>>> +{
>>> +  /* Avoid implicit array coercion in syscall macros.  */
>>> +  INLINE_SYSCALL_CALL (execveat, dirfd, path, &argv[0], &envp[0], flags);
>>> +#ifndef __ASSUME_EXECVEAT
>>> +  if (errno != ENOSYS)
>>> +    return -1;
>>
>> You need get the INLINE_SYSCALL_CALL and check if it was sucessful as well,
>> instead of just check for the errno value. Also, this implementation always 
>> return '-1' (as below):
>>
>>     int r = INLINE_SYSCALL_CALL (execveat, dirfd, path, &argv[0], &envp[0],
>>                                  flags);
>>   #if __ASSUME_EXECVEAT
>>     return r;
>>   #else
>>     if (r == 0 || errno != ENOSYS)
>>       return r;
>>     [...]
> 
>>> +  return -1;
>>> +}
>>
>> This will make the function always return -1.  Hasn't it shown in
>> testing?
> 
> This is the expected behavior for execve and execveat.  It does not
> return successfully, which is why it is not necessary to check the value
> of the INLINE_SYSCALL_CALL macro, either.

Right, forgot about the non return in case of success. So please ignore
that part of the review.


  reply	other threads:[~2020-11-27 17:38 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28 12:20 [PATCH] Linux: Add execveat system call wrapper Alexandra Hájková via Libc-alpha
2020-04-28 14:17 ` Florian Weimer
2020-04-28 15:03   ` Joseph Myers
2020-04-28 15:03 ` Joseph Myers
2020-04-28 15:08   ` Florian Weimer
2020-04-28 15:29     ` Joseph Myers
2020-04-28 17:15       ` Florian Weimer
2020-04-28 17:19         ` Joseph Myers
2020-04-28 17:44 ` Adhemerval Zanella via Libc-alpha
2020-04-28 17:50   ` Florian Weimer
2020-04-28 18:31     ` Adhemerval Zanella via Libc-alpha
2020-04-30 11:15 ` Florian Weimer via Libc-alpha
2020-04-30 12:28   ` Adhemerval Zanella via Libc-alpha
2020-04-30 12:55     ` Florian Weimer via Libc-alpha
2020-04-30 19:03       ` Adhemerval Zanella via Libc-alpha
2020-04-30 12:32 ` Adhemerval Zanella via Libc-alpha
2020-11-06 21:03 ` Alexandra Hájková via Libc-alpha
2020-11-06 22:15   ` Joseph Myers
2020-11-09 18:43     ` Florian Weimer via Libc-alpha
2020-11-09 21:34   ` Yann Droneaud
2020-11-26 11:31     ` Alexandra Petlanova Hajkova via Libc-alpha
2020-11-09 20:39 ` Adhemerval Zanella via Libc-alpha
2020-12-03 13:55   ` Florian Weimer via Libc-alpha
2020-11-26 21:28 ` Alexandra Hájková via Libc-alpha
2020-11-27 14:58   ` Adhemerval Zanella via Libc-alpha
2020-11-27 17:32     ` Florian Weimer via Libc-alpha
2020-11-27 17:38       ` Adhemerval Zanella via Libc-alpha [this message]
2020-12-03 14:20 ` Alexandra Hájková via Libc-alpha
2020-12-03 14:37   ` Andreas Schwab
2020-12-08 14:44   ` Adhemerval Zanella via Libc-alpha
2020-12-08 15:18     ` Florian Weimer via Libc-alpha
2020-12-08 16:41       ` Adhemerval Zanella via Libc-alpha
2021-03-15 21:42 ` Alexandra Hájková via Libc-alpha
2021-03-15 22:12   ` Joseph Myers
2021-03-15 22:17   ` Dmitry V. Levin
2021-03-24 13:54 ` Alexandra Hájková via Libc-alpha
2021-03-26 20:36   ` Adhemerval Zanella via Libc-alpha
2021-04-02 12:13     ` Alexandra Hájková via Libc-alpha
2021-04-02 13:29       ` Adhemerval Zanella via Libc-alpha
2021-04-05 16:32 ` Alexandra Hájková via Libc-alpha
2021-04-12 10:26   ` Alexandra Hájková via Libc-alpha
2021-04-12 11:14   ` Andreas Schwab
2021-04-12 19:26 ` Alexandra Hájková via Libc-alpha
2021-04-13 19:27   ` Adhemerval Zanella via Libc-alpha
2021-04-21 18:11 ` Alexandra Hájková via Libc-alpha
2021-05-03 19:20   ` Adhemerval Zanella via Libc-alpha

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=27f7a855-f3b6-62b8-0ffb-99603f72009d@linaro.org \
    --to=libc-alpha@sourceware.org \
    --cc=adhemerval.zanella@linaro.org \
    --cc=ahajkova@redhat.com \
    --cc=fweimer@redhat.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).