From: Joshua Watt <jpewhacker@gmail.com>
To: bitbake-devel@lists.openembedded.org
Cc: Joshua Watt <JPEWhacker@gmail.com>
Subject: [bitbake-devel][PATCH] siggen: Fix sigtask data not being renamed atomically
Date: Mon, 1 Aug 2022 15:34:18 -0500 [thread overview]
Message-ID: <20220801203418.57677-1-JPEWhacker@gmail.com> (raw)
Signature generation uses mkstemp() to get a file descriptor to a unique
file and then write the signature into it, however it closed the file
before doing the chmod() and rename() operations. Closing the file means
that other mkstemp() could potentially open the same file and race with
the chmod() and rename(), causing a error. While it may not sound like
this would be very likely, glibc (at least) generates the filename for
mkstemp() using the system clock, meaning that it is much more likely
for highly parallel builds sharing sstate over NFS to encounter the race
condition.
To fix the problem, perform the chmod() and rename() while the file is
still open, since this prevents other mkstemp() calls from being able to
open the file (due to the O_EXCL flag).
Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
bitbake/lib/bb/siggen.py | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/bitbake/lib/bb/siggen.py b/bitbake/lib/bb/siggen.py
index 3f3d6df54d..55f25235df 100644
--- a/bitbake/lib/bb/siggen.py
+++ b/bitbake/lib/bb/siggen.py
@@ -426,18 +426,18 @@ class SignatureGeneratorBasic(SignatureGenerator):
sigfile = sigfile.replace(self.taskhash[tid], computed_taskhash)
fd, tmpfile = tempfile.mkstemp(dir=os.path.dirname(sigfile), prefix="sigtask.")
- try:
- with bb.compress.zstd.open(fd, "wt", encoding="utf-8", num_threads=1) as f:
+ with bb.compress.zstd.open(fd, "wt", encoding="utf-8", num_threads=1) as f:
+ try:
json.dump(data, f, sort_keys=True, separators=(",", ":"), cls=SetEncoder)
f.flush()
- os.chmod(tmpfile, 0o664)
- bb.utils.rename(tmpfile, sigfile)
- except (OSError, IOError) as err:
- try:
- os.unlink(tmpfile)
- except OSError:
- pass
- raise err
+ os.chmod(tmpfile, 0o664)
+ bb.utils.rename(tmpfile, sigfile)
+ except (OSError, IOError) as err:
+ try:
+ os.unlink(tmpfile)
+ except OSError:
+ pass
+ raise err
def dump_sigfn(self, fn, dataCaches, options):
if fn in self.taskdeps:
--
2.33.0
next reply other threads:[~2022-08-01 20:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 20:34 Joshua Watt [this message]
2022-08-01 21:05 ` [bitbake-devel][PATCH] siggen: Fix sigtask data not being renamed atomically Christopher Larson
2022-08-02 13:14 ` [bitbake-devel][PATCH v2] " Joshua Watt
2022-08-03 11:40 ` Rasmus Villemoes
2022-08-03 13:21 ` Joshua Watt
2022-08-03 14:04 ` Joshua Watt
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=20220801203418.57677-1-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.com \
--cc=bitbake-devel@lists.openembedded.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.