[1003.1(2016)/Issue7+TC2 0001118]: Clarify meaning of "file lock"
The following issue has a resolution that has been APPLIED. == http://austingroupbugs.net/view.php?id=1118 == Reported By:rpalethorpe Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1118 Category: Base Definitions and Headers Type: Clarification Requested Severity: Comment Priority: normal Status: Applied Name: Richard Palethorpe Organization: SUSE User Reference: Section:fork, fcntl, flockfile Page Number:fork Line Number:20ish Interp Status: --- Final Accepted Text:http://austingroupbugs.net/view.php?id=1118#c4061 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2017-01-20 13:05 UTC Last Modified: 2019-10-30 10:58 UTC == Summary:Clarify meaning of "file lock" == Relationships ID Summary -- related to 0001112 mutex/rwlock ownership after fork is un... == Issue History Date ModifiedUsername FieldChange == 2017-01-20 13:05 rpalethorpeNew Issue 2017-01-20 13:05 rpalethorpeName => Richard Palethorpe 2017-01-20 13:05 rpalethorpeOrganization => SUSE 2017-01-20 13:05 rpalethorpeSection => fork, fcntl, flockfile 2017-01-20 13:05 rpalethorpePage Number => fork 2017-01-20 13:05 rpalethorpeLine Number => 20ish 2017-01-20 14:36 rpalethorpeNote Added: 0003558 2018-07-26 15:11 nick Relationship added related to 0001112 2018-07-26 16:06 geoffclare Note Added: 0004061 2018-07-26 16:07 geoffclare Interp Status => --- 2018-07-26 16:07 geoffclare Final Accepted Text => http://austingroupbugs.net/view.php?id=1118#c4061 2018-07-26 16:07 geoffclare Status New => Resolved 2018-07-26 16:07 geoffclare Resolution Open => Accepted As Marked 2018-07-26 16:08 geoffclare Tag Attached: tc3-2008 2018-07-26 16:42 shware_systems Note Added: 0004063 2019-10-30 10:58 geoffclare Status Resolved => Applied ==
[1003.1(2016)/Issue7+TC2 0001118]: Clarify meaning of "file lock"
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1118 == Reported By:rpalethorpe Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1118 Category: Base Definitions and Headers Type: Clarification Requested Severity: Comment Priority: normal Status: Resolved Name: Richard Palethorpe Organization: SUSE User Reference: Section:fork, fcntl, flockfile Page Number:fork Line Number:20ish Interp Status: --- Final Accepted Text:http://austingroupbugs.net/view.php?id=1118#c4061 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2017-01-20 13:05 UTC Last Modified: 2018-07-26 16:42 UTC == Summary:Clarify meaning of "file lock" == Relationships ID Summary -- related to 0001112 mutex/rwlock ownership after fork is un... == -- (0004063) shware_systems (reporter) - 2018-07-26 16:42 http://austingroupbugs.net/view.php?id=1118#c4063 -- Additional note based on phone discussion: page 497 line 17271: Note that after a fork( ), two handles (Ed: either file descriptor or FILE * in this context) exist where one existed before. The application shall ensure that, if both handles can ever be accessed, they are both in a state where the other could become the active handle first. The application shall prepare for a fork( ) exactly as if it were a change of active handle. (If the only action performed by one of the processes is one of the exec functions or _exit( ) (not exit( )), the handle is never accessed in that process.) This apparently includes it being the application's responsibility to unlock any locks established by fcntl() or f(try)lockfile() on the stream, whether the application is single or multi-threaded, before attempting the call to fork() so either parent or child process may establish a new lock without blocking, if desired, and otherwise the behavior is undefined. Issue History Date ModifiedUsername FieldChange == 2017-01-20 13:05 rpalethorpeNew Issue 2017-01-20 13:05 rpalethorpeName => Richard Palethorpe 2017-01-20 13:05 rpalethorpeOrganization => SUSE 2017-01-20 13:05 rpalethorpeSection => fork, fcntl, flockfile 2017-01-20 13:05 rpalethorpePage Number => fork 2017-01-20 13:05 rpalethorpeLine Number => 20ish 2017-01-20 14:36 rpalethorpeNote Added: 0003558 2018-07-26 15:11 nick Relationship added related to 0001112 2018-07-26 16:06 geoffclare Note Added: 0004061 2018-07-26 16:07 geoffclare Interp Status => --- 2018-07-26 16:07 geoffclare Final Accepted Text => http://austingroupbugs.net/view.php?id=1118#c4061 2018-07-26 16:07 geoffclare Status New => Resolved 2018-07-26 16:07 geoffclare Resolution Open => Accepted As Marked 2018-07-26 16:08 geoffclare Tag Attached: tc3-2008 2018-07-26 16:42 shware_systems Note Added: 0004063 ==
[1003.1(2016)/Issue7+TC2 0001118]: Clarify meaning of "file lock"
The following issue has been RESOLVED. == http://austingroupbugs.net/view.php?id=1118 == Reported By:rpalethorpe Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1118 Category: Base Definitions and Headers Type: Clarification Requested Severity: Comment Priority: normal Status: Resolved Name: Richard Palethorpe Organization: SUSE User Reference: Section:fork, fcntl, flockfile Page Number:fork Line Number:20ish Interp Status: --- Final Accepted Text:http://austingroupbugs.net/view.php?id=1118#c4061 Resolution: Accepted As Marked Fixed in Version: == Date Submitted: 2017-01-20 13:05 UTC Last Modified: 2018-07-26 16:07 UTC == Summary:Clarify meaning of "file lock" == Relationships ID Summary -- related to 0001112 mutex/rwlock ownership after fork is un... == Issue History Date ModifiedUsername FieldChange == 2017-01-20 13:05 rpalethorpeNew Issue 2017-01-20 13:05 rpalethorpeName => Richard Palethorpe 2017-01-20 13:05 rpalethorpeOrganization => SUSE 2017-01-20 13:05 rpalethorpeSection => fork, fcntl, flockfile 2017-01-20 13:05 rpalethorpePage Number => fork 2017-01-20 13:05 rpalethorpeLine Number => 20ish 2017-01-20 14:36 rpalethorpeNote Added: 0003558 2018-07-26 15:11 nick Relationship added related to 0001112 2018-07-26 16:06 geoffclare Note Added: 0004061 2018-07-26 16:07 geoffclare Interp Status => --- 2018-07-26 16:07 geoffclare Final Accepted Text => http://austingroupbugs.net/view.php?id=1118#c4061 2018-07-26 16:07 geoffclare Status New => Resolved 2018-07-26 16:07 geoffclare Resolution Open => Accepted As Marked ==
[1003.1(2016)/Issue7+TC2 0001118]: Clarify meaning of "file lock"
A NOTE has been added to this issue. == http://austingroupbugs.net/view.php?id=1118 == Reported By:rpalethorpe Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1118 Category: Base Definitions and Headers Type: Clarification Requested Severity: Comment Priority: normal Status: New Name: Richard Palethorpe Organization: SUSE User Reference: Section:fork, fcntl, flockfile Page Number:fork Line Number:20ish Interp Status: --- Final Accepted Text: == Date Submitted: 2017-01-20 13:05 UTC Last Modified: 2018-07-26 16:06 UTC == Summary:Clarify meaning of "file lock" == Relationships ID Summary -- related to 0001112 mutex/rwlock ownership after fork is un... == -- (0004061) geoffclare (manager) - 2018-07-26 16:06 http://austingroupbugs.net/view.php?id=1118#c4061 -- On page 60 line 1795 section 3 add a new subsection:3.168 File Lock A lock obtained on a file through the use of fcntl() or lockf().and renumber the later 3.x subsections. On page 874 after line 29515, add to flockfile APPLICATION USAGE:Note: a FILE lock is not a file lock (see XREF to XBD 3.168). On page 875 line 29518 section flockfile(), change:acquire a file lockto:acquire a FILE lock Issue History Date ModifiedUsername FieldChange == 2017-01-20 13:05 rpalethorpeNew Issue 2017-01-20 13:05 rpalethorpeName => Richard Palethorpe 2017-01-20 13:05 rpalethorpeOrganization => SUSE 2017-01-20 13:05 rpalethorpeSection => fork, fcntl, flockfile 2017-01-20 13:05 rpalethorpePage Number => fork 2017-01-20 13:05 rpalethorpeLine Number => 20ish 2017-01-20 14:36 rpalethorpeNote Added: 0003558 2018-07-26 15:11 nick Relationship added related to 0001112 2018-07-26 16:06 geoffclare Note Added: 0004061 ==
[1003.1(2016)/Issue7+TC2 0001118]: Clarify meaning of "file lock"
The following issue has been set as RELATED TO issue 0001112. == http://austingroupbugs.net/view.php?id=1118 == Reported By:rpalethorpe Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1118 Category: Base Definitions and Headers Type: Clarification Requested Severity: Comment Priority: normal Status: New Name: Richard Palethorpe Organization: SUSE User Reference: Section:fork, fcntl, flockfile Page Number:fork Line Number:20ish Interp Status: --- Final Accepted Text: == Date Submitted: 2017-01-20 13:05 UTC Last Modified: 2018-07-26 15:11 UTC == Summary:Clarify meaning of "file lock" == Relationships ID Summary -- related to 0001112 mutex/rwlock ownership after fork is un... == Issue History Date ModifiedUsername FieldChange == 2017-01-20 13:05 rpalethorpeNew Issue 2017-01-20 13:05 rpalethorpeName => Richard Palethorpe 2017-01-20 13:05 rpalethorpeOrganization => SUSE 2017-01-20 13:05 rpalethorpeSection => fork, fcntl, flockfile 2017-01-20 13:05 rpalethorpePage Number => fork 2017-01-20 13:05 rpalethorpeLine Number => 20ish 2017-01-20 14:36 rpalethorpeNote Added: 0003558 2018-07-26 15:11 nick Relationship added related to 0001112 ==
[1003.1(2016)/Issue7+TC2 0001118]: Clarify meaning of "file lock"
The following issue has been SUBMITTED. == http://austingroupbugs.net/view.php?id=1118 == Reported By:rpalethorpe Assigned To: == Project:1003.1(2016)/Issue7+TC2 Issue ID: 1118 Category: Base Definitions and Headers Type: Clarification Requested Severity: Comment Priority: normal Status: New Name: Richard Palethorpe Organization: SUSE User Reference: Section:fork, fcntl, flockfile Page Number:fork Line Number:20ish Interp Status: --- Final Accepted Text: == Date Submitted: 2017-01-20 13:05 UTC Last Modified: 2017-01-20 13:05 UTC == Summary:Clarify meaning of "file lock" Description: In http://pubs.opengroup.org/onlinepubs/9699919799/ (fork) it states that "File locks set by the parent process shall not be inherited by the child process.". As far as I can tell, the phrase 'file lock', is not explicitly defined and there are at least two types of lock which could be described as a 'file lock'. One is the type of lock established by fcntl(), which states in its rationale that locks are not inherited through fork(). The other is a lock established by flockfile() which makes no mention of fork(). Furthermore, in this context, the term 'inherited' could be taken to mean that the lock's data structures are copied to the child or that the ownership of the lock is inherited by the child (i.e. the child can access a file locked by the parent) or that the child is subject to restrictions imposed by the locks (i.e. it can't access a locked file). This may or may not be related to: http://austingroupbugs.net/view.php?id=1112 Desired Action: 1. Explicitly state the types of lock meant by 'file lock' 2. Elaborate on the term 'inherit' in the context of file locks during a process fork or cite its definition. == Issue History Date ModifiedUsername FieldChange == 2017-01-20 13:05 rpalethorpeNew Issue 2017-01-20 13:05 rpalethorpeName => Richard Palethorpe 2017-01-20 13:05 rpalethorpeOrganization => SUSE 2017-01-20 13:05 rpalethorpeSection => fork, fcntl, flockfile 2017-01-20 13:05 rpalethorpePage Number => fork 2017-01-20 13:05 rpalethorpeLine Number => 20ish ==
