linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Masahiro Yamada <masahiroy@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Michal Marek <michal.lkml@markovi.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kbuild: Ctrl-C of parallel kernel build sometimes corrupts .o.cmd files permanently
Date: Fri, 4 Jun 2021 12:22:33 +0900	[thread overview]
Message-ID: <CAK7LNAQ73zG69F4hMJhgrHp8yT9tUmb-0tN=kFtWA98-YV3eNA@mail.gmail.com> (raw)
In-Reply-To: <YLjOjZVetM4UbUPn@gmail.com>

On Thu, Jun 3, 2021 at 9:44 PM Ingo Molnar <mingo@kernel.org> wrote:
>
>
> * Ingo Molnar <mingo@kernel.org> wrote:
>
> > >   CC      security/keys/keyctl_pkey.o
> > >   CC      kernel/sys.o
> > >   CC      arch/x86/power/hibernate_64.o
> > > ^Cmake[5]: *** Deleting file 'drivers/video/fbdev/core/fbcmap.o'  <---- Deleting
> > > make[5]: *** [scripts/Makefile.build:272:
> > > drivers/video/fbdev/core/fbmon.o] Interrupt
> > > make[3]: *** [scripts/Makefile.build:272: security/selinux/nlmsgtab.o] Interrupt
> > > make[2]: *** [scripts/Makefile.build:272: arch/x86/power/cpu.o] Interrupt
> > > make[2]: *** [scripts/Makefile.build:272:
> >
> > Interestingly I don't get *any* interruption messages at all:
> >
> >   CC      drivers/dma/dw/acpi.o
> >   CC      sound/pci/ice1712/ice1712.o
> >   CC      drivers/char/ipmi/ipmi_watchdog.o
> >   CC      fs/overlayfs/export.o
> >   CC      fs/nls/nls_cp936.o
> >   CC      drivers/char/ipmi/ipmi_poweroff.o
> >  ^Ckepler:~/tip>
> >
> > The '^C' there - it just stops, make never prints anything for me.
>
> Found something - seems to be related whether the build is going into a
> pipe or not.
>
>
> I usually build this way (directly or via a script):
>
>    make -j96 bzImage ARCH=x86 2>&1 | tee e
>
> Ctrl-C interruption is not handled by kbuild in this case:
>
>   CC      fs/jffs2/xattr_trusted.o
>   CC      sound/firewire/motu/motu-transaction.o
>   CC      sound/usb/clock.o
>   ^Ckepler:~/tip>
>
> Immediate prompt - no cleanup sequence.
>
> But if I do it without 'tee', I get the expected cleanup sequence by make:
>
>   kepler:~/tip> make -j96 bzImage ARCH=x86 2>&1
>
>   CC      fs/jffs2/acl.o
>   CC      sound/pci/echoaudio/mona.o
>   CC      fs/nls/nls_iso8859-9.o
>   ^Cmake[2]: *** Deleting file 'drivers/reset/core.o'
>     make[3]: *** Deleting file 'sound/pci/mixart/mixart.o'
>     make[3]: *** Deleting file 'sound/pci/emu10k1/voice.o'
>     make[2]: *** Deleting file 'fs/gfs2/aops.o'
>
> Thanks,
>
>         Ingo



Hmm, I do not know why GNU Make behaves like this...

I will ask about this in GNU Make ML.


-- 
Best Regards
Masahiro Yamada

  reply	other threads:[~2021-06-04  3:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 15:50 Ingo Molnar
2021-06-02 18:20 ` Masahiro Yamada
2021-06-03 12:39   ` Ingo Molnar
2021-06-03 12:43     ` Ingo Molnar
2021-06-04  3:22       ` Masahiro Yamada [this message]
2021-06-09 13:59         ` Masahiro Yamada
2021-06-12 13:25           ` Ingo Molnar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAK7LNAQ73zG69F4hMJhgrHp8yT9tUmb-0tN=kFtWA98-YV3eNA@mail.gmail.com' \
    --to=masahiroy@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michal.lkml@markovi.net \
    --cc=mingo@kernel.org \
    --subject='Re: kbuild: Ctrl-C of parallel kernel build sometimes corrupts .o.cmd files permanently' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).