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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAMuHMdU5UGfDSzfNWsZvsgLvJJYK-5VWEZ841Zc4GYfey6RdtA@mail.gmail.com>
Date:	Mon, 28 Sep 2015 15:50:16 +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 11:48 AM, Russell King - ARM Linux
<linux@....linux.org.uk> wrote:
> On Mon, Sep 28, 2015 at 10:30:06AM +0100, Russell King - ARM Linux wrote:
>> On Mon, Sep 28, 2015 at 08:57:44AM +0200, Geert Uytterhoeven wrote:
>> > On Sun, Sep 27, 2015 at 9:34 PM, Geert Uytterhoeven
>> > <geert@...ux-m68k.org> wrote:
>> > > JFYI, when comparing v4.3-rc3[1] to v4.3-rc2[3], the summaries are:
>> > >   - build errors: +8/-12
>> >
>> >   + error: No rule to make target include/config/auto.conf:  => N/A
>> >
>> > arm-randconfig
>>
>> Not every randconfig failure is a kernel problem.  Here's an example:
>>
>> Physical address of main memory (PHYS_OFFSET) [] (NEW) aborted!
>>
>> Console input/output is redirected. Run 'make oldconfig' to update configuration.
>>
>> This needs someone to provide a value, which means these failures are
>> not in fact failures of the kernel, but a failure of the build system
>> to anticipate that there may be Kconfig questions that need input.
>>
>> So, these ones should be ignored.

Usually I ignore them. But as this was the only failure to report (I ignore
R_PPC64_REL24 failures, too), I thought to kick the kbuild people (and the
ARM list, as it was the ARM randconfig that failed) for once.

> 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?

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/