From: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] cpuacct_task: exit cleanly on SIGVTALRM
Date: Wed, 31 Aug 2016 17:26:02 +0300 [thread overview]
Message-ID: <57C6E8FA.6030603@oracle.com> (raw)
In-Reply-To: <20160831133416.GA30378@rei.lan>
Hi!
On 08/31/2016 04:34 PM, Cyril Hrubis wrote:
> Hi!
>> We don't handle the SIGVTALRM signal in cpuacct_task,
>> so the process gets terminated, and it makes cpuacct.sh generate
>> a "Virtual timer expired" message for each cpuacct_task process.
>>
>> In my opinion, these messages have no real value, and there is no
>> need in keeping them in the output.
>
> I was just too lazy to install the signal handler in this case given
> that the default action for the signal is to terminate the process...
>
>> Signed-off-by: Stanislav Kholmanskikh <stanislav.kholmanskikh@oracle.com>
>> ---
>> .../kernel/controllers/cpuacct/cpuacct_task.c | 23 +++++++++++++++++++-
>> 1 files changed, 22 insertions(+), 1 deletions(-)
>>
>> diff --git a/testcases/kernel/controllers/cpuacct/cpuacct_task.c b/testcases/kernel/controllers/cpuacct/cpuacct_task.c
>> index 0ca01d1..94aa4e6 100644
>> --- a/testcases/kernel/controllers/cpuacct/cpuacct_task.c
>> +++ b/testcases/kernel/controllers/cpuacct/cpuacct_task.c
>> @@ -25,11 +25,21 @@
>> #include <sys/time.h>
>> #include <sys/types.h>
>> #include <unistd.h>
>> +#include <signal.h>
>> #include <stdlib.h>
>> +#include <string.h>
>> +
>> +static volatile int got_signal;
>> +
>> +static void sig_handler(int signo)
>> +{
>> + got_signal = 1;
>> +}
>
> We can as well do _exit(0); here. Then we don't have to add the global
> variable and the main loop will stay as for (;;);
Ok
>
>> int main(int argc, char **argv)
>> {
>> FILE *f;
>> + struct sigaction sa;
>>
>> if (argc != 2) {
>> fprintf(stderr, "Usage: %s /cgroup/.../tasks\n", argv[0]);
>> @@ -44,9 +54,20 @@ int main(int argc, char **argv)
>>
>> fprintf(f, "%i\n", getpid());
>> fclose(f);
>> +
>> + memset(&sa, 0, sizeof(sa));
>> + sigemptyset(&sa.sa_mask);
>> + sa.sa_handler = sig_handler;
>> +
>> + if (sigaction(SIGVTALRM, &sa, NULL)) {
>> + perror("sigaction failed");
>> + return 1;
>> + }
>
> I would just use simpler signal(SIGVTALRM, sig_handler); here.
I tend to use sigaction() everywhere, since the man page for signal()
gives preference to sigaction() for the general case.
>
>> struct itimerval it = {.it_value = {.tv_sec = 0, .tv_usec = 10000}};
>>
>> setitimer(ITIMER_VIRTUAL, &it, NULL);
>> - for (;;);
>> + while (!got_signal)
>> + ;
>> return 0;
>> }
>
> Other than that it's fine.
>
next prev parent reply other threads:[~2016-08-31 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 10:21 [LTP] [PATCH] cpuacct_task: exit cleanly on SIGVTALRM Stanislav Kholmanskikh
2016-08-31 13:34 ` Cyril Hrubis
2016-08-31 14:26 ` Stanislav Kholmanskikh [this message]
2016-09-02 7:57 ` Stanislav Kholmanskikh
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=57C6E8FA.6030603@oracle.com \
--to=stanislav.kholmanskikh@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox