From: Darren Hart <dvhart@linux.intel.com>
To: Yu Ke <ke.yu@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 1/1] base.bbclass: add lock file for do_unpack task
Date: Tue, 04 Jan 2011 07:45:56 -0800 [thread overview]
Message-ID: <4D2340B4.4030601@linux.intel.com> (raw)
In-Reply-To: <6b19cf34c82bc4f083a420da7430ff60cbfcb815.1294140740.git.ke.yu@intel.com>
On 01/04/2011 03:36 AM, Yu Ke wrote:
> This patch intend to fix the random unpack failure of linux-libc-headers-yocto
> and linux-yocto.
>
> The root cause of the unpack failure is that: these two recpies has the same URL, thus
> has the same dest file during the fetch and unpack phase:
> do_fetch : create tar ball ${DL_DIR}/git_git.pokylinux.org.linux-yocto-2.6.37.tar.gz
> do_unpack : extract tar ball ${DL_DIR}/git_git.pokylinux.org.linux-yocto-2.6.37.tar.gz
> fetch phase is protected by lockfile, so it works fine. but unpack phase is not lock protected,
> thus there is race condition like: when linux-yocto do_unpack is extracting the tar ball,
> linux-libc-headers-yocto do_fetch starts to create tar ball thus overwrite linux-yocto's
> tar ball and cause linux-yocto do_unpack failure
>
> To fix this issue, do_unpack also need to be protected by lock
Nice work! My out-for-review trace-cmd and kernelshark recipes will
suffer the same issue.
--
Darren Hart
Yocto Linux Kernel
next prev parent reply other threads:[~2011-01-04 15:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 11:36 [PATCH 0/1] Fix random kernel unpack failure Yu Ke
2011-01-04 11:36 ` [PATCH 1/1] base.bbclass: add lock file for do_unpack task Yu Ke
2011-01-04 15:45 ` Darren Hart [this message]
2011-01-05 2:18 ` Cui, Dexuan
2011-01-04 19:51 ` [PATCH 0/1] Fix random kernel unpack failure Saul Wold
2011-01-05 2:00 ` Yu Ke
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=4D2340B4.4030601@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=ke.yu@intel.com \
--cc=poky@yoctoproject.org \
/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.