From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 4/5] API: Add tst_clone
Date: Thu, 11 Feb 2021 16:30:29 +0100 [thread overview]
Message-ID: <YCVNlU3JRCddZ4Z9@yuki.lan> (raw)
In-Reply-To: <874kii63to.fsf@suse.de>
Hi!
> I don't know where you are getting EINVAL from?
>
> Try the following
>
> #include <errno.h>
> #include <unistd.h>
> #include <sys/syscall.h>
>
> int main(int argc, const char* argv[])
> {
> syscall(~0ULL);
>
> return errno;
> }
>
> It returns ENOSYS and strace shows this is not due to any sanity
> checking by glibc.
>
> I guess it would actually be a bug if it returned EINVAL although I am
> not sure this is specified anywhere.
And I guess that I got confused again. You get EINVAL when you pass
unsupported flags to a syscall, not unsupported syscall number.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2021-02-11 15:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 11:03 [LTP] [PATCH 0/5] Add close_range01, SAFE_DUP2 and SAFE_CLONE Richard Palethorpe
2021-02-11 11:03 ` [LTP] [PATCH 1/5] close_range: Add syscall number Richard Palethorpe
2021-02-11 11:03 ` [LTP] [PATCH 2/5] API: Add SAFE_DUP2 Richard Palethorpe
2021-02-11 11:03 ` [LTP] [PATCH 3/5] API: Fix clone.h Richard Palethorpe
2021-02-11 11:03 ` [LTP] [PATCH 4/5] API: Add tst_clone Richard Palethorpe
2021-02-11 12:51 ` Cyril Hrubis
2021-02-11 14:24 ` Richard Palethorpe
2021-02-11 14:35 ` Cyril Hrubis
2021-02-11 15:07 ` Richard Palethorpe
2021-02-11 15:30 ` Cyril Hrubis [this message]
2021-02-11 11:03 ` [LTP] [PATCH 5/5] close_range: Add test Richard Palethorpe
2021-02-11 12:54 ` Cyril Hrubis
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=YCVNlU3JRCddZ4Z9@yuki.lan \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.