linux-kernel - Re: [bug report][stable] perf probe: failed to add events

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]

Date:   Mon, 25 Mar 2019 12:02:44 +0200
From:   Adrian Hunter <adrian.hunter@...el.com>
To:     Greg KH <gregkh@...uxfoundation.org>
Cc:     Joseph Qi <joseph.qi@...ux.alibaba.com>,
        Arnaldo Carvalho de Melo <arnaldo.melo@...il.com>,
        Alexander Shishkin <alexander.shishkin@...ux.intel.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        luto@...nel.org, Jiufei Xue <jiufei.xue@...ux.alibaba.com>,
        Xu Yu <xuyu@...ux.alibaba.com>, peterz@...radead.org,
        mingo@...hat.com
Subject: Re: [bug report][stable] perf probe: failed to add events

On 21/03/19 12:10 PM, Greg KH wrote:
> On Thu, Feb 28, 2019 at 09:19:08AM +0200, Adrian Hunter wrote:
>> On 28/02/19 4:07 AM, Joseph Qi wrote:
>>> Hi Adrian,
>>>
>>> On 19/2/27 20:39, Adrian Hunter wrote:
>>>> Seems to be fixed by this:
>>>>
>>>> From: Adrian Hunter <adrian.hunter@...el.com>
>>>> Date: Wed, 27 Feb 2019 05:35:25 +0200
>>>> Subject: [PATCH] perf probe: Fix getting the kernel map
>>>>
>>>> Since commit 4d99e4136580 ("perf machine: Workaround missing maps for x86
>>>> PTI entry trampolines"), perf tools has been creating more than one kernel
>>>> map, however 'perf probe' assumed there could be only one.
>>>>
>>>> Fix by using machine__kernel_map() to get the main kernel map.
>>>>
>>>> Signed-off-by: Adrian Hunter <adrian.hunter@...el.com>
>>>> Fixes: 4d99e4136580 ("perf machine: Workaround missing maps for x86 PTI entry trampolines")
>>>
>>> Below is my investigation result before, FYI.
>>> the first bad commit (v4.18 ~ v4.19):
>>> d83212d5dd67 kallsyms, x86: Export addresses of PTI entry trampolines
>>
>> Yes we should add a fixes tag for that also.
> 
> So, what do I need to do here for the stable tree(s) to resolve this
> issue?

Nothing.

Patch was re-sent with a stable tag so will go through like normal:

	https://lore.kernel.org/lkml/2ed432de-e904-85d2-5c36-5897ddc5b23b@intel.com/