All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Martin Doucha <mdoucha@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] waitpid01: Test all standard deadly signals
Date: Tue, 30 Jan 2024 18:22:43 +0100	[thread overview]
Message-ID: <20240130172243.GB824958@pevik> (raw)
In-Reply-To: <20240130162813.20278-1-mdoucha@suse.cz>

Hi Martin,

nice work.

Reviewed-by: Petr Vorel <pvorel@suse.cz>

...
> +++ b/testcases/kernel/syscalls/waitpid/waitpid01.c
> @@ -5,25 +5,57 @@
>   * Copyright (c) 2018 Cyril Hrubis <chrubis@suse.cz>

Very nice cleanup, you deserve copyright, right?
 * Copyright (C) 2024 SUSE LLC <mdoucha@suse.cz>
>   */

> Extend waitpid01 to test all standard signals that kill the target
> process unless caught. Also remove waitpid02 since testing SIGFPE
> in waitpid01 makes it redundant.
> +static int testcase_list[] = {
> +	SIGABRT,
> +	SIGALRM,
> +	SIGBUS,
> +	SIGFPE,
> +	SIGHUP,
> +	SIGILL,
> +	SIGINT,
> +	SIGKILL,
> +	SIGPIPE,
> +	SIGPOLL,
> +	SIGPROF,
> +	SIGQUIT,
> +	SIGSEGV,
> +	SIGSYS,
> +	SIGTERM,
> +	SIGTRAP,
> +	SIGVTALRM,
> +	SIGXCPU,
> +	SIGXFSZ
> +};

I suppose you ignored from the list of signals in man signal(7) these with
action "Core" "Term" unless without standard ("-"), right?
So user defined signals (SIGUSR1, SIGUSR2) does not make sense to test?

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2024-01-30 17:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-30 16:28 [LTP] [PATCH] waitpid01: Test all standard deadly signals Martin Doucha
2024-01-30 17:22 ` Petr Vorel [this message]
2024-01-31  9:05   ` Martin Doucha
2024-01-31 10:14     ` Petr Vorel
2024-01-31 10:23       ` Martin Doucha
2024-01-31 16:13         ` Petr Vorel
2024-02-05 17:34 ` Petr Vorel
2024-02-05 18:13   ` Petr Vorel
2024-02-06 10:01   ` Martin Doucha
2024-02-06 10:44     ` Petr Vorel
2024-02-06 10:49       ` Martin Doucha
2024-02-06 11:00         ` Petr Vorel

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=20240130172243.GB824958@pevik \
    --to=pvorel@suse.cz \
    --cc=ltp@lists.linux.it \
    --cc=mdoucha@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 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.