Problems in Standards
This section contains remarks on the text versions of Linux standards. All the issues reported here have been found during requirements formalization in the OLVER and LSB Infrastructure projects. We have defined the following life cycle for each potential issue.
- Initial problem detection during standard formalization.
- Problem formulation and registration in the internal problem tracking system.
- Periodical collective analysis of the validity and importance of registered problems.
- Reporting all approved issues to the appropriate standard bodies.
- Standard bodies decide whether to incorporate any changes in the standards or not.
Click on a problem number for detailed description. Click on a column header to change the sorting order.
No. | Type | Brief | Added on | Accepted | Status |
S0561 | Inconsistency | Positive tm_isdst field for %z processing in strftime() | reported | ||
S0807 | Inadequacy | LSB sysconf specification is not safe relative to POSIX update | |||
S0737 | Misprint | Misprint in the description of the interface strerror_r | Fixed in LSB 3.2 Update 2 | ||
S0687 | Inadequacy | Incorrect description of tgetflag return value | |||
S0686 | Inadequacy | Incorrect description of tgetnum return value | |||
S0685 | Inadequacy | Incorrect description of strsignal(int sig) if sig is an unknown signal number | Fixed in LSB 4.0 | ||
S0680 | Incompleteness | Incomplete set of MM_* constants for fmtmsg() at the LSB | Fixed in LSB 3.2 Update 2 | ||
S0544 | Crash | After compiling with lsbcc on IA64 or s390x architecture code with timer_create() call, timer_getoverrun(), timer_delete(), timer_settime(), timer_gettime() functions crashe | Fixed in LSB 3.2 | ||
S0524 | Inadequacy | The scanw() functions do not return OK upon successful completion | Fixed in LSB 4.0 | ||
S0102 | Inadequacy | setreuid/setregid may change saved set-user/group-ID | |||
S0620 | Inadequacy | Incorrect definition of the constant HUGE_VALL on ppc32, ppc64, s390, and s390x | Fixed in LSB 3.2 | ||
S0623 | Contradiction | Ambiguity of requirements to the poll() function in the LSB 3.2 | Fixed in LSB 3.2 Update 1 | ||
D0060 | Inadequacy | Implementation of the interface "g_cache_value_foreach" does not conform to the LSB 3.1 | Fixed in LSB 4.0 | ||
D0059 | Inadequacy | LSB incorrectly describes usage of the NULL value of the "group_name" parameter of the "Key-value file parser" interfaces | Fixed in LSB 4.0 | ||
S0504 | Inaccuracy | Function sched_setscheduler() always returns 0, but not the former scheduling policy | Fixed in LSB 3.1 Update 1 | ||
S0498 | Crash | sigandset, sigorset and sigisemptyset functions crash if one of the parameters is NULL | Fixed in LSB 3.1 Update 1 | ||
S0311 | Inaccuracy | inchnstr() family of functions writes n+1 symbols in the supplied array | |||
S0525 | Contradiction | getgrouplist() updates ngroups incorrectly if there was not sufficient room to copy all the supplementary group identifiers | Fixed in LSB 3.1 Update 1 | ||
S0177 | Contradiction | getgrouplist() returns 1, if user does not refer to a valid user on the system | Fixed in LSB 3.1 Update 1 | ||
S0319 | Contradiction | The ripoffline() call above five calls limit returns -1 | Fixed in LSB 4.0 | ||
S0313 | Inadequacy | mvcur() of ncurses does not follow the SuSv2 specification | Fixed in LSB 4.0 | ||
S0357 | Contradiction | Enabling or disabling meta characters does not influence the behaviour of keyname() function | |||
S0534 | Inaccuracy | Improper references to standards for some of Math’s functions. | Fixed in LSB 3.2 | ||
S0275 | Misprint | Misprint in the description of the |
Fixed in LSB 3.1 Update 1 | ||
S0447 | Misprint | Misprint in description of the |
Fixed in LSB 3.1 Update 1 | ||
S0409 | Misprint | Misprint in the description of the |
Fixed in LSB 3.1 Update 1 | ||
S0407 | Inaccuracy | The |
Fixed in LSB 3.1 Update 1 | ||
S0408 | Misprint | Misprint in the description of the |
Fixed in LSB 3.1 Update 1 | ||
S0384 | Inaccuracy | Different types of the ‘protocol’ parameter in |
|||
S0264 | Inaccuracy | Incomplete description of the error condition for the |
|||
S0269 | Inaccuracy | No errors are defined in the description of the |
|||
S0267 | Inaccuracy | Z_BLOCK is not defined anywhere. | Fixed in LSB 3.1 Update 1 | ||
S0369 | Inaccuracy | The xdr_destroy() is absent in LSB 3.1 | Fixed in LSB 4.0 | ||
S0355 | Inaccuracy | Functions from XDR are not defined in any header described in LSB | Fixed in LSB 3.2 | ||
S0449 | Inaccuracy | Possible misprint in the declaration of wchar_t. | Fixed in LSB 3.2 | ||
S0293 | Contradiction | The *inchstr, *inchnstr and *instr functions do not return OK. | Fixed in LSB 4.0 | ||
S0359 | Contradiction | atexit() in the LSB Software Development Kit (SDK). | Fixed in LSB 3.1 Update 1 | ||
S0207 | Inaccuracy | Implementation of the basename() function in libc.so does not satisfy LSB 3.1. | Fixed in LSB 3.1 Update 1 | ||
S0398 | Contradiction | Inconsistency in constant definitions for mutex types in LSB 3.1 и в glibc-2.3.4. | Fixed in LSB 3.1 Update 1 | ||
S0162 | Inaccuracy | The RUSAGE_BOTH is not defined anywhere. | Fixed in LSB 3.1 Update 1 | ||
S0270 | Misprint | Misprint in the description of the |
Fixed in LSB 3.1 Update 1 | ||
S0277 | Misprint | Misprint in the description of the |
Fixed in LSB 3.1 Update 1 | ||
S0261 | Contradiction | Contradiction in the description of |
Fixed in LSB 3.1 Update 1 | ||
S0268 | Misprint | Misprint in the descriptions of |
Fixed in LSB 3.2 | ||
S0245 | Contradiction | Wrong name of macro in the descriptions of |
Fixed in LSB 3.2 | ||
S0295 | Misprint | Misprint in the description of the |
Fixed in LSB 3.2 | ||
S0148 | Inaccuracy | Lack of details in requirements to |
Fixed in LSB 3.2 | ||
S0263 | Misprint | Misprint in the description of |
Fixed in LSB 3.2 | ||
S0205 | Contradiction | Declaration of |
Fixed in LSB 3.2 | ||
S0204 | Contradiction | LSB Software Development Kit (SDK) does not satisfy the POSIX requirements | Fixed in LSB 3.2 | ||
S0252 | Inaccuracy | Standard refers to |
Fixed in LSB 3.2 | ||
S0231 | Inaccuracy | Remark to descriptions of |
Fixed in LSB 3.2 | ||
S0260 | Misprint | Misprint in the description of the |
Fixed in LSB 3.2 | ||
S0262 | Inaccuracy | The flag DEF_WBITS is not defined anywhere | Fixed in LSB 3.2 | ||
S0153 | Inaccuracy | The flags, that are defined in glob.h, are not described anywhere. | |||
S0146 | Misprint | Misprint in the description of the |
Fixed in LSB 3.2 | ||
S0117 | Incompleteness | The flag __WRDE_FLAGS is not described | Fixed in LSB 3.2 | ||
S0273 | Misprint | Misprint in description of the |
Fixed in LSB 3.2 | ||
S0289 | Misprint | Variables are declared as functions in curses.h in LSB 3.1 | Fixed in LSB 3.2 | ||
S0210 | Inaccuracy | Possibly incomplete list of errors in the description of flock() function | Fixed in LSB 3.2 | ||
S0009 | Inaccuracy | Lack of details in the requirements for __rawmemchr() function. | Fixed in LSB 4.0 | ||
S0136 | Inaccuracy | Names, which should be defined according to SUSv3, are not defined in LSB 3.1 | Fixed in LSB 3.2 | ||
S0116 | Inaccuracy | Inconsistency between types of fields ‘we_wordc’ and ‘we_offs’ in type ‘wordexp_t’ in |
Fixed in LSB 3.2 | ||
S0022 | Inaccuracy | Standard defines the first parameter of strnlen() function as 'string', but such definition reduces the applicability of the function. It looks valid to define the first parameter as 'array of char'. | Fixed in LSB 3.2 | ||
S0010 | Inaccuracy | Lack of details in the requirements for memmem() function. | Fixed in LSB 4.0 | ||
S0019 | Inaccuracy | No possible errors are defined for wcsdup() | Fixed in LSB 3.2 | ||
S0008 | Inaccuracy | Lack of details in requirements to |
Fixed in LSB 4.0 | ||
S0007 | Inaccuracy | Type 'ptr_t' that is used in synopsis of functions |
Fixed in LSB 3.2 | ||
S0026 | Contradiction | Contradiction between macro definitions of terminal speed in different sections of LSB 3.1 | Fixed in LSB 3.2 | ||
S0158 | Inaccuracy | Standard refers to |
Fixed in LSB 3.2 | ||
S0011 | Misprint | Misprint in the synopsis of the |
Fixed in LSB 3.2 |
»