linux-kernel - Re: perf: PERF_FLAG_FD_OUTPUT has been broken since 2.6.35

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: <alpine.DEB.2.11.1501091123040.27178@vincent-weaver-1.umelst.maine.edu>
Date:	Fri, 9 Jan 2015 11:26:54 -0500 (EST)
From:	Vince Weaver <vincent.weaver@...ne.edu>
To:	Peter Zijlstra <peterz@...radead.org>
cc:	Vince Weaver <vincent.weaver@...ne.edu>,
	linux-kernel@...r.kernel.org, Paul Mackerras <paulus@...ba.org>,
	Ingo Molnar <mingo@...hat.com>,
	Arnaldo Carvalho de Melo <acme@...nel.org>
Subject: Re: perf: PERF_FLAG_FD_OUTPUT has been broken since 2.6.35


On Fri, 9 Jan 2015, Peter Zijlstra wrote:
> > So is this worth fixing seeing as apparently no one uses this feature?
> 
> I think there's a fair argument for removing it, Ingo, Acme?

could the functionality be replaced with a subsequent call to
	ioctl(PERF_EVENT_IOC_SET_OUTPUT)
?

Although I suppose there's a possibility for losing a small amount of data 
or some other reason that PERF_FLAG_FD_OUTPUT was introduced in the first 
place.

In addition, if we remove PERF_FLAG_FD_OUTPUT would there then be any 
reason to keep PERF_FLAG_FD_NO_GROUP around?

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