| Commit message (Expand) | Author | Files | Lines |
|---|
| 2013-12-06 | add posix_close, accepted for inclusion in the next issue of POSIX•••this is purely a wrapper for close since Linux does not support EINTR
semantics for the close syscall.
| Rich Felker | 2 | -0/+9 |
| 2013-12-04 | remove dependency of version.h on .git/* to avoid errors•••the wildcard function in GNU make includes dangling symlinks; if any
exist under the .git directory, they would get added as dependencies,
causing make to exit with an error due to lacking a rule to build the
missing file.
as far as I can tell, git operations which should force version.h to
be rebuilt must all touch the mtime of the top-level .git directory.
| Rich Felker | 1 | -1/+1 |
| 2013-12-04 | move struct ucred under _GNU_SOURCE in sys/socket.h for clean posix namespace | Szabolcs Nagy | 1 | -0/+2 |
| 2013-12-04 | fix SHUT_WR typo in sys/socket.h and duplicate definitions of SHUT_* | Szabolcs Nagy | 1 | -5/+1 |
| 2013-12-04 | fix res_mkquery and res_send prototypes in resolv.h•••historically these functions appeared in BSD 4.3 without prototypes,
then in the bind project prototypes were added to resolv.h, but those
were incompatible with the definitions of the implementation.
the bind resolv.h became the defacto api most systems use now, but the
old internal definitions found their way into the linux manuals and thus
into musl.
| Szabolcs Nagy | 1 | -4/+2 |
| 2013-12-03 | remove duplicate definition of _PATH_LASTLOG in paths.h | Rich Felker | 1 | -1/+0 |
| 2013-12-03 | fix mv usage in install.sh to avoid bogus interactive prompting | Rich Felker | 1 | -1/+1 |
| 2013-12-02 | workaround clang deficiency affecting thread pointer access on powerpc•••based on patch by Richard Pennington, who initially reported the
issue.
| Rich Felker | 1 | -1/+6 |
| 2013-12-02 | implement FNM_LEADING_DIR extension flag in fnmatch•••previously this flag was defined and accepted as a no-op, possibly
breaking some software that uses it. given the choice to remove the
definition and possibly break applications that were already working,
or simply implement the feature, the latter turned out to be easy
enough to make the decision easy.
in the case where the FNM_PATHNAME flag is also set, this
implementation is clean and essentially optimal. otherwise, it's an
inefficient "brute force" implementation. at some point, when cleaning
up and refactoring this code, I may add a more direct code path for
handling FNM_LEADING_DIR in the non-FNM_PATHNAME case, but at this
point my main interest is avoiding introducing new bugs in the code
that implements the standard fnmatch features specified by POSIX.
| Rich Felker | 1 | -2/+9 |
| 2013-12-02 | remove now-unnecessary features.h inclusion from fnmatch.h | Rich Felker | 1 | -2/+0 |
| 2013-12-02 | expose FNM_* extensions in fnmatch.h without _GNU_SOURCE•••at least a couple of these are used on BSD too, and the FNM_*
namespace is reserved in fnmatch.h anyway.
| Rich Felker | 1 | -3/+0 |
| 2013-12-01 | fix typos in INSTALL file | Rich Felker | 1 | -2/+2 |
| 2013-12-01 | add infrastructure to record and report the version of libc.so•••this is still experimental and subject to change. for git checkouts,
an attempt is made to record the exact revision to aid in bug reports
and debugging. no version information is recorded in the static libc.a
or binaries it's linked into.
| Rich Felker | 5 | -3/+39 |
| 2013-12-01 | fix fnmatch corner cases related to escaping•••the FNM_PATHNAME logic for advancing by /-delimited components was
incorrect when the / character was escaped (i.e. \/), and a final \ at
the end of pattern was not handled correctly.
| Rich Felker | 1 | -4/+4 |
| 2013-12-01 | fix the end of string matching in fnmatch with FNM_PATHNAME•••a '/' in the pattern could be incorrectly matched against the
terminating null byte in the string causing arbitrarily long
sequence of out-of-bounds access in fnmatch("/","",FNM_PATHNAME)
| Szabolcs Nagy | 1 | -2/+2 |
| 2013-11-30 | support mix of IPv4 and v6 nameservers in resolv.conf•••a v6 socket will only be used if there is at least one v6 nameserver
address. if the kernel lacks v6 support, the code will fall back to
using a v4 socket and requests to v6 servers will silently fail. when
using a v6 socket, v4 addresses are converted to v4-mapped form and
setsockopt is used to ensure that the v6 socket can accept both v4 and
v6 traffic (this is on-by-default on Linux but the default is
configurable in /proc and so it needs to be set explicitly on the
socket level). this scheme avoids increasing resource usage during
lookups and allows the existing network io loop to be used without
modification.
previously, nameservers whose address family did not match the address
family of the first-listed nameserver were simply ignored. prior to
recent __ipparse fixes, they were not ignored but erroneously parsed.
| Rich Felker | 1 | -5/+31 |
| 2013-11-29 | increase TTY_NAME_MAX limit to 32•••the old value of 20 was reported by Laurent Bercot as being
insufficient for a reasonable real-world usage case. actual problem
was the internal buffer used by ttyname(), but the implementation of
ttyname uses TTY_NAME_MAX, and for consistency it's best to increase
both. the new value is aligned with glibc.
| Rich Felker | 1 | -1/+1 |
| 2013-11-27 | reject invalid address families in getaddrinfo•••subsequent code assumes the address family requested is either
unspecified or one of IPv4/IPv6, and could malfunction if this
constraint is not met, so other address families should be explicitly
rejected.
| Rich Felker | 1 | -0/+3 |
| 2013-11-26 | adjust fallback INFINITY definition for FLT_EVAL_METHOD==2 case•••on archs with excess precision, the floating point constant 1e40f may
be evaluated such that it does not actually produce an infinity.
1e5000f is sufficiently large to produce an infinity for all supported
floating point formats. note that this definition of INFINITY is only
used for old or non-GNUC compilers anyway; despite being a portable,
conforming definition, it leads to erroneous warnings on many
compilers and thus using the builtin is preferred.
| Rich Felker | 1 | -1/+1 |
| 2013-11-26 | fix off-by-one length failure in strftime/wcsftime and improve error behavior•••these functions were spuriously failing in the case where the buffer
size was exactly the number of bytes/characters to be written,
including null termination. since these functions do not have defined
error conditions other than buffer size, a reasonable application may
fail to check the return value when the format string and buffer size
are known to be valid; such an application could then attempt to use a
non-terminated buffer.
in addition to fixing the bug, I have changed the error handling
behavior so that these functions always null-terminate the output
except in the case where the buffer size is zero, and so that they
always write as many characters as possible before failing, rather
than dropping whole fields that do not fit. this actually simplifies
the logic somewhat anyway.
| Rich Felker | 2 | -12/+16 |
| 2013-11-25 | remove duplicate includes from dynlink.c, strfmon.c and getaddrinfo.c | Szabolcs Nagy | 3 | -7/+0 |
| 2013-11-24 | restore type of NULL to void * except when used in C++ programs•••unfortunately this eliminates the ability of the compiler to diagnose
some dangerous/incorrect usage, but POSIX requires (as an extension to
the C language, i.e. CX shaded) that NULL have type void *. plain C
allows it to be defined as any null pointer constant.
the definition 0L is preserved for C++ rather than reverting to plain
0 to avoid dangerous behavior in non-conforming programs which use
NULL as a variadic sentinel. (it's impossible to use (void *)0 for C++
since C++ lacks the proper implicit pointer conversions, and other
popular alternatives like the GCC __null extension seem non-conforming
to the standard's requirements.)
| Rich Felker | 8 | -0/+33 |
| 2013-11-24 | shadow: Implement fgetspent | Michael Forney | 1 | -1/+10 |
| 2013-11-24 | shadow: Move spent parsing to internal function | Michael Forney | 2 | -31/+40 |
| 2013-11-24 | Fix dn_comp prototype and add stub•••This function is used by ping6 from iputils.
| Michael Forney | 2 | -1/+10 |
| 2013-11-24 | shadow: Implement putspent | Michael Forney | 2 | -5/+13 |
| 2013-11-24 | math: clean up __rem_pio2•••- remove the HAVE_EFFICIENT_IRINT case: fn is an exact integer, so
it can be converted to int32_t a bit more efficiently than with a
cast (the rounding mode change can be avoided), but musl does not
support this case on any arch.
- __rem_pio2: use double_t where possible
- __rem_pio2f: use less assignments to avoid stores on i386
- use unsigned int bit manipulation (and union instead of macros)
- use hexfloat literals instead of named constants
| Szabolcs Nagy | 3 | -71/+53 |
| 2013-11-24 | use 0 instead of NULL in headers where NULL is not defined•••some macros in sys/mtio.h and syslog.h used NULL without defining it
| Szabolcs Nagy | 2 | -3/+3 |
| 2013-11-23 | add O_TMPFILE flag, new in linux 3.11•••definition in linux:
#define O_TMPFILE (__O_TMPFILE | O_DIRECTORY)
where __O_TMPFILE and O_DIRECTORY are arch specific
| Szabolcs Nagy | 6 | -0/+6 |
| 2013-11-23 | add TCP_NOTSENT_LOWAT tcp socket option, new in linux v3.12 | Szabolcs Nagy | 1 | -0/+1 |
| 2013-11-23 | add linux tcp state enums | Timo Teräs | 1 | -0/+12 |
| 2013-11-23 | add multicast structures from RFC 3678 to netinet/in.h•••and use _GNU_SOURCE || _BSD_SOURCE guards for all of the RFC 3678
namespace polluting things like glibc/uclibc does.
| Timo Teräs | 1 | -1/+42 |
| 2013-11-23 | Fix dn_expand pointer following | Michael Forney | 1 | -1/+1 |
| 2013-11-23 | putgrent: Add missing newline | Michael Forney | 1 | -0/+1 |
| 2013-11-23 | putgrent: Stop writing output on first failure•••This way, if an fprintf fails, we get an incomplete group entry rather
than a corrupted one.
| Michael Forney | 1 | -2/+3 |
| 2013-11-23 | strcmp: Remove unnecessary check for *r•••If *l == *r && *l, then by transitivity, *r.
| Michael Forney | 1 | -1/+1 |
| 2013-11-23 | timeradd/timersub: cast result to void to get rid of warnings•••previously:
timersub(&now, t, &diff);
warning: value computed is not used [-Wunused-value]
| rofl0r | 1 | -2/+2 |
| 2013-11-22 | fix and refactor child reaping logic in wordexp•••loop condition was incorrect and confusing and caused an infinite loop
when (broken) applications reaped the pid from a signal handler or
another thread before wordexp's call to waitpid could do so.
| Rich Felker | 1 | -6/+16 |
| 2013-11-22 | fix fd leak and case where fd 1 is already closed in wordexp | Rich Felker | 1 | -4/+4 |
| 2013-11-22 | fix resource exhaustion and zero-word cases in wordexp•••when WRDE_NOSPACE is returned, the we_wordv and we_wordc members must
be valid, because the interface contract allows them to return partial
results.
in the case of zero results (due either to resource exhaustion or a
zero-word input) the we_wordv array still should contain a terminating
null pointer and the initial we_offs null pointers. this is impossible
on resource exhaustion, so a correct application must presumably check
for a null pointer in we_wordv; POSIX however seems to ignore the
issue. the previous code may have crashed under this situation.
| Rich Felker | 1 | -8/+18 |
| 2013-11-22 | improve robustness of wordexp and fix handling of 0-word case•••avoid using exit status to determine if a shell error occurred, since
broken programs may install SIGCHLD handlers which reap all zombies,
including ones that don't belong to them. using clone and __WCLONE
does not seem to work for avoiding this problem since exec resets the
exit signal to SIGCHLD.
instead, the new code uses a dummy word at the beginning of the
shell's output, which is ignored, to determine whether the command was
executed successfully. this also fixes a corner case where a word
string containing zero words was interpreted as a single zero-length
word rather than no words at all. POSIX does not seem to require this
case to be supported anyway, though.
in addition, the new code uses the correct retry idiom for waitpid to
ensure that spurious STOP/CONT signals in the child and/or EINTR in
the parent do not prevent successful wait for the child, and blocks
signals in the child.
| Rich Felker | 1 | -11/+16 |
| 2013-11-21 | add legacy getloadavg api | Szabolcs Nagy | 2 | -0/+19 |
| 2013-11-20 | fix fd leak (missing close-on-exec) in getifaddrs | Rich Felker | 1 | -1/+1 |
| 2013-11-21 | math: add (obsolete) bsd drem and finite functions | Szabolcs Nagy | 5 | -0/+26 |
| 2013-11-21 | math: lgamma cleanup (simpler sin(pi*x) for the negative case)•••* simplify sin_pi(x) (don't care about inexact here, the result is
inexact anyway, and x is not so small to underflow)
* in lgammal add the previously removed special case for x==1 and
x==2 (to fix the sign of zero in downward rounding mode)
* only define lgammal on supported long double platforms
* change tgamma so the generated code is a bit smaller
| Szabolcs Nagy | 4 | -202/+110 |
| 2013-11-20 | fix the nominal type of LDBL_* limits on archs with ld64•••previously these macros wrongly had type double rather than long
double. I see no way an application could detect the error in C99, but
C11's _Generic can trivially detect it.
at the same time, even though these archs do not have excess
precision, the number of decimal places used to represent these
constants has been increased to 21 to be consistent with the decimal
representations used for the DBL_* macros.
| Rich Felker | 4 | -16/+16 |
| 2013-11-20 | write floating point limit constants to 21 significant decimal places•••this is enough to produce the correct value even if the constant is
interpreted as 80-bit extended precision, which matters on archs with
excess precision (FLT_EVAL_METHOD==2) under at least some
interpretations of the C standard. the shorter representations, while
correct if converted to the nominal precision at translation time,
could produce an incorrect value at extended precision, yielding
results such as (double)DBL_MAX != DBL_MAX.
| Rich Felker | 2 | -10/+10 |
| 2013-11-11 | iswspace: fix handling of 0 | rofl0r | 1 | -2/+1 |
| 2013-11-09 | fix harmless inconsistency in semtimedop•••this should not matter since the reality is that either all the sysv
sem syscalls are individual syscalls, or all of them are multiplexed
on the SYS_ipc syscall (depending on arch). but best to be consistent
anyway.
| Rich Felker | 1 | -1/+1 |
| 2013-11-09 | implement semtimedop•••this is a Linux-specific extension to the sysv semaphore api.
| Rich Felker | 2 | -0/+14 |
