A NOTE has been added to this issue. 
====================================================================== 
https://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-20 08:16 UTC
====================================================================== 
Summary:                    off-by-one error regarding offset maximum
====================================================================== 

---------------------------------------------------------------------- 
 (0006786) geoffclare (manager) - 2024-05-20 08:16
 https://austingroupbugs.net/view.php?id=1830#c6786 
---------------------------------------------------------------------- 
Good catch that my proposed fix doesn't work for pwrite().  Having looked
into it some more, I notice that the wording of the associated EFBIG error
works fine for both:<blockquote>[EFBIG]<blockquote>The file is a regular
file, <i>nbyte</i> is greater than 0, and the starting position is greater
than or equal to the offset maximum established in the open file
description associated with <i>fildes</i>.</blockquote></blockquote>
So I think the text in the description should be worded in a similar way.
The only difference is that the description needs to allow for writes that
start before the offset maximum but would extend beyond it (if all
requested bytes were written).

Change:<blockquote>For regular files, no data transfer shall occur past the
offset maximum established in the open file description associated with
<i>fildes</i>.</blockquote>to:<blockquote>For regular files, no data shall
be written at positions greater than or equal to the offset maximum
established in the open file description associated with <i>fildes</i>. If
the starting position is greater than or equal to the offset maximum (and
<i>nbyte</i> is greater than 0), the request shall fail; otherwise, only as
many bytes as there is room for shall be written.</blockquote> 

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                          
2024-05-20 08:16 geoffclare     Note Added: 0006786                          
======================================================================


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

Reply via email to