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, 09 Oct 2012 11:08:38 +0900
From:	Yoshihiro YUNOMAE <yoshihiro.yunomae.ez@...achi.com>
To:	Steven Rostedt <rostedt@...dmis.org>,
	David Sharp <dhsharp@...gle.com>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...hat.com>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Vaibhav Nagarnaik <vnagarnaik@...gle.com>,
	linux-kernel@...r.kernel.org, yrl.pp-manager.tt@...achi.com
Subject: [PATCH 0/2] ftrace: [BUGFIX] type of ring_buffer_oldest_event_ts()
 and showing of stats per cpu directory

The following patch set fixes two bugs for ftrace.

[1/2] 
This patch fixes type mismatch of ring_buffer_oldest_event_ts().

[2/2]
This fixes showing of stats per cpu directory for ftrace using counter or tsc
as a time stamp. This patch depends on David's patch series
(https://lkml.org/lkml/2012/10/1/652), but this bug already exists in the
counter mode. 

Thank you,

---

Yoshihiro YUNOMAE (2):
      ftrace: Show raw time stamp on stats per cpu using counter or tsc mode for trace_clock
      ftrace: Change unsigned long type of ring_buffer_oldest_event_ts() to u64


 include/linux/ring_buffer.h |    2 +-
 kernel/trace/ring_buffer.c  |    4 ++--
 kernel/trace/trace.c        |   23 +++++++++++++++++------
 3 files changed, 20 insertions(+), 9 deletions(-)

-- 
Yoshihiro YUNOMAE
Software Platform Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: yoshihiro.yunomae.ez@...achi.com
--
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/

Powered by blists - more mailing lists