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: <20250207025127.2sy74bhcu6wtbo6a@jpoimboe>
Date: Thu, 6 Feb 2025 18:51:27 -0800
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: Nathan Chancellor <nathan@...nel.org>
Cc: Brendan Jackman <jackmanb@...gle.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Masahiro Yamada <masahiroy@...nel.org>,
	Nicolas Schier <nicolas@...sle.eu>, linux-kernel@...r.kernel.org,
	linux-kbuild@...r.kernel.org
Subject: Re: [PATCH v3 0/2] objtool: Add option to fail build on vmlinux
 warnings

On Thu, Feb 06, 2025 at 10:10:36AM -0700, Nathan Chancellor wrote:
> Right, I think gating on '!COMPILE_TEST' would not be a terrible way to
> introduce it. We would definitely want to remove that dependency as
> soon as possible because we want compile testers to be qble to find
> these problems and have them be noticeable but it should make the
> introduction of CONFIG_OBJTOOL_WERROR less disruptive.

I want to get CONFIG_OBJTOOL_WERROR merged soon.  I'm working on some
other patches to go along with it that will hopefully ease some of the
pain.  I'll post those soon and then hopefully we can get it into
linux-next.

I didn't quite follow the OBJTOOL_FLAGS idea.  We already have
OBJTOOL_ARGS which allows adding arguments (though not removing them),
was it mean to be something like that?

I agree we might want to ease into the pool with !COMPILE_TEST.

-- 
Josh

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ