diff options
| -rw-r--r-- | glibc/fork.mdwn | 18 | ||||
| -rw-r--r-- | open_issues/fork_mach_port_mod_refs_ekern_urefs_owerflow.mdwn | 5 |
2 files changed, 19 insertions, 4 deletions
diff --git a/glibc/fork.mdwn b/glibc/fork.mdwn index d1b26906..564d9d5b 100644 --- a/glibc/fork.mdwn +++ b/glibc/fork.mdwn @@ -34,8 +34,18 @@ operation. Perhaps we can learn from what they're been doing? Also, perhaps they have patches for software packages, to avoid using `fork` followed by `exec`, for example. ---- -We no longer support `MACH_IPC_COMPAT`, thus we can get rid of the `err = -__mach_port_allocate_name ([...]); if (err == KERN_NAME_EXISTS)` code[[!tag -open_issue_glibc]]. +# TODO + + * [[fork: mach_port_mod_refs: + EKERN_UREFS_OWERFLOW|open_issues/fork_mach_port_mod_refs_ekern_urefs_owerflow]] + ([[!taglink open_issue_glibc]]). + + * Include de-duplicate information from elsewhere: [[hurd-paper]], + [[hurd-talk]] [[hurd/ng/trivialconfinementvsconstructorvsfork]], + [[open_issues/resource_management_problems/zalloc_panics]] ([[!taglink + open_issue_glibc open_issue_documentation]]). + + * We no longer support `MACH_IPC_COMPAT`, thus we can get rid of the `err = + __mach_port_allocate_name ([...]); if (err == KERN_NAME_EXISTS)` code + ([[!taglink open_issue_glibc]]). diff --git a/open_issues/fork_mach_port_mod_refs_ekern_urefs_owerflow.mdwn b/open_issues/fork_mach_port_mod_refs_ekern_urefs_owerflow.mdwn index b6ecb92a..e80a5661 100644 --- a/open_issues/fork_mach_port_mod_refs_ekern_urefs_owerflow.mdwn +++ b/open_issues/fork_mach_port_mod_refs_ekern_urefs_owerflow.mdwn @@ -159,3 +159,8 @@ The error is 19, `EKERN_UREFS_OVERFLOW`. successfully.) [[!tag open_issue_glibc]] + + +# Discussion + +<http://lists.gnu.org/archive/html/bug-hurd/2010-11/msg00028.html> |