linux-kernel - Re: kbuild: Ctrl-C of parallel kernel build sometimes corrupts .o.cmd files permanently

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: <YMS1vNnnbPNUbsVN@gmail.com>
Date:   Sat, 12 Jun 2021 15:25:16 +0200
From:   Ingo Molnar <mingo@...nel.org>
To:     Masahiro Yamada <masahiroy@...nel.org>
Cc:     Michal Marek <michal.lkml@...kovi.net>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: kbuild: Ctrl-C of parallel kernel build sometimes corrupts
 .o.cmd files permanently


* Masahiro Yamada <masahiroy@...nel.org> wrote:

> > Hmm, I do not know why GNU Make behaves like this...
> >
> > I will ask about this in GNU Make ML.
> 
> 
> https://lists.gnu.org/archive/html/help-make/2021-06/msg00001.html
> 
> 
> In short, 'tee' was also interrupted,
> then 'make' got SIGPIPE, which terminated the app
> due to the default behavior.

So, what's the solution? It's rather common to 
run a build job while capturing a log via 'tee'. 

Ctrl-C only recently started corrupting the 
kernel build. (As in the past ~2 years ;-)


Thanks,

	Ingo