linux-kernel - Re: Kernel builds now failing

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: <cad69928-92a2-472a-9ef4-99d3b74c0ab1@t-8ch.de>
Date:   Mon, 16 Jan 2023 17:15:45 -0600 (CST)
From:   Thomas Weißschuh  <thomas@...ch.de>
To:     Amy Parker <apark0006@...dent.cerritos.edu>
Cc:     Thomas Weißschuh <linux@...ssschuh.net>,
        linux-kernel@...r.kernel.org, linux-kbuild@...r.kernel.org
Subject: Re: Kernel builds now failing


Jan 16, 2023 17:10:34 Amy Parker <apark0006@...dent.cerritos.edu>:

> On Mon, Jan 16, 2023 at 11:54 AM Thomas Weißschuh <linux@...ssschuh.net> wrote:
>> I expect this to be due to a change in make 4.4 that ignores SIGPIPEs [0].
>> So programs called from make will not receive a SIGPIPE when writing to
>> a closed pipe but instead an EPIPE write error.
>> `find` does not seem to handle this.

> Thank you so much for the clarification! I've also seen reports of
> other tools not handling it (such as `yes').

Even bash os affected.

>> This behavior in make is new and I can't find a reasoning for it.
>> It also breaks other softwares builds.
>
> Are you aware of active discussion regarding this on Savannah, or
> should I go and report the effects there?

I got a pointer to the discussion after my first mail:
https://savannah.gnu.org/bugs/index.php?63307

It will be fixed in 4.4.1, testing the linked prerelease version would be good.

>> For now you can disable CONFIG_IKHEADERS and the build should work
>> again.
>
> Alright, thanks. Did that, and re-ran my kernel build (allmodconfig).
> All works now.

Nice.

>> [0] make 4.4 was packaged for ArchLinux on 5th of January, so it would
>> fit the timeline.
>
> Yep, running Make 4.4.

Maybe it makes sense to ask for a backport for the fix for the ArchLinux package.