From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] getrlimit/getrlimit03: new test for underlying syscall variants
Date: Tue, 27 Nov 2018 18:41:56 +0100 [thread overview]
Message-ID: <20181127174156.GA19801@dell5510> (raw)
In-Reply-To: <20181107212213.129534-1-ghackmann@google.com>
Hi Greg,
> Depending on the architecture, Linux provides up to three syscalls that
> have been used to implement getrlimit(2) in different libc
> implementations. These syscalls differ in the size and signedness of
> rlim_t.
> This test compares the results returned by all three syscalls, confirming
> that they either match or were appropriately capped at the respective
> RLIM_INFINITY constant.
> Signed-off-by: Greg Hackmann <ghackmann@google.com>
> ---
Thanks for your patch, pushed with minor GPL related change (replaced GPL text
with SPDX-License-Identifier).
Kind regards,
Petr
prev parent reply other threads:[~2018-11-27 17:41 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
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 [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=20181127174156.GA19801@dell5510 \
--to=pvorel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox