From: Li Wang <liwang@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2] crypto/af_alg02: thread termination fixes
Date: Fri, 30 Jul 2021 19:43:32 +0800 [thread overview]
Message-ID: <CAEemH2etw1W0dBzHG+X+1EA4qsKr95DuqOHeWqEv=N0Bo2T2QQ@mail.gmail.com> (raw)
In-Reply-To: <668aa923-dda1-b3ce-8f5e-042e3a2174f5@jv-coder.de>
Hi Joerg,
> > That should work but no precise log to indicate where goes wrong,
> > so I vote to go the loop way:).
> Does it really matter? The being stuck in the read does not seem to be
> the failure case tested with this test. Otherwise it would TFAIL.
> Additionally the loop and "custom" timeout was only introduced at a
> later stage of the test. Initially it relied on the default timeout
> handling.
>
It's doesn't matter actually.
> If my assumption, that being stuck in the read is not the failure case
> of this test, then your argument is invalid. Your argument would work for
> each and every line of code, that might be executed, when the timeout hits.
>
Yes right, but I was not arguing for that.
I just provide more opinions for Alexey to make a final decision:).
--
Regards,
Li Wang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linux.it/pipermail/ltp/attachments/20210730/0ac04989/attachment.htm>
next prev parent reply other threads:[~2021-07-30 11:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 10:12 [LTP] [PATCH v2] crypto/af_alg02: thread termination fixes Alexey Kodanev
2021-07-30 9:12 ` Cyril Hrubis
2021-07-30 9:32 ` Joerg Vehlow
2021-07-30 10:38 ` Li Wang
2021-07-30 10:57 ` Joerg Vehlow
2021-07-30 11:43 ` Li Wang [this message]
2021-07-30 11:43 ` Cyril Hrubis
2021-08-02 4:39 ` Joerg Vehlow
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='CAEemH2etw1W0dBzHG+X+1EA4qsKr95DuqOHeWqEv=N0Bo2T2QQ@mail.gmail.com' \
--to=liwang@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 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.