From: Shuah Khan <skhan@linuxfoundation.org>
To: Laura Nao <laura.nao@collabora.com>, shuah@kernel.org
Cc: kernel@collabora.com, linux-kernel@vger.kernel.org,
linux-kselftest@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 1/2] selftests/watchdog: add -c option to limit the ping loop
Date: Thu, 5 Dec 2024 19:48:29 -0700 [thread overview]
Message-ID: <206162ed-eef9-4428-a59f-6029ed1bac8f@linuxfoundation.org> (raw)
In-Reply-To: <20241119150127.152830-2-laura.nao@collabora.com>
On 11/19/24 08:01, Laura Nao wrote:
> In order to run the watchdog selftest in a non-interactive environment,
> the loop responsible for pinging the watchdog should be finite.
> Introduce a new '-c' option to adjust the number of pings as needed.
>
> Signed-off-by: Laura Nao <laura.nao@collabora.com>
> ---
> tools/testing/selftests/watchdog/watchdog-test.c | 15 +++++++++++++--
> 1 file changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/tools/testing/selftests/watchdog/watchdog-test.c b/tools/testing/selftests/watchdog/watchdog-test.c
> index bc71cbca0dde..58c25015d5e7 100644
> --- a/tools/testing/selftests/watchdog/watchdog-test.c
> +++ b/tools/testing/selftests/watchdog/watchdog-test.c
> @@ -27,13 +27,14 @@
>
> int fd;
> const char v = 'V';
> -static const char sopts[] = "bdehp:st:Tn:NLf:i";
> +static const char sopts[] = "bdehp:c:st:Tn:NLf:i";
> static const struct option lopts[] = {
> {"bootstatus", no_argument, NULL, 'b'},
> {"disable", no_argument, NULL, 'd'},
> {"enable", no_argument, NULL, 'e'},
> {"help", no_argument, NULL, 'h'},
> {"pingrate", required_argument, NULL, 'p'},
> + {"pingcount", required_argument, NULL, 'c'},
> {"status", no_argument, NULL, 's'},
> {"timeout", required_argument, NULL, 't'},
> {"gettimeout", no_argument, NULL, 'T'},
> @@ -90,6 +91,7 @@ static void usage(char *progname)
> printf(" -h, --help\t\tPrint the help message\n");
> printf(" -p, --pingrate=P\tSet ping rate to P seconds (default %d)\n",
> DEFAULT_PING_RATE);
> + printf(" -c, --pingcount=C\tLimit the number of pings to C (default infinite)\n");
> printf(" -t, --timeout=T\tSet timeout to T seconds\n");
> printf(" -T, --gettimeout\tGet the timeout\n");
> printf(" -n, --pretimeout=T\tSet the pretimeout to T seconds\n");
> @@ -172,6 +174,7 @@ int main(int argc, char *argv[])
> {
> int flags;
> unsigned int ping_rate = DEFAULT_PING_RATE;
> + unsigned int ping_count = -1;
Assigning -1 to unsigned?
> int ret;
> int c;
> int oneshot = 0;
> @@ -248,6 +251,12 @@ int main(int argc, char *argv[])
> ping_rate = DEFAULT_PING_RATE;
> printf("Watchdog ping rate set to %u seconds.\n", ping_rate);
> break;
> + case 'c':
> + ping_count = strtoul(optarg, NULL, 0);
strtoul() returns ULONG_MAX if there are errors.Don't you have
to handle those cases? Also ping_count in unsigned int? Do you
see compile warns?
> + if (!ping_count)
> + oneshot = 1;
Why not just "goto end" at this point?
> + printf("Number of pings set to %u.\n", ping_count);> + break;
> case 's':
> flags = 0;
> oneshot = 1;
> @@ -336,9 +345,11 @@ int main(int argc, char *argv[])
>
> signal(SIGINT, term);
>
> - while (1) {
> + while (ping_count != 0) {
> keep_alive();
> sleep(ping_rate);
> + if (ping_count > 0)
> + ping_count--;
Did you test this with strtoul() failed case when the return
could be ULONG_MAX?
> }
> end:
> /*
thanks,
-- Shuah
next prev parent reply other threads:[~2024-12-06 2:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-19 15:01 [PATCH v2 0/2] Modify the watchdog selftest for execution in non-interactive environments Laura Nao
2024-11-19 15:01 ` [PATCH v2 1/2] selftests/watchdog: add -c option to limit the ping loop Laura Nao
2024-12-06 2:48 ` Shuah Khan [this message]
2024-11-19 15:01 ` [PATCH v2 2/2] selftests/watchdog: convert the test output to KTAP format Laura Nao
2024-12-05 18:34 ` Shuah Khan
2024-12-05 18:37 ` [PATCH v2 0/2] Modify the watchdog selftest for execution in non-interactive environments Shuah Khan
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=206162ed-eef9-4428-a59f-6029ed1bac8f@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=kernel@collabora.com \
--cc=laura.nao@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuah@kernel.org \
/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