linux-kernel - Re: [tip:perf/core] perf: Update perf_event

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

Message-ID: <20130913214225.GJ21832@twins.programming.kicks-ass.net>
Date:	Fri, 13 Sep 2013 23:42:25 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Vince Weaver <vince@...ter.net>
Cc:	mingo@...nel.org, hpa@...or.com, linux-kernel@...r.kernel.org,
	adrian.hunter@...el.com, tglx@...utronix.de,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf: Update perf_event_type documentation

On Fri, Sep 13, 2013 at 05:31:26PM -0400, Vince Weaver wrote:
> So in Adrian Hunter's posted patches the PERF_RECORD_MMAP documentation
> is also patched like all the others, with 
> 
>     struct sample_id                sample_id;
> 
> But in this tip message (and in the current linus-git kernel) somehow the
> PERF_RECORD_MMAP line of the patch was dropped.
> 
> Was that intentional?

No, no idea what happened..

---
Subject: perf: Update ABI comment
From: Peter Zijlstra <peterz@...radead.org>
Date: Fri Sep 13 23:39:17 CEST 2013

For some mysterious reason the sample_id field of PERF_RECORD_MMAP
went AWOL.

Reported-by: Vince Weaver <vince@...ter.net>
Signed-off-by: Peter Zijlstra <peterz@...radead.org>
---
 include/uapi/linux/perf_event.h |    1 +
 1 file changed, 1 insertion(+)

--- a/include/uapi/linux/perf_event.h
+++ b/include/uapi/linux/perf_event.h
@@ -528,6 +528,7 @@ enum perf_event_type {
 	 *	u64				len;
 	 *	u64				pgoff;
 	 *	char				filename[];
+	 * 	struct sample_id		sample_id;
 	 * };
 	 */
 	PERF_RECORD_MMAP			= 1,
--
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/