linux-kernel - Re: [PATCH 1/1] hung_task debugging: Add tracepoint to report the hang

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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131020084837.GB16236@gmail.com>
Date:	Sun, 20 Oct 2013 10:48:37 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Oleg Nesterov <oleg@...hat.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Steven Rostedt <rostedt@...dmis.org>,
	Dave Sullivan <dsulliva@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] hung_task debugging: Add tracepoint to report the
 hang


* Oleg Nesterov <oleg@...hat.com> wrote:

> Currently check_hung_task() prints a warning if it detects the problem, 
> but it is not convenient to watch the system logs if user-space wants to 
> be notified about the hang.
> 
> Add the new trace_sched_process_hang() into check_hung_task(), this way 
> a user-space monitor can easily wait for the hang and potentially 
> resolve a problem.

I'm wondering, is the data of trace_console() in kernel/printk/printk.c 
not sufficient?

If it's not enough then it might be better to add a higher level printk 
tracepoint instead - that can catch hung_task messages and (much) more.

Thanks,

	Ingo
--
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/