From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] acct02: relax ac_btime checks
Date: Tue, 12 Nov 2019 13:37:44 +0100 [thread overview]
Message-ID: <20191112123744.GA760@dell5510> (raw)
In-Reply-To: <95d94fede00533a07fc604de3252636b094fc8f8.1573550061.git.jstancek@redhat.com>
Hi Jan,
> ac_btime is calculated back from current time and isn't accurate.
> Problems include nanoseconds accumulation (lags behind gettimeofday),
> suspend/resume isn't taken into account and any adjtime() (like DST
> change) will cause ac_btime to jump as well.
> Relax the condition to ~2h around gettimeofday value at start of
> the test. That should be enough to cover usual DST time jumps.
> Signed-off-by: Jan Stancek <jstancek@redhat.com>
Reviewed-by: Petr Vorel <pvorel@suse.cz>
Tested-by: Petr Vorel <pvorel@suse.cz>
on both 390x and intel.
LGTM, although on in intel I got quite a lot of entries:
acct02.c:202: INFO: Number of accounting file entries tested: 159
> ---
> testcases/kernel/syscalls/acct/acct02.c | 17 ++++++++---------
> 1 file changed, 8 insertions(+), 9 deletions(-)
> diff --git a/testcases/kernel/syscalls/acct/acct02.c b/testcases/kernel/syscalls/acct/acct02.c
> index 890568b08774..2f1290fa287f 100644
> --- a/testcases/kernel/syscalls/acct/acct02.c
> +++ b/testcases/kernel/syscalls/acct/acct02.c
> @@ -74,7 +74,8 @@ static int verify_acct(void *acc, int elap_time)
> {
> int sys_time = UNPACK(ACCT_MEMBER(ac_stime));
> int user_time = UNPACK(ACCT_MEMBER(ac_stime));
> - int ret = 0, tmp;
> + unsigned int btime_diff;
> + int ret = 0;
> float tmp2;
We could rename tmp2 to tmp (but understand if you don't want to bother
with it).
> if (strcmp(ACCT_MEMBER(ac_comm), COMMAND)) {
> @@ -83,15 +84,13 @@ static int verify_acct(void *acc, int elap_time)
> ret = 1;
> }
> - if (ACCT_MEMBER(ac_btime) < start_time) {
> - tst_res(TINFO, "ac_btime < %d (%d)", start_time,
> - ACCT_MEMBER(ac_btime));
> - ret = 1;
> - }
> + if (start_time > ACCT_MEMBER(ac_btime))
> + btime_diff = start_time - ACCT_MEMBER(ac_btime);
> + else
> + btime_diff = ACCT_MEMBER(ac_btime) - start_time;
> - tmp = ACCT_MEMBER(ac_btime) - start_time;
> - if (tmp > 1) {
> - tst_res(TINFO, "ac_btime - %d > 1 (%d)", start_time, tmp);
> + if (btime_diff > 7200) {
IMHO It's probably obvious that it's time in seconds without digging in git, so
we don't have to bother with a constant definition.
> + tst_res(TINFO, "ac_btime_diff %u", btime_diff);
> ret = 1;
> }
Kind regards,
Petr
next prev parent reply other threads:[~2019-11-12 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-12 9:15 [LTP] [PATCH] acct02: relax ac_btime checks Jan Stancek
2019-11-12 12:37 ` Petr Vorel [this message]
2019-11-12 12:52 ` Jan Stancek
2019-11-12 13:30 ` Petr Vorel
2019-11-13 9:25 ` Cyril Hrubis
2019-11-13 20:08 ` Jan Stancek
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=20191112123744.GA760@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 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.