From: Peter Kjellerstedt <pkj@axis.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [RFC][PATCH] server/process: Avoid hanging if a parser process is terminated
Date: Sat, 26 Mar 2022 06:18:34 +0100 [thread overview]
Message-ID: <20220326051834.7244-1-pkj@axis.com> (raw)
If a parser process is terminated while holding a write lock, then it
will lead to a deadlock (see
https://docs.python.org/3/library/multiprocessing.html#multiprocessing.Process.terminate).
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
---
After the discussion on IRC about the hanging parsing processes, I
just had to understand the code and what happens. This is a solution to
the problem, though I am not sure it is THE solution. It may also be
that the rlock in ConnectionReader should be handled the same way.
Anyway, even if this is not accepted as a solution to the problem, I now
at least know a lot more about how the parsing processes in bitbake
work... :)
bitbake/lib/bb/server/process.py | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/bitbake/lib/bb/server/process.py b/bitbake/lib/bb/server/process.py
index 1636616660..544b00f2cd 100644
--- a/bitbake/lib/bb/server/process.py
+++ b/bitbake/lib/bb/server/process.py
@@ -20,6 +20,7 @@ import os
import sys
import time
import select
+import signal
import socket
import subprocess
import errno
@@ -728,6 +729,10 @@ class ConnectionReader(object):
def close(self):
return self.reader.close()
+terminated = False
+def catch_sigterm(signum, frame):
+ global terminated
+ terminated = True
class ConnectionWriter(object):
@@ -739,8 +744,12 @@ class ConnectionWriter(object):
def send(self, obj):
obj = multiprocessing.reduction.ForkingPickler.dumps(obj)
+ oldsig = signal.signal(signal.SIGTERM, catch_sigterm)
with self.wlock:
self.writer.send_bytes(obj)
+ signal.signal(signal.SIGTERM, oldsig)
+ if terminated:
+ os.kill(os.getpid(), signal.SIGTERM)
def fileno(self):
return self.writer.fileno()
reply other threads:[~2022-03-26 5:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220326051834.7244-1-pkj@axis.com \
--to=pkj@axis.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox