linux-kernel - [PATCH 0/2 v3] scsi: ftrace based scsi tracing feature

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: <4B7914CD.8020508@jp.fujitsu.com>
Date:	Mon, 15 Feb 2010 18:33:01 +0900
From:	Kei Tokunaga <tokunaga.keiich@...fujitsu.com>
To:	"linux-scsi@...r.kernel.org" <linux-scsi@...r.kernel.org>,
	James Bottomley <James.Bottomley@...e.de>,
	Ingo Molnar <mingo@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	"Martin K. Petersen" <martin.petersen@...cle.com>
CC:	Tomohiro Kusumi <kusumi.tomohiro@...fujitsu.com>,
	lkml <linux-kernel@...r.kernel.org>,
	Li Zefan <lizf@...fujitsu.com>,
	Xiao Guangrong <xiaoguangrong@...fujitsu.com>,
	Kei Tokunaga <tokunaga.keiich@...fujitsu.com>
Subject: [PATCH 0/2 v3] scsi: ftrace based scsi tracing feature

Hi,

This is v3 patch series of SCSI trace.  Since there has been no
more new feedback on v2 for about a week, I've decided to post
this.

Changelog from v2:

  - fixed variable length command handling (removed the
    assumption that READ/WRITE(32) is only called if protection
    is enabled.)

Here are the links to the discussions on v2:

  [PATCH 0/2 v2] scsi: ftrace based scsi tracing feature
    http://marc.info/?l=linux-scsi&m=126500018231317&w=2
  [PATCH 1/2 v2] scsi: add __print_hex() to ftrace
    http://marc.info/?l=linux-scsi&m=126500074718183&w=2
  [PATCH 2/2 v2] scsi: add scsi trace core function and put trace
points
    http://marc.info/?l=linux-scsi&m=126500087718320&w=2

This patchset applies to 2.6.33-rc8.

Thanks,
Kei

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