|
Home About Us A-Z Index Search * Contact Us Register Login Press ShopThe Open Brand -- Problem Reporting and Interpretations System |
Problem Report 2382 Details Show help | Quick Search | Submit a Test Suite Support Request | Click here to view your privileges
This page provides all information on Problem Report 2382.
Report 2382 Actions
Problem Report Number 2382 Submitter's Classification Test Suite problem State Resolved Resolution Test Suite Deficiency (TSD) Problem Resolution ID TSD.X.1231 Raised 2004-05-26 13:01 Updated 2004-05-29 03:16 Published 2004-05-29 03:16 Product Standard Internationalised System Calls and Libraries Extended V3 (UNIX 03) Certification Program The Open Brand certification program Test Suite VSX4 version 4.6.2 Test Identification POSIX.os/files/fpathconf 33
POSIX.os/files/pathconf 49Specification Base Definitions Issue 6 Problem Summary pathconf/fpathconf not allowing for "may fail" EINVAL condition. Problem Text From SUSv3's pathconf/fpathconf description:
RETURN VALUE
If name is an invalid value, both pathconf() and fpathconf()
shall return -1 and set errno to indicate the error.
...
ERRORS
The pathconf() function may fail if:
[EINVAL]
The implementation does not support an association of the
variable name with the specified file.
The -1 return with errno set to EINVAL is saying "The implementation
does not support Prioritized input or output operations on the specified
file." The "support an association of the variable name with" above with
_PC_PRIO_IO can be directly translated to "support Prioritized input or
output operation on".
Furthermore, text added to XSH6 2004 edition, page 408, L13261-13262
(RETURN VALUE section on the [f]pathconf() page):
If the variable corresonding to name is dependent on an
unsupported option, the results are unspecified.
says the test suite should not care because we do not claim to support
the Prioritized Input and Output option.
The tests are not allowing for the EINVAL "may fail" condition.Test Output
****************************************************************************************************************
/tset/POSIX.os/files/fpathconf/T.fpathconf 33 Failed
Test Description:
For UNIX03 and POSIX01 modes:
When the value of name is _PC_ALLOC_SIZE_MIN,
_PC_REC_INCR_XFER_SIZE, _PC_REC_MAX_XFER_SIZE,
_PC_REC_MIN_XFER_SIZE, _PC_REC_XFER_ALIGN, _PC_ASYNC_IO,
_PC_PRIO_IO or _PC_SYNC_IO, and fildes refers to a regular
file,
then fpathconf(fildes, name) either returns a value not
equal to
-1, or returns -1 without setting errno.
Test Strategy:
CREATE a file using creat().
SET errno to zero
IF fpathconf(fd, name) returns -1
VERIFY that errno is zero
Test Information:
fpathconf(fd, _PC_PRIO_IO) on "fpathcf-reg" did not give correct
results expected: return value != -1
OR: return value == -1, errno == 0 (NO ERROR)
observed: return value == -1, errno == 22 (EINVAL)
****************************************************************************************************************
****************************************************************************************************************
/tset/POSIX.os/files/pathconf/T.pathconf 49 Failed
Test Description:
For POSIX01 and UNIX03 modes:
When the value of name is _PC_ALLOC_SIZE_MIN,
_PC_REC_INCR_XFER_SIZE, _PC_REC_MAX_XFER_SIZE,
_PC_REC_MIN_XFER_SIZE, _PC_REC_XFER_ALIGN, _PC_ASYNC_IO,
_PC_PRIO_IO or _PC_SYNC_IO, and path refers to a regular
file,
then pathconf(path, name) either returns a value not equal
to -1,
or returns -1 without setting errno.
Test Strategy:
CREATE a file using creat().
SET errno to zero
IF pathconf(file, name) returns -1
VERIFY that errno is zero
Test Information:
pathconf("pathconf-t.49", _PC_PRIO_IO) did not give correct
results
expected: return value != -1
OR: return value == -1, errno == 0 (NO ERROR)
observed: return value == -1, errno == 22 (EINVAL)
****************************************************************************************************************Review Information
Review Type TSMA Review Start Date 2004-05-26 13:01 Last Updated 2004-05-26 20:13 Completed 2004-05-26 20:13 Status Complete Review Recommendation Test Suite Deficiency (TSD) Review Response This is accepted as a fault in the test suite.
Review Type SA Review Start Date 2004-05-26 19:13 Last Updated 2004-05-27 00:48 Completed 2004-05-27 00:48 Status Complete Review Resolution Test Suite Deficiency (TSD) Review Conclusion This PR represents an agreed test suite deficiency
Problem Reporting System Options:
- View Report 2382
- List All PRs
- Search Reports
- Email the System Administrator
- View the The Open Brand Interpretations Database User Manual
Contact the Certification Authority