Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 484319[details]
test application
Description of problem:
libquestfs can call waitpid(0,..) causing it to wait on all
child processes (including processes started by the application).
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. exec a process
2. start a guestfs session
3. call kill_subprocesses()
4. call 'del g_obj'
Actual results:
my test application blocks in a waitpid(0,..) call
Expected results:
it should not cause my application to block
Additional info:
I'll attach a test application and patch.
Comment 4Richard W.M. Jones
2011-03-14 22:40:41 UTC
Angus, please test this and also provide some sort of easy(-ish)
test that QA can perform to verify that it is fixed in RHEL 6.2.
A small snippet of C code which fails before and succeeds after
would be ideal.
(In reply to comment #4)
> Angus, please test this and also provide some sort of easy(-ish)
> test that QA can perform to verify that it is fixed in RHEL 6.2.
Already attached is a python test case, super easy to run.
just edit and replace my iso with what ever iso you have then
if it locks up - FAIL, if it exits nicely the PASS.
> A small snippet of C code which fails before and succeeds after
> would be ideal.
I have tested and it seems I missed a "if (pid > 0)".
I will attach an extra patch that makes my test case pass.
Reproduced on libguestfs-1.7.17-19 running the forker test.
$ python forker.py
qpidd(14137) is running
2011-08-29 11:16:28 notice SASL disabled: No Authentication Performed
2011-08-29 11:16:28 notice Listening on TCP port 49000
2011-08-29 11:16:28 notice Broker running
The program hangs here.
Verified on libguestfs-1.7.17-26 that the test could exit without hang.
$ python forker.py
qpidd(14023) is running
2011-08-29 11:06:04 notice SASL disabled: No Authentication Performed
2011-08-29 11:06:04 notice Listening on TCP port 49000
2011-08-29 11:06:04 notice Broker running
2011-08-29 11:06:08 notice Shut down
qpidd(14023) exited with 0
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1512.html
Created attachment 484319 [details] test application Description of problem: libquestfs can call waitpid(0,..) causing it to wait on all child processes (including processes started by the application). Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. exec a process 2. start a guestfs session 3. call kill_subprocesses() 4. call 'del g_obj' Actual results: my test application blocks in a waitpid(0,..) call Expected results: it should not cause my application to block Additional info: I'll attach a test application and patch.