| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
incorrectly when encountering `large' groups (many members and/or many
long member names). The reporter tracked this down to the glibc NSS
module compatibility code (nss_compat.c): it would prematurely record
that a NSS module was finished iterating through its database in some
cases.
Two aspects are corrected:
1. nss_compat.c recorded that a NSS module was finished iterating
whenever the module reported something other than SUCCESS. The
correct logic is to continue iteration when the module reports
either SUCCESS or RETURN. The __nss_compat_getgrent_r and
__nss_compat_getpwent_r routines are updated to reflect this.
2. An internal helper macro __nss_compat_result is used to map glibc
NSS status codes to BSD NSS status codes (e.g. NSS_STATUS_SUCCESS ->
NS_SUCCESS). It provided the obvious mapping.
When a NSS routine is called with a too-small buffer, the
convention in the BSD NSS code is to report RETURN. (This is used
to implement reentrant APIs such as getpwnam_r(3).) However, the
convention in glibc for this case is to set errno = ERANGE and
overload TRYAGAIN. __nss_compat_result is updated to handle this
case.
PR: bin/60287
Reported by: Lachlan O'Dea <odela01@ca.com>
|
|
|
|
|
|
| |
that mksnap_ffs(8) can be found using the current $PATH.
Reviewed by: mckusick
|
|
|
|
|
| |
tokens, so it does indeed need to be parenthesized. Duh. Sometimes
it can stare you right and the face and you still don't see it. Thanks, bde.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
1) Fix style issues in comments.
2) Properly namespaceify changes
3) Appropriate sectioning of changes
Not changed: parenthesis around macro rvalue. That would make the additions
inconsistent with the other entries there, merely a different style violation
rather than a clear and obvious improvement so I'm going to have to disagree
with the judges on that one. If someone wishes to adjust *all* the rvalues
to conform to fully parenthesized marco rule, that would be both consistent
and reasonable but that's beyond the scope of the changes I wish to make at
this time.
|
|
|
|
|
| |
I'll keep the same style regardless of the wisdom of it. :)
Clarified by: eivind
|
|
|
|
| |
Noticed by: Nate Lawson <nate@root.org>
|
|
|
|
| |
http://www.opengroup.org/onlinepubs/007904975/basedefs/regex.h.html)
|
|
|
|
| |
http://www.opengroup.org/onlinepubs/007904975/basedefs/fnmatch.h.html)
|
|
|
|
|
|
| |
as these ioctl's aren't MD. This also means they are installed in
/usr/include/dev/bktr now. Also provide compatability wrappers for
where these headers lived in 4.x.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
an int constant to a long constant. This change improves consistency
in the following two ways:
1. The first 8 arguments are always passed in registers on ia64, which
by virtue of the generated code implicitly widens ints to longs and
allows the use of an 32-bit integral type for 64-bit arguments.
Subsequent arguments are passed onto the memory stack, which does
not exhibit the same behaviour and consequently do not allow this.
In practice this means that variadic functions taking pointers
and given NULL (without cast) work as long as the NULL is passed
in one of the first 8 arguments. A SIGSEGV is more likely the
result if such would be done for stack-based arguments. This is
due to the fact that the upper 4 bytes remain undefined.
2. All 64-bit platforms that FreeBSD supports, with the obvious
exception of ia64, allow 32-bit integral types (specifically NULL)
when 64-bit pointers are expected in variadic functions by way of
how the compiler generates code. As such, code that works correctly
(whether rightfully so or not) on any platform other than ia64, may
fail on ia64.
To more easily allow tweaking of the definition of NULL, this commit
removes the 12 definitions in the various headers and puts it in a
new header that can be included whenever NULL is to be made visible.
This commit fixes GNOME, emacs, xemacs and a whole bunch of ports
that I don't particularly care about at this time...
|
|
|
|
|
| |
Submitted by: Paul Vixie <paul@vix.com> / ISC
MFC After: 1 week
|
|
|
|
| |
Submitted by: imura@ryu16.org
|
|
|
|
|
|
| |
getifmaddrs(), is added to retrieve current multicast group memberships.
Reviewed by: harti
|
|
|
|
| |
Reviewed by: davidxu
|
|
|
|
| |
characters '*', '?' and '['.
|
|
|
|
| |
Sorry folks.
|
|
|
|
|
|
|
|
|
|
|
| |
send strhash(3) off to sleep with the fishes. Nothing in our tree uses it.
It has no documentation. It is nonstandard and in spite of the filename
strhash.c and strhash.h, it lives in application namespace by providing
compulsory global symbols hash_create()/hash_destroy()/hash_search()/
hash_traverse()/hash_purge()/hash_stats() regardless of whether you
#include <strhash.h> or not. If it turns out that there is a huge
application for this after all, I can repocopy it somewhere safer and
we can revive it elsewhere. But please, not in libc!
|
|
|
|
| |
dependencies.
|
| |
|
|
|
|
| |
Reported by: bde
|
| |
|
|
|
|
|
|
| |
it will be removed on 23 Apr 2004.
Submitted by: terry
|
| |
|
|
|
|
| |
Obtained from: KAME
|
|
|
|
| |
Reviewed by: deischen
|
|
|
|
| |
pthread_rwlock_timedrwlock.
|
|
|
|
|
|
| |
pthread_mutex_timedlock().
Reviewed by: deischen
|
|
|
|
|
|
|
| |
to announce the demise of varargs support in GCC versions 3.3+ and to
direct users to stdarg.h instead.
Fall back to machine/varargs.h for older GCC versions.
|
| |
|
| |
|
|
|
|
| |
is run in non-compat mode (-j without -B).
|
|
|
|
| |
previous commit.
|
|
|
|
|
|
| |
with a couple of bits from usr.bin in a crunchgen'd binary.
Submitted by: Tim Kientzle <kientzle@acm.org>
|
|
|
|
|
|
| |
these definitions in the /rescue case.
Submitted by: Tim Kientzle <kientzle@acm.org>
|
|
|
|
|
|
|
| |
This simplifies the code path and makes the default path easy to override
in the /rescue case.
Submitted by: Tim Kientzle <kientzle@acm.org>
|
|
|
|
|
|
|
|
| |
Change execvp to be a wrapper around execvP. This is necessary for some
of the /rescue pieces. It may also be more generally applicable as well.
Submitted by: Tim Kientzle <kientzle@acm.org>
Approved by: Silence on arch@
|
| |
|
|
|
|
| |
Reviewed by: ache
|
| |
|
|
|
|
|
|
| |
tree local translator.
Requested by: jmallett
|
| |
|
|
|
|
|
|
| |
dependent. Instead provide one for GCC & Intel's GCC copy and one for lint.
Anyone using any other translator tool needs to look closely at how that tool
can handle alloca.
|
| |
|
| |
|
|
|
|
|
|
| |
installs the per-header symlinks.
Prodded by: many
|
|
|
|
| |
Reviewed by: phk
|
| |
|
| |
|