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:	Tue, 29 Sep 2015 19:31:09 +0200
From:	Borislav Petkov <bp@...en8.de>
To:	Ksenija Stanojević <ksenija.stanojevic@...il.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>, tglx@...utronix.de,
	mingo@...hat.com, x86@...nel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: include: asm: Fix build warning

On Tue, Sep 29, 2015 at 07:19:32PM +0200, Ksenija Stanojević wrote:
> On Tue, Sep 29, 2015 at 7:16 PM, Borislav Petkov <bp@...en8.de> wrote:
> > On Tue, Sep 29, 2015 at 07:12:07PM +0200, Ksenija Stanojević wrote:
> >> when building with:
> >> make drivers/staging/oplc_dcon/olpc_dcon.o
> >> I get this warnings.
> >
> > Yeah, you can't pick out single files from the source tree and try to
> > build them and expect that to always work. That olpc_dcon think depends
> > on CONFIG_OLPC so if you go enable it in Kconfig, you would have to have
> > enabled CONFIG_OLPC first.
> >
> Ok, thanks!

Sure, no probs.

Btw, if you really want to try to fix some bugs, you could try to build
the kernel with

make -j<number-of-cores-on-your-machine> W=n 2>build-warnings.log

where n is 1, 2 or 3 (or any subset of those) and try to analyze them.

Look at the output in build-warnings.log and try to understand why the
compiler is complaining and whether it makes sense.

Some of them might be worth fixing. Most of them are bogus and/or fixing
them would require just too much code changes for no real gain but some
of the warnings do make sense.

Also, you could do

make allmodconfig

before that so that you can build *everything* and catch all warnings.

HTH.

-- 
Regards/Gruss,
    Boris.

ECO tip #101: Trim your mails when you reply.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ