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.
Bug 601192 - fork causes trouble for vcpu threads
Summary: fork causes trouble for vcpu threads
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: kernel
Version: 6.0
Hardware: All
OS: Linux
low
medium
Target Milestone: rc
: ---
Assignee: Glauber Costa
QA Contact: Virtualization Bugs
URL:
Whiteboard:
: 585195 (view as bug list)
Depends On:
Blocks: 579026 606953
TreeView+ depends on / blocked
 
Reported: 2010-06-07 12:42 UTC by Gerd Hoffmann
Modified: 2013-01-09 22:41 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 606953 (view as bug list)
Environment:
Last Closed: 2010-07-09 02:10:35 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Gerd Hoffmann 2010-06-07 12:42:34 UTC 
Description of problem:
Guest stops running when qemu receives SIGCHILD.

Version-Release number of selected component (if applicable):
qemu-kvm-0.12.1.2-2.69.el6.x86_64

How reproducible:
(1) boot guest
(2) make qemu fork+exec something which exits quicky.
    "netdev_add tap,id=foo,script=/bin/true" will do.
  
Actual results:
Guest stops running.

Expected results:
Guest continues running.

Additional info:
Disabling the qemu SIGCHLD signal handler makes the problem disappear.  Not a good idea though.

Blocking SIGCHLD in the vcpu threads works too.  Not sure this is the correct fix or whenever it just papers over the underlying bug.
Comment 2 RHEL Program Management 2010-06-07 17:03:19 UTC 
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux major release.  Product Management has requested further
review of this request by Red Hat Engineering, for potential inclusion in a Red
Hat Enterprise Linux Major release.  This request is not yet committed for
inclusion.
Comment 3 Gerd Hoffmann 2010-06-08 08:58:16 UTC 
Glauber, can you put your io-thread hat on and either comment on the possible fixes outlined in "Additional info" above or just grab this bug and handle it?
Comment 4 Glauber Costa 2010-06-08 17:47:38 UTC 
Gerd,

I made some comments on this bug yesterday. Somehow, they are missing, no idea why.
I am already working on it.
Comment 5 Glauber Costa 2010-06-10 18:48:00 UTC 
Ok, some more info:

It doesn't seem to happen with -no-kvm-irqchip. Investigating, I've found that after the receival of SIGCHLD, the kernel is blocked in kvm_vcpu_block. Also,
it is hardly triggable when the guest kernel hasn't reached userspace yet (probably because it halts less, during kernel boot).

The funny thing is that it never happens when one just sends SIGCHLD to the process. The signal handler is executed, but the problem does not appear.

I believe there is a race somewhere, where we consume a SIGCHLD when expecting SIG_IPI, and then this other signal is lost.

But right now, my biggest belief is that there is a race bug somewhere in the kernel, in the in-kernel apic implementation.
Comment 6 Glauber Costa 2010-06-10 19:45:03 UTC 
Ok, I now reproduce it even when disabling the SIGCHLD signal handler.

This is conforming to my theory that we have a race with sigpending status.
Comment 7 Aristeu Rozanski 2010-07-01 16:23:13 UTC 
Patch(es) available on kernel-2.6.32-42.el6
Comment 10 Cao, Chen 2010-07-05 12:07:22 UTC 
I have tried on 
# uname -r
2.6.32-42.el6.x86_64

for tens of times, and cannot reproduce this bug.


but on
# uname -r
2.6.32-39.el6.x86_64

I can, sometimes, find the guest machine (rhel6) cannot execute commands
completely, i.e.
#  ping 127.0.0.1
PING 127.0.0.1 (127.0.0.1) 56(84) bytes of data.
64 bytes from 127.0.0.1: icmp_seq=1 ttl=64 time=0.034 ms

and cannot go on any more.

and "top", "reboot" and some other commands cannot return any thing.

anyway, I cannot reproduce this on 2.6.32-42.el6.x86_64 kernel.


Additional info:
# rpm -q qemu-kvm
qemu-kvm-0.12.1.2-2.90.el6.x86_64

command that starts vm:
qemu-kvm -name vm1 -monitor stdio -drive file=./RHEL-Server-6.0-64.qcow2,if=ide,cache=none,aio=native  -m 2048 -smp 2 -vnc :0 -spice port=8000,disable-ticketing -usbdevice tablet -rtc-td-hack -cpu qemu64,+sse2 -no-kvm-pit-reinjection -net nic,vlan=0,netdev=DWxy,model=rtl8139,macaddr='02:6F:F6:3D:b9:b2' -netdev tap,id=DWxy,ifname=rtl8139_0_8000,script=.scripts/qemu-ifup-switch,downscript=no


command that trys to trigger this bug:
netdev_add tap,id=foo,script=/bin/true
Comment 11 Dor Laor 2010-07-12 09:31:44 UTC 
*** Bug 585195 has been marked as a duplicate of this bug. ***
Note You need to log in before you can comment on or make changes to this bug.