linux-kernel - Re: PERF_EVENT_IOC_SET_FILTER has different values based on bitness

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: <20141008152204.GN14113@kernel.org>
Date:	Wed, 8 Oct 2014 12:22:04 -0300
From:	Arnaldo Carvalho de Melo <acme@...nel.org>
To:	David Ahern <dsahern@...il.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	Ingo Molnar <mingo@...nel.org>,
	Frederic Weisbecker <fweisbec@...il.com>,
	LKML <linux-kernel@...r.kernel.org>, Jiri Olsa <jolsa@...nel.org>
Subject: Re: PERF_EVENT_IOC_SET_FILTER has different values based on bitness

Em Wed, Oct 08, 2014 at 09:17:38AM -0600, David Ahern escreveu:
> On 10/8/14, 1:23 AM, Peter Zijlstra wrote:
> >Should be fixed for a while now
> >
> >---
> >commit b3f207855f57b9c8f43a547a801340bb5cbc59e5
> >Author: Pawel Moll <pawel.moll@....com>
> >Date:   Fri Jun 13 16:03:32 2014 +0100
> >
> >     perf: Handle compat ioctl
> >
> 
> that works. Can we get this queued to the stable releases (at least as far
> back as v3.4)?

I wonder how that works best, being on the receiving side of such requests
from time to time.

I guess that to scale, that would be better done by:

1. Reporter tests if the patch applies (and works) on the desired
targets.

2. Reporter sends the request, with the above test results, to
stable@...nel.org, following whatever conventions are to get the
attention of the stable release maintainers.

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