linux-kernel - Re: [PATCH] perf unwind: Limit warnings when asked for not supported unwind

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: <20170618225308.GC13111@krava>
Date:   Mon, 19 Jun 2017 00:53:08 +0200
From:   Jiri Olsa <jolsa@...hat.com>
To:     Arnaldo Carvalho de Melo <acme@...nel.org>
Cc:     Jiri Olsa <jolsa@...nel.org>, He Kuang <hekuang@...wei.com>,
        lkml <linux-kernel@...r.kernel.org>,
        Ingo Molnar <mingo@...nel.org>,
        Peter Zijlstra <a.p.zijlstra@...llo.nl>,
        Namhyung Kim <namhyung@...nel.org>,
        David Ahern <dsahern@...il.com>
Subject: Re: [PATCH] perf unwind: Limit warnings when asked for not supported
 unwind

On Fri, Jun 16, 2017 at 01:25:04PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Jun 16, 2017 at 02:12:53PM +0200, Jiri Olsa escreveu:
> > Ingo reported following warning flooding the report out:
> > 
> >   unwind: target platform=x86 is not supported
> > 
> > We trigger this warning when the dwarf unwinder is asked to
> > process architecture which wasn't compiled in, like when you
> > get 32bit application samples on your 64bit server and you
> > don't have the 32bit remote unwind support compiled in.
> > 
> > This patch limits the warning to single message for arch,
> > and adds bits info. Above message is changed to:
> > 
> >   unwind: target platform=x86 32bit is not supported
> 
> Can we have a more informative message telling the user what is
> necessary to have this feature supported?
> 
> The way you phrased it looks like it is not supported at all, while what
> I read in the discussion is that one needs to have specific versions of
> support libraries installed to have this working, right?

exactly, I'll dig out from changelogs needed libunwind version
and change the changelog in v2

jirka