A NOTE has been added to this issue. 
====================================================================== 
https://www.austingroupbugs.net/view.php?id=1830 
====================================================================== 
Reported By:                lacos
Assigned To:                
====================================================================== 
Project:                    1003.1(2016/18)/Issue7+TC2
Issue ID:                   1830
Category:                   System Interfaces
Type:                       Enhancement Request
Severity:                   Editorial
Priority:                   normal
Status:                     New
Name:                       László Érsek 
Organization:                
User Reference:              
Section:                    pwrite, write 
Page Number:                ? 
Line Number:                ? 
Interp Status:              --- 
Final Accepted Text:         
====================================================================== 
Date Submitted:             2024-05-03 06:55 UTC
Last Modified:              2024-05-19 10:26 UTC
====================================================================== 
Summary:                    off-by-one error regarding offset maximum
====================================================================== 

---------------------------------------------------------------------- 
 (0006785) lacos (reporter) - 2024-05-19 10:26
 https://www.austingroupbugs.net/view.php?id=1830#c6785 
---------------------------------------------------------------------- 
My reason for covering pwrite() as well is the following: an application
may maintain a separate off_t variable for recording the exclusive end
offset of a successful pwrite() call -- effectively the same offset to
which an equivalent write() call would set the file offset inside the
underlying open file description. Given that the spec intends to prevent
the file offset inside the open file description from overflowing upon a
write(), the same guarantee should be extended to an application that
captures the same "exclusive end of successful data transfer" concept in an
off_t object. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2024-05-03 06:55 lacos          New Issue                                    
2024-05-03 06:55 lacos          Name                      => László Érsek 
2024-05-03 06:55 lacos          Section                   => pwrite, write   
2024-05-03 06:55 lacos          Page Number               => ?               
2024-05-03 06:55 lacos          Line Number               => ?               
2024-05-13 09:10 geoffclare     Note Added: 0006778                          
2024-05-19 10:20 lacos          Note Added: 0006784                          
2024-05-19 10:26 lacos          Note Added: 0006785                          
======================================================================


  • [1003.1(2016... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group
    • [1003.1... Austin Group Bug Tracker via austin-group-l at The Open Group

Reply via email to