| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
puts it before library's object files, making the whole constuct useless.
|
| |
|
|
|
|
| |
architectures. Linker defines end is synonym for _end.
|
|
|
|
| |
as static later.
|
| |
|
|
|
|
|
| |
SSP functions into FreeBSD libc. Use the same file name and location
for consistency with other projects.
|
|
|
|
| |
Suggested by: deischen
|
|
|
|
| |
export them.
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
can be used on any read socketopt).
-Clean up of sendmsg call and make it conformant when no syscall
is available.
|
|
|
|
|
| |
PR: 112704
Submitted by: kou@cozmixng.org
|
|
|
|
|
| |
world and it wreak havoc if libc collides with other versioned
libraries.
|
|
|
|
|
|
| |
PR: docs/78915
Submitted by: Marc Olzheim <marcolz@stack.nl>
MFC after: 1 week
|
|
|
|
| |
Submitted by: marius
|
|
|
|
| |
Pointed out by: deischen
|
|
|
|
|
|
|
| |
arch. It can be named differently depending on the arch (.mcount,
_mcount).
Submitted by: marius
|
|
|
|
|
|
|
|
|
|
| |
Warning, after symbol versioning is enabled, going back is not easy
(use WITHOUT_SYMVER at your own risk).
Change the default thread library to libthr.
There most likely still needs to be a version bump for at least the
thread libraries. If necessary, this will happen later.
|
|
|
|
|
|
| |
passed storage buffers rather than using static storage. Reimplement
ether_ntoa() and ether_aton() in terms of these functions. These variants
are thread-safe.
|
| |
|
|
|
|
| |
- Replace magic 14 with PIL_TICK.
|
|
|
|
| |
even if the programmer asks for zero padding.
|
|
|
|
| |
Reported by: Bruno Haible
|
|
|
|
|
| |
Approved by: keramida (mentor)
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
Not because I admit they are technically wrong and not because of bug
reports (I receive nothing). But because I surprisingly meets so
strong opposition and resistance so lost any desire to continue that.
Anyone who interested in POSIX can dig out what changes and how
through cvs diffs.
|
|
|
|
| |
Suggested by: Henrik Brix Andersen <henrik@brixandersen.dk>
|
|
|
|
|
| |
"so altering the argument shall change the environment."
into putenv description.
|
|
|
|
|
|
|
|
|
|
|
| |
(also IEEE Std 1003.1-2001)
The specs explicitly says that altering passed string
should change the environment, i.e. putenv() directly puts its arg
into environment (unlike setenv() which just copies it there).
It means that putenv() can't be implemented via setenv()
(like we have before) at all. Putenv() value lives (allows modifying)
up to the next putenv() or setenv() call.
|
|
|
|
|
|
|
|
|
| |
compatibility with the different environment conventions" (man page).
With the standards, we don't have them different anymore and
IEEE Std 1003.1-2001 says that
"The values that the environment variables may be assigned are not
restricted except that they are considered to end with a null byte"
|
|
|
|
|
|
|
|
|
| |
Issue 6 (also IEEE Std 1003.1-2001) in following areas:
args, return, errors.
Putenv still needs rewriting because specs explicitly says that
altering passed string later should change the environment (currently we
copy the string so can't provide that).
|
| |
|
|
|
|
| |
inheritance chain.
|
| |
|
|
|
|
| |
compatibility between versions (as we do for the public namespace).
|
|
|
|
|
|
|
|
| |
it is only relevant to receiving data from sockets, not to sending.
PR: 109667
Submitted by: Jari Kirma <kirma@cs.hut.fi>
Approved by: wollman
|
|
|
|
|
|
|
|
|
|
|
| |
1. CMSG_NXTHDR(mhdr, cmsg) is supposed to dereference cmsg and return
the next header in the chain. If cmsg is NULL it should return
the first header, behaving essentially like CMSG_FIRSTHDR().
2. inet6_rth_(space|init|add) should do basic checking on their input
to verify that the number of headers (segments) is
between 0 and 127 inclusive.
MFC-After: 1 month
|
| |
|
|
|
|
| |
don't program against our more restrictive behaviour.
|
|
|
|
|
|
|
|
|
|
| |
on int, but in fact it should operate on long.
- Introduce 'lvalue' variable, which is long.
- Fix _SC_XOPEN_SHM for 64bit archs.
- Fix _SC_PHYS_PAGES for 64bit archs.
Reported by: simokawa
- Use lvalue for pathconf(3), as it returns long.
- Cast value explicitly to long on return.
|
| |
|
|
|
|
| |
OK'ed by: pjd
|
|
|
|
|
| |
Submitted by: Ricardo Nabinger Sanchez
MFC after: 3 days
|
|
|
|
|
|
|
| |
the platform ABI and as such does not belong in FBSDprivate.
__libc_tls_* functions do not have to be visible to outside world
at all.
|
|
|
|
| |
Reminded by: ru
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
redeclared as static in res_debug.c.
Make __p_rcode_syms global and add it to Symbol map. The rest of
__p_??_syms are already global.
Choice of FBSD_1.0 version for these debug symbols seems strange and
should be revisited before symbol versioning is enabled for libc.so.7.
|
| |
|
|
|
|
|
|
| |
OpenSolaris. For more information please refer to:
http://blogs.sun.com/bonwick/entry/seek_hole_and_seek_data
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
unmount jail-friendly file systems from within a jail.
Precisely it grants PRIV_VFS_MOUNT, PRIV_VFS_UNMOUNT and
PRIV_VFS_MOUNT_NONUSER privileges for a jailed super-user.
It is turned off by default.
A jail-friendly file system is a file system which driver registers
itself with VFCF_JAIL flag via VFS_SET(9) API.
The lsvfs(1) command can be used to see which file systems are
jail-friendly ones.
There currently no jail-friendly file systems, ZFS will be the first one.
In the future we may consider marking file systems like nullfs as
jail-friendly.
Reviewed by: rwatson
|