From: Jan Stancek <jstancek@redhat.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH] cgroup/cpuctl: clean cpuctl_task_* in case of OOM
Date: Mon, 19 Sep 2011 10:57:28 +0200 [thread overview]
Message-ID: <4E7703F8.9000905@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
If one of cpuctl_task_* gets killed by OOM, it won't
signal run script with SIGUSR1, and trap action
"killall cpuctl_task_*;" never runs.
Try to kill all left over cpuctl_task_* in cleanup() to be sure,
none are left behind.
Signed-off-by: Jan Stancek <jstancek@redhat.com>
---
testcases/kernel/controllers/cpuctl/parameters.sh | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
[-- Attachment #2: 0001-cgroup-cpuctl-clean-cpuctl_task_-in-case-of-OOM.patch --]
[-- Type: text/x-patch, Size: 608 bytes --]
diff --git a/testcases/kernel/controllers/cpuctl/parameters.sh b/testcases/kernel/controllers/cpuctl/parameters.sh
index 502944e..5f87695 100755
--- a/testcases/kernel/controllers/cpuctl/parameters.sh
+++ b/testcases/kernel/controllers/cpuctl/parameters.sh
@@ -70,6 +70,8 @@ cleanup ()
echo "Cleanup called";
killall cpuctl_def_task01 1>/dev/null 2>&1;
killall cpuctl_def_task02 1>/dev/null 2>&1;
+ killall cpuctl_task_* 1>/dev/null 2>&1;
+ sleep 1
rm -f cpuctl_task_* 2>/dev/null
for task in `cat /dev/cpuctl/group_def/tasks`; do
echo $task > /dev/cpuctl/tasks 2>/dev/null 1>&2;
[-- Attachment #3: Type: text/plain, Size: 369 bytes --]
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the
BlackBerry® mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry® DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1
[-- Attachment #4: Type: text/plain, Size: 155 bytes --]
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
reply other threads:[~2011-09-19 8:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4E7703F8.9000905@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp-list@lists.sourceforge.net \
/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