LSB Core test suite results for glibc-2.17

[Andrey Ponomarenko <aponomarenko at rosalab dot ru>]

Hello,

I've run the official LSB Core test suite against the latest stable 
release of glibc 2.17 and also written an article [1] about how to do it 
for the local install tree of the library. The test suite covers 1193 
glibc functions (see LSB 12.3. "Interfaces for libc") and checks them 
for conformance with LSB, SUSv2, SUSv3, SUSv4, LFS and SVID.4 standards. 
The test suite is a part of the LSB certification tests for Linux 
distributions.

Tests have found 47 known problems (described in detail here [2]) and 
two new ones [3]:

1) util_dl_scenario [dlsym.03] Requirement failed: {dlsym.03} correct 
symbol not found

The failed test case:

#include <dlfcn.h>
int main()
{
    void* h = dlopen(NULL, RTLD_NOW | RTLD_GLOBAL);
    void* r = dlsym(h, "authnone_create");

    return 0;
}

The issue is that dlsym cannot find a symbol "authnone_create" in the 
libc. There is only "authnone_create@GLIBC_2.0" symbol. The problem is 
not reproducible on glibc versions older than 2.14.

2) util_crypt_scenario [crypt.09] Requirement failed: Unexpected error 
code returned: [EINVAL] code 0x16

The failed test case:

#include <unistd.h>
#include <errno.h>
int main()
{
    int e1 = 0;
    int e2 = 0;
    int r = 0;

    e1 = errno;
    r = crypt("Key", "a");
    e2 = errno;

    return 0;
}

The issue is that the new implementation of the crypt function in glibc 
2.17 requires the salt parameter to be longer than two characters and 
returned an error code EINVAL (22). This error code is not described in 
the standard for this function [4].

Please tell me your thoughts on this.

[1] http://sourceware.org/glibc/wiki/Testing/LSB_Core
[2] 
http://upstream-tracker.org/olver_reports/glibc-2.17/Fedora_18/summary.htm#fails
[3] 
http://upstream-tracker.org/olver_reports/glibc-2.17/Fedora_18/summary.htm#New
[4] http://pubs.opengroup.org/onlinepubs/000095399/functions/crypt.html

--
Andrey Ponomarenko, ROSA Lab.