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]
Date:   Mon, 13 Feb 2017 16:00:02 -0600
From:   Josh Poimboeuf <jpoimboe@...hat.com>
To:     Marc MERLIN <marc@...lins.org>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: Please turn "Cannot use CONFIG_STACK_VALIDATION" into build error

On Mon, Feb 13, 2017 at 01:31:32PM -0800, Marc MERLIN wrote:
> Anyway, after not finding it in xconfig, I editted .config, and did:
> # CONFIG_STACK_VALIDATION is not set
> save .config
> and the next build re-enabled the option.
> That's what caught me by surprise. Did I do something wrong, or is there an
> issue there?

I really don't see how it would be possible for it to come back by
itself, as it's disabled by default, and no other options select it.
When I remove it, it stays disabled.

> > Ideally the same warning should be printed when building OOT modules.
> > I'll try to figure out if there's a way to do that it.
> 
> This would help, although in that case you can even make the warning an
> error since objtool missing seems to be fatal?

It doesn't need to be fatal though.  It should just be a warning and the
build should succeed, like it does when building the kernel.

-- 
Josh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ