From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] getrlimit/getrlimit03: new test for underlying syscall variants
Date: Tue, 6 Nov 2018 14:45:13 -0500 (EST) [thread overview]
Message-ID: <629612842.70327511.1541533513279.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20181106180804.163305-1-ghackmann@google.com>
----- Original Message -----
<snip>
> +const uint64_t RLIM_INFINITY_U64 = UINT64_MAX;
> +
> +static int getrlimit_u64(int resource, struct rlimit64 *rlim)
> +{
> + return syscall(__NR_prlimit64, 0, resource, NULL, rlim);
Hi,
(Likely an issue for old distro kernels, but)
consider using ltp_syscall here, or in setup(). Syscall __NR defines
come from LTP, so those will be always present, but syscall can still
be unsupported by kernel, so test can end up comparing with 'ENOSYS'.
Regards,
Jan
next prev parent reply other threads:[~2018-11-06 19:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-06 18:08 [LTP] [PATCH] getrlimit/getrlimit03: new test for underlying syscall variants Greg Hackmann
2018-11-06 19:45 ` Jan Stancek [this message]
2018-11-06 19:47 ` Cyril Hrubis
2018-11-07 21:11 ` Greg Hackmann
2018-11-07 21:22 ` [LTP] [PATCH v2] " Greg Hackmann
2018-11-09 11:34 ` Jan Stancek
2018-11-27 17:41 ` Petr Vorel
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=629612842.70327511.1541533513279.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox