Bug 108016
Summary: | Problem with vfork in GNU version 3.2.2 | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Mohan Mohta <mohan_mohta> |
Component: | kernel | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-10-27 09:23:52 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Mohan Mohta
2003-10-26 10:28:33 UTC
Your testcase is ill-formed. See man vfork: "except that the behaviour is undefined if the process created by vfork() either ... , or returns from the function in which vfork() was called" That's exactly what you're trying to do. The difference between vfork and fork is that vfork provides performance boost but makes very strong requirements what you can and what you cannot do. |