linux-kernel - [PATCH] ftrace: also dump the entry->flag field

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]

Date:	Tue, 13 May 2008 18:52:45 +0200
From:	Sebastian Siewior <bigeasy@...utronix.de>
To:	Ingo Molnar <mingo@...hat.com>
Cc:	Greg Ungerer <gerg@...inux.org>, uclinux-dev@...inux.org,
	linux-kernel@...r.kernel.org,
	Sebastian Siewior <bigeasy@...utronix.de>
Subject: [PATCH] ftrace: also dump the entry->flag field

The data is collected anyway so why not print it?

Signed-off-by: Sebastian Siewior <bigeasy@...utronix.de>
---
 kernel/trace/trace.c |    9 ++++++++-
 1 files changed, 8 insertions(+), 1 deletions(-)

diff --git a/kernel/trace/trace.c b/kernel/trace/trace.c
index 06c85b3..0b0e996 100644
--- a/kernel/trace/trace.c
+++ b/kernel/trace/trace.c
@@ -1514,7 +1514,14 @@ static int print_trace_fmt(struct trace_iterator *iter)
 	ret = trace_seq_printf(s, "[%02d] ", iter->cpu);
 	if (!ret)
 		return 0;
-	ret = trace_seq_printf(s, "%5lu.%06lu: ", secs, usec_rem);
+	ret = trace_seq_printf(s, "%5lu.%06lu ", secs, usec_rem);
+	if (!ret)
+		return 0;
+	ret = trace_seq_printf(s, "{%2u|%c%c%c%c}: ", entry->preempt_count,
+			entry->flags & TRACE_FLAG_IRQS_OFF      ? '.' : 'I',
+			entry->flags & TRACE_FLAG_NEED_RESCHED  ? 'R' : '.',
+			entry->flags & TRACE_FLAG_HARDIRQ       ? 'H' : '.',
+			entry->flags & TRACE_FLAG_SOFTIRQ       ? 'S' : '.');
 	if (!ret)
 		return 0;
 
-- 
1.5.4.3

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