From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jeffrey C Honig <jeffrey.honig@windriver.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] siggen.py: Insure .siginfo files writes into shared sstate cache are atomic
Date: Tue, 17 Jul 2012 10:53:15 +0100 [thread overview]
Message-ID: <1342518795.10484.3.camel@ted> (raw)
In-Reply-To: <1342486137-9149-1-git-send-email-jeffrey.honig@windriver.com>
On Mon, 2012-07-16 at 20:48 -0400, Jeffrey C Honig wrote:
> Use tempfile.mkstemp to create a temporary file in the sstate dir and move it
> into place after closing. The previous code would fail in the chmod() if two
> users were running jobs that touched the same signature file.
>
> Signed-off-by: Jeffrey C Honig <jeffrey.honig@windriver.com>
> ---
> lib/bb/siggen.py | 19 +++++++++++++++----
> 1 files changed, 15 insertions(+), 4 deletions(-)
Merged to master, thanks.
Richard
next prev parent reply other threads:[~2012-07-17 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-17 0:48 [PATCH] siggen.py: Insure .siginfo files writes into shared sstate cache are atomic Jeffrey C Honig
2012-07-17 9:53 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-07-17 0:27 Jeffrey C Honig
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=1342518795.10484.3.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=jeffrey.honig@windriver.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox