All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12911] New: usb_modeswitch installation race condition
Date: Sat, 16 May 2020 16:40:10 +0000	[thread overview]
Message-ID: <bug-12911-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=12911

            Bug ID: 12911
           Summary: usb_modeswitch installation race condition
           Product: buildroot
           Version: 2020.02.2
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: jharjuma at gmail.com
                CC: buildroot at uclibc.org
  Target Milestone: ---

In usb_modeswitch Makefile dispatcher-script, dispatcher-dynlink and
dispatcher-statlink are .PHONY targets. The result is that sources are compiled
also when install targets are called. USB_MODESWITCH_INSTALL_TARGET_CMDS calls
$(MAKE) which is a call to parallel make eg. make -j9. So the install phase can
install empty usb_modeswitch binary (happened once) if the compiler have just
cleared the binary and install command installs it before compiler writes the
binary. USB_MODESWITCH_INSTALL_TARGET_CMDS should call $(MAKE1).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2020-05-16 16:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-16 16:40 bugzilla at busybox.net [this message]
2020-05-17  9:06 ` [Buildroot] [Bug 12911] usb_modeswitch installation race condition bugzilla at busybox.net
2020-05-18  4:25 ` bugzilla at busybox.net
2020-06-01 10:21 ` bugzilla at busybox.net
2020-09-04 14:59 ` bugzilla at busybox.net

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=bug-12911-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.