A NOTE has been added to this issue. 
====================================================================== 
http://austingroupbugs.net/view.php?id=1114 
====================================================================== 
Reported By:                Florian Weimer
Assigned To:                
====================================================================== 
Project:                    1003.1(2016)/Issue7+TC2
Issue ID:                   1114
Category:                   System Interfaces
Type:                       Clarification Requested
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       Florian Weimer 
Organization:               Red Hat 
User Reference:              
Section:                    fork 
Page Number:                unknown 
Line Number:                unknown 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2017-01-12 16:05 UTC
Last Modified:              2018-07-19 15:22 UTC
====================================================================== 
Summary:                    Clarify if fork preserves thread resources
====================================================================== 

---------------------------------------------------------------------- 
 (0004055) geoffclare (manager) - 2018-07-19 15:22
 http://austingroupbugs.net/view.php?id=1114#c4055 
---------------------------------------------------------------------- 
On page 899 line 30368 section fork(), change APPLICATION USAGE
from:<blockquote>None.</blockquote>to:<blockquote>When a multi-threaded
process calls <i>fork</i>(), although all memory that is addressable in the
calling thread remains addressable in the child, there is no guarantee that
the contents of thread-specific memory, such as stacks or thread-local
storage, that was specific to other threads in the parent will still be the
same in the child.  This is because such memory could be treated as
available in the child given that the threads it related to do not exist in
the child, and consequently the processing performed in the child before
<i>fork</i>() returns could make use of that memory.  Therefore
applications should avoid using in the child any pointers to
thread-specific memory that were passed to the calling thread from other
threads in the parent.</blockquote> 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2017-01-12 16:05 Florian Weimer New Issue                                    
2017-01-12 16:05 Florian Weimer Name                      => Florian Weimer  
2017-01-12 16:05 Florian Weimer Organization              => Red Hat         
2017-01-12 16:05 Florian Weimer Section                   => fork            
2017-01-12 16:05 Florian Weimer Page Number               => unknown         
2017-01-12 16:05 Florian Weimer Line Number               => unknown         
2017-01-12 16:50 torvald        Note Added: 0003541                          
2017-01-12 16:50 torvald        Issue Monitored: torvald                     
2017-05-19 20:20 slow           Issue Monitored: slow                        
2017-10-30 16:35 Florian Weimer Issue Monitored: Florian Weimer                 
  
2018-07-19 15:20 geoffclare     Note Added: 0004054                          
2018-07-19 15:22 geoffclare     Note Added: 0004055                          
======================================================================


Reply via email to