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: <202106011555.A7E9BE38@keescook>
Date:   Tue, 1 Jun 2021 15:55:31 -0700
From:   Kees Cook <keescook@...omium.org>
To:     jarmo.tiitto@...il.com
Cc:     Bill Wendling <morbo@...gle.com>,
        LKML <linux-kernel@...r.kernel.org>,
        Nathan Chancellor <nathan@...nel.org>,
        Jonathan Corbet <corbet@....net>,
        Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        clang-built-linux <clang-built-linux@...glegroups.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Nick Desaulniers <ndesaulniers@...gle.com>,
        Sami Tolvanen <samitolvanen@...gle.com>
Subject: Re: [PATCH] pgo: rename the raw profile file to vmlinux.profraw

On Wed, Jun 02, 2021 at 12:40:25AM +0300, jarmo.tiitto@...il.com wrote:
> Yes, my future intention is that there will be one *.profraw file per module.
> And curiously I would also have renamed the current profile data file to 
> "vmlinux.profraw" to disambiguate it from what part of kernel generated it.
> 
> I already wrote an small fix up that I think should be part of the upstream 
> code so that profiling the vmlinux works better.
> It filters out any module originated content from vmlinux.profraw.
> 
> Above will be probably a good exercise for me.
> 
> Next, my future v2 module profiling machinery
> would probably follow on top of your work.

Okay, great; thanks for digging into it! :)

-- 
Kees Cook

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ