linux-kernel - Re: [tracing, hang] dumping events gets stuck in synchronise

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: <4C6A4A58.2030904@cn.fujitsu.com>
Date:	Tue, 17 Aug 2010 16:37:44 +0800
From:	Lai Jiangshan <laijs@...fujitsu.com>
To:	Dave Chinner <david@...morbit.com>
CC:	linux-kernel@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>
Subject: Re: [tracing, hang] dumping events gets stuck in synchronise_sched

On 08/17/2010 03:37 PM, Dave Chinner wrote:
> Tracing folks,
> 
> I've got a machine stuck with a cpu spinning in a tight loop (the
> new writeback/sync livelock avoidance code is, well, livelocking),
> and I was trying to find out what triggered by using the writeback
> trace events. Unfortunately, I can't dump the trace events because
> it gets stuck here:

> 
> Given that the trace events are there mainly for debugging, this
> seems like a bit of an oversight - hanging a CPU in a tight loop is
> not an uncommon event during code development....
> 

You can try 'cat trace_pipe', if I did not miss you meaning.

Lai

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