linux-kernel - [PATCH] trace-cmd: Plug startup race between flush

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4CB8401B.2020801@siemens.com>
Date:	Fri, 15 Oct 2010 13:50:51 +0200
From:	Jan Kiszka <jan.kiszka@...mens.com>
To:	Steven Rostedt <srostedt@...hat.com>
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	linux-trace-users@...r.kernel.org
Subject: [PATCH] trace-cmd: Plug startup race between flush_threads and recorders

As the SIGUSR1 handler is so far registered after forking the recorder
child, there is a small race window where a flush sent by the main
process can actually kill the child. Plug this by registering the signal
handlers before the fork. This also allows to unify SIGINT registration.

Signed-off-by: Jan Kiszka <jan.kiszka@...mens.com>
---
 trace-cmd.c |    7 +++----
 1 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/trace-cmd.c b/trace-cmd.c
index 9cbe362..f8992a8 100644
--- a/trace-cmd.c
+++ b/trace-cmd.c
@@ -1089,6 +1089,8 @@ static int create_recorder(int cpu)
 	char *file;
 	int pid;
 
+	signal(SIGUSR1, flush);
+
 	pid = fork();
 	if (pid < 0)
 		die("fork");
@@ -1096,9 +1098,6 @@ static int create_recorder(int cpu)
 	if (pid)
 		return pid;
 
-	signal(SIGINT, finish);
-	signal(SIGUSR1, flush);
-
 	if (rt_prio)
 		set_prio(rt_prio);
 
@@ -1694,9 +1693,9 @@ int main (int argc, char **argv)
 	set_options();
 
 	if (record || extract) {
+		signal(SIGINT, finish);
 		if (!latency)
 			start_threads();
-		signal(SIGINT, finish);
 	}
 
 	if (extract) {
-- 
1.7.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/