| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
getobjformat.3: "takes precedence over" is not an envrionment variable.
PR: 75545
Submitted by: n-kogane@syd.odn.ne.jp
MFC after: 3 days
|
|
|
|
| |
Submitted by: ru
|
|
|
|
|
|
|
| |
only be called once after failure or completion of an AIO request. Bump doc
date while I'm here.
Noticed by: Samy Al Bahra
|
|
|
|
| |
Noticed by: Samy Al Bahra
|
|
|
|
| |
Obtained from: OpenBSD
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
PR: docs/103666
Submitted by: vd
Approved by: maxim
|
|
|
|
| |
No functional changes.
|
|
|
|
| |
v1.21 which just do that.
|
|
|
|
|
|
| |
don't be greedy on the GNU "::" extension when arg separated by whitespace
and POSIX_CORRECTLY is set. From POSIX point of view this is unclear
situation, so minimal assumption looks right.
|
|
|
|
| |
in another. GCC4 does not like that.
|
| |
|
|
|
|
| |
add rtprio_thread.
|
|
|
|
|
| |
Submitted by: pgollucci@p6m7g8.com, Mark Costlow
MFC after: 3 weeks
|
| |
|
| |
|
|
|
|
| |
Reviewed by: andre
|
| |
|
|
|
|
|
|
|
|
| |
Coverity CID 2292: Plug memory leak.
Coverity CID 2291: Move function call before allocating storage to prevent
memory leak on error.
MFC after: 1 month
|
|
|
|
|
|
| |
Coverity CID 2293: Fix memory leak.
MFC after: 1 month
|
|
|
|
|
|
| |
Coverity CID 779 + 780: Avoid NULL pointer dereference.
MFC after: 1 month
|
|
|
|
|
|
|
| |
Coverity CID 2284: Fix multiple memory leaks.
Coverity CID 710: Remove unreachable code.
MFC after: 1 month
|
|
|
|
|
|
| |
Coverity CID 2276: Don't leak memory on error.
MFC after: 1 month
|
|
|
|
|
|
| |
Coverity CID 2275: Avoid memory leak on error.
MFC after: 1 month
|
|
|
|
|
|
|
| |
Fix unpaired sigblock which possibly leaves the process with all
signals blocked.
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
Coverity CID 3651: Don't leak ifaddrs on getaddrinfo failure.
Coverity CID 2283: Don't leak sys_auth on error.
MFC after: 1 month
|
|
|
|
|
|
|
| |
structures, in order to avoid the possibility of attempted recursive
lock acquisition for chunks_mtx.
Reported by: Slawa Olhovchenkov <slw@zxy.spb.ru>
|
|
|
|
| |
Obtained from: OpenBSD
|
|
|
|
|
|
| |
we can find another way to issue an #error, but using a preprocessed
assembler for that purpose and clobbering libc.a with an empty .o
just for the sake of #error reporting is way too much of a burden.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
that the documented TCB is at the tail of the extended TCB. In other
words, the base of the TCB has a negative offset from the TLS.
|
|
|
|
| |
assembly.
|
|
|
|
| |
assembly.
|
|
|
|
|
|
| |
PR: docs/102353
Submitted by: phk
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
| |
there's no need to to anything in the hton* functions, beside returning
the parameter.
Spotted out by: Oleksandr Tymoshenko <gonzo@freebsd.org>
|
|
|
|
| |
PR: 24125
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
first sentence back to the way it was. Add a second sentence that
explains the case when strcmp is called.
|
|
|
|
|
|
|
|
|
|
|
| |
(size_t)(num * size) == 0
but both num and size are nonzero.
Reported by: Ilja van Sprundel
Approved by: jasone
Security: Integer overflow; calloc was allocating 1 byte in
response to a request for a multiple of 2^32 (or 2^64)
bytes instead of returning NULL.
|
|
|
|
| |
See also: PR ia64/91846
|
|
|
|
|
|
| |
PR: docs/101314
Submitted by: Vasil Dimov
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The symptom is that syslog() fails to log anything but the "ident"
string if LOG_PERROR is specified to openlog(3) and the extensible
printf is in action.
For unclear, likely quaint historical reasons, syslog uses fwopen()
on a stack buffer, rather than using the more straightforward
and faster snprintf().
Along the way, fflush(3) is called, and since the callback writer
function returns zero instead of the length "written", __SERR
naturally gets set on the filedescriptor.
The extensible printf, in difference from the normal printf refuses
to output anything to an __SERR marked filedescriptor, and thus
the actual syslog message is supressed.
MFC: after 2 weeks
|
|
|
|
|
|
|
|
|
| |
old resolver opened just one socket, BIND9's resolver may
open more than one sockets. And, BIND9's resolver doesn't
close the socket on timeout. So, we need this check.
Reported by: freebsd-cvs-src__at__oldach.net (Helge Oldach), bz
Hinted by: rwatson
|
| |
|