Austin Group Defect Tracker

Aardvark Mark IV


Viewing Issue Simple Details Jump to Notes ] Issue History ] Print ]
ID Category Severity Type Date Submitted Last Update
0000904 [1003.1(2013)/Issue7+TC1] Rationale Editorial Error 2014-12-12 16:24 2019-06-10 08:54
Reporter nick View Status public  
Assigned To
Priority normal Resolution Accepted As Marked  
Status Closed  
Name Nick Stoughton
Organization USENIX
User Reference nms-threadsafe-rationale
Section B.2.9.1 Thread-Safety
Page Number 3606
Line Number 122868
Interp Status ---
Final Accepted Text Note: 0002520
Summary 0000904: Rationale uses non-existant limit {PIPE_MAX}
Description The first sentence of the second paragraph reads

While a read from a pipe of {PIPE_MAX}*2 bytes may not generate a single atomic and thread-safe stream of bytes, it should generate ‘‘several’’ (individually atomic) thread-safe streams of bytes.


However, a search for "PIPE_MAX" throughout the standard finds only one other (non-index) mention of PIPE_MAX, in the rationale for write():

The concept of a {PIPE_MAX} limit (indicating the maximum number of bytes that can be written to a pipe in a single operation) was considered, but rejected, because this concept would unnecessarily limit application writing.


These two conflicting pieces of rationale should be aligned.
Desired Action On page 3606, line 122868, change

While a read from a pipe of {PIPE_MAX}*2 bytes may not generate a single atomic ...

To

While a read from a pipe may not generate a single atomic ...
Tags tc2-2008
Attached Files

- Relationships

-  Notes
(0002498)
nick (manager)
2014-12-12 16:36

Alternatively, change PIPE_MAX to PIPE_BUF in this sentence.
(0002501)
joerg (reporter)
2014-12-16 13:24

I would prefer to change PIPE_MAX to PIPE_BUF as this is most likely the intended text.

Note that PIPE_MAX is the pre-POSIX name.
(0002520)
Don Cragun (manager)
2015-01-08 17:28

On page 3606, line 122868, change
While a read from a pipe of {PIPE_MAX}*2 bytes may not generate a single atomic ...

to:
While a read from a pipe of {PIPE_BUF}*2 bytes may not generate a single atomic ...

- Issue History
Date Modified Username Field Change
2014-12-12 16:24 nick New Issue
2014-12-12 16:24 nick Name => Nick Stoughton
2014-12-12 16:24 nick Organization => USENIX
2014-12-12 16:24 nick User Reference => nms-threadsafe-rationale
2014-12-12 16:24 nick Section => B.2.9.1 Thread-Safety
2014-12-12 16:24 nick Page Number => 3606
2014-12-12 16:24 nick Line Number => 122868
2014-12-12 16:24 nick Interp Status => ---
2014-12-12 16:36 nick Note Added: 0002498
2014-12-16 13:24 joerg Note Added: 0002501
2015-01-08 17:28 Don Cragun Note Added: 0002520
2015-01-08 17:29 geoffclare Final Accepted Text => Note: 0002520
2015-01-08 17:29 geoffclare Status New => Resolved
2015-01-08 17:29 geoffclare Resolution Open => Accepted As Marked
2015-01-08 17:29 geoffclare Tag Attached: tc2-2008
2019-06-10 08:54 agadmin Status Resolved => Closed


Mantis 1.1.6[^]
Copyright © 2000 - 2008 Mantis Group
Powered by Mantis Bugtracker