From: Richard Palethorpe <rpalethorpe@suse.de>
To: Petr Vorel <pvorel@suse.cz>
Cc: LTP List <ltp@lists.linux.it>
Subject: Re: [LTP] [PATCH 1/2] read_all: Add worker timeout
Date: Mon, 18 Jul 2022 11:37:59 +0100 [thread overview]
Message-ID: <87lesqiu29.fsf@suse.de> (raw)
In-Reply-To: <YtBYsYOMskQ6v3dD@pevik>
Hello,
Petr Vorel <pvorel@suse.cz> writes:
> Hi all,
>
> Reviewed-by: Petr Vorel <pvorel@suse.cz>
>
>> > +static void restart_worker(struct worker *const worker)
>> > +{
>> > + int wstatus, ret, i, q_len;
>> > + struct timespec now;
>> > +
>> > + kill(worker->pid, SIGKILL);
>> > + ret = waitpid(worker->pid, &wstatus, 0);
>
>> Is there a chance we could get stuck in uninterruptible read? I think I saw some
>> in past, but those may be blacklisted already, so this may only be something
>> to watch for if we still get test timeouts in future.
>
> +1
>
> ...
>> > + if (ret != worker->pid) {
>> > + tst_brk(TBROK | TERRNO, "waitpid(%d, ...) = %d",
>> > + worker->pid, ret);
>> > + }
>> > +
>> > + /* Make sure the queue length and semaphore match. Threre is a
>> > + * race in qeuue_pop where the semaphore can be decremented
>> ^^ typo in queue_pop above
>
> ...
>> > + tst_clock_gettime(CLOCK_MONOTONIC_RAW, &now);
>> > + elapsed =
>> > + tst_timespec_to_ms(now) - tst_atomic_load(&w->last_seen);
>> > +
>> > + if (elapsed > worker_timeout) {
>> > + if (!quiet) {
>> > + tst_res(TINFO,
>> > + "Worker %d (%d) stuck for %dms, restarting it",
>> > + i, w->pid, elapsed);
>
>> Can we also print file worker is stuck on?
>> And as Li pointed out, I'd also extend max_runtime to 60 seconds.
>
> +1, all these additional changes make sense to me.
OK I'll make these changes, thanks!
>
> Kind regards,
> Petr
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-07-18 10:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 12:46 [LTP] [PATCH 1/2] read_all: Add worker timeout Richard Palethorpe via ltp
2022-07-12 12:46 ` [LTP] [PATCH 2/2] read_all: Fix type warnings Richard Palethorpe via ltp
2022-07-14 4:46 ` Li Wang
2022-07-14 17:53 ` Petr Vorel
2022-07-14 4:45 ` [LTP] [PATCH 1/2] read_all: Add worker timeout Li Wang
2022-07-18 10:09 ` Richard Palethorpe
2022-07-19 8:58 ` Li Wang
2022-07-14 6:58 ` Jan Stancek
2022-07-14 17:56 ` Petr Vorel
2022-07-18 10:37 ` Richard Palethorpe [this message]
2022-07-18 10:57 ` Richard Palethorpe
2022-07-18 13:01 ` Richard Palethorpe
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=87lesqiu29.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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