linux-kernel - Re: Build regressions/improvements in v4.3-rc3

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:	Mon, 28 Sep 2015 16:08:43 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Russell King - ARM Linux <linux@....linux.org.uk>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	linux-kbuild <linux-kbuild@...r.kernel.org>
Subject: Re: Build regressions/improvements in v4.3-rc3

Hi Russell,

On Mon, Sep 28, 2015 at 3:58 PM, Russell King - ARM Linux
<linux@....linux.org.uk> wrote:
> On Mon, Sep 28, 2015 at 03:50:16PM +0200, Geert Uytterhoeven wrote:
>> On Mon, Sep 28, 2015 at 11:48 AM, Russell King - ARM Linux
>> <linux@....linux.org.uk> wrote:
>> > Also, a great many of the failures are due to the build toolchain not
>> > supporting -fstack-protector-strong.  I think it's absolutely right
>> > for the build to error out if you enable a kernel feature which requires
>> > toolchain support, but the toolchain does not support that feature.
>> >
>> > What this means is that the build results from kissb are less than
>> > useful - without spending ages looking at every single build, it's
>> > hard to find the real failures we care about.
>> >
>> > I'd suggest that either the randconfig is seeded to ensure that
>> > CONFIG_CC_STACKPROTECTOR_STRONG is always disabled in ARM randconfigs,
>> > or that the ARM toolchain is updated to support this feature.
>>
>> Or that it's impossible to enable this feature if your toolchain doesn't
>> support it?
>
> I think that would require kconfig to call out to the compiler to run
> a test build.  This kind of thing has been talked about in the past
> but the feature never seems to appear - probably because it would end
> up increasing the kconfig startup time in every case.

Given the number of existing "$(call cc-option, ...)" in Makefiles, the effect
on kconfig startup time should be small.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
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/