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: <CAK7LNARQbJH_cScJ+feCSCFGbHr+EiaKcYLLxsvVn+WVCOoRbg@mail.gmail.com>
Date:   Fri, 1 Feb 2019 20:03:43 +0900
From:   Masahiro Yamada <yamada.masahiro@...ionext.com>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>, X86 ML <x86@...nel.org>,
        Michal Marek <michal.lkml@...kovi.net>
Subject: Re: [PATCH] kbuild: Disable extra debugging info in .s output

On Fri, Feb 1, 2019 at 7:25 PM Borislav Petkov <bp@...en8.de> wrote:
>
> On Fri, Feb 01, 2019 at 07:09:36PM +0900, Masahiro Yamada wrote:
> > Why should the normal build affected by the debugging aid?
>
> Hmm, ok, so then that target really is being used during the normal
> build. I don't know why yet so I'll have to do some more staring.
>
> > One more thing, you did not answer my question.
> >
> > If you are complaining about the DWARF info
> > enabled by CONFIG_DEBUG_INFO,
> > I recommend to turn off CONFIG_DEBUG_INFO.
>
> Yes but I don't want to be changing .config just so that I can look at
> the asm output.


Generally speaking, the build system should do what was
requested by a set of CONFIG options.

If you want to turn off DWARF info,
you should disable the corresponding CONFIG.


If you want to tweak the behavior from the command line,
KCFLAGS is available though.


make arch/x86/kernel/cpu/common.s KCFLAGS="-gno-as-locview-support
-fno-dwarf2-cfi-asm -feliminate-unused-debug-symbols
-gno-statement-frontiers"



> I'll think about a better solution.
>
> Thx.
>
> --
> Regards/Gruss,
>     Boris.
>
> Good mailing practices for 400: avoid top-posting and trim the reply.



-- 
Best Regards
Masahiro Yamada

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ