| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
PR: 136383
Submitted by: Ulrich Spoerlein - uqs at spoerlein dot net
Approved by: re (kib)
MFC after: 3 weeks
|
|
|
|
|
|
|
|
|
| |
display '+' on them. Taken from kern/125613, with cosmetic
changes.
PR: kern/125613
Submitted by: Jaakko Heinonen <jh at saunalahti dot fi>
Approved by: re (kib)
|
|
|
|
| |
Approved by: ed (mentor) (implicit)
|
|
|
|
|
|
| |
Also document various properties of special builtins that we implement.
Approved by: ed (mentor) (implicit)
|
|
|
|
|
| |
Submitted by: Eygene Ryabinkin
Approved by: ed (mentor) (implicit)
|
|
|
|
| |
Approved by: ed (mentor) (implicit)
|
|
|
|
| |
so that we need to do segmentation.
|
|
|
|
| |
Approved by: ed (mentor)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
any open file descriptors >= 'lowfd'. It is largely identical to the same
function on other operating systems such as Solaris, DFly, NetBSD, and
OpenBSD. One difference from other *BSD is that this closefrom() does not
fail with any errors. In practice, while the manpages for NetBSD and
OpenBSD claim that they return EINTR, they ignore internal errors from
close() and never return EINTR. DFly does return EINTR, but for the common
use case (closing fd's prior to execve()), the caller really wants all
fd's closed and returning EINTR just forces callers to call closefrom() in
a loop until it stops failing.
Note that this implementation of closefrom(2) does not make any effort to
resolve userland races with open(2) in other threads. As such, it is not
multithread safe.
Submitted by: rwatson (initial version)
Reviewed by: rwatson
MFC after: 2 weeks
|
|
|
|
| |
Approved by: ed (mentor)
|
| |
|
|
|
|
|
|
| |
Strange, isn't it?
Pointed out by: bde
|
| |
|
|
|
|
|
|
| |
same fcntl lock.
Approved by: dfr (mentor)
|
| |
|
| |
|
|
|
|
| |
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
| |
format strings.
PR: bin/127514
Submitted by: edwin@
MFC after: 1 week
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
because it means getdelim() returns -1 for both error and EOF, and
never returns 0. However, this is what the original GNU implementation
does, and POSIX inherited the bug.
Reported by: marcus@
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Tested by: make universe
Tested by: ports exp build (done by pav)
Reviewed by: ru
Reviewed by: silence on arch
Approved by: ed (mentor)
|
|
|
|
|
|
|
|
|
| |
colliding upper case letters as the lower case letter with a '_' in
front.
MFC after: 3 days
Discussed with: ed
Spotted by: Michael David Crawford <mdc at prgmr.com>
|
|
|
|
| |
non-blocking, EINPROGRESS is an acceptable result from connect().
|
| |
|
|
|
|
|
| |
Currently it only has tests for a few sign issues with integer
formats, including PR 131880.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The function pow() in libmp(3) clashes with pow(3) in libm. We could
rename this single function, but we can just take the same approach as
the Solaris folks did, which is to prefix all function names with mp_.
libmp(3) isn't really popular nowadays. I suspect not a single
application in ports depends on it. There's still a chance, so I've
increased the SHLIB_MAJOR and __FreeBSD_version.
Reviewed by: deischen, rdivacky
|
|
|
|
|
|
|
|
|
| |
It is only really necessary for open(2)'s third argument, which is optional and
obtained through stdarg(3). open(2)'s third argument is 32bit and we pass 64
bits. On little endian it works, because we take lower 32 bits, but on big
endian platforms we take upper 32 bits, so we end up with 0.
Reported by: Milan Čermák <Milan.Cermak@Sun.COM>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
allocated in a fork(2)-inheritable way at the beginning or end of an
accept(2) system call. This test creates a test thread and blocks it
in accept(2), then forks a child process which tests to see if the
next available file descriptor is defined or not (EBADF vs EINVAL for
ftruncate(2)).
This detects a regression introduced during the network stack locking
work, in which a very narrow race during which fork(2) from one
thread during accept(2) in a second thread lead to an extra inherited
file descriptor turned into a very wide race ensuring that a
descriptor was leaked into the child even though it hadn't been
returned.
PR: kern/130348
|
| |
|
|
|
|
| |
versions in libm, not the gcc builtins.
|
|
|
|
| |
Submitted by: Milan Cermak <Milan.Cermak@Sun.COM>
|
|
|
|
|
|
|
|
| |
The jot(1) regression tests directory contained two tests named `wx' and
`wX', which doesn't work on case insensitive filesystems. Rename `wX' to
`wX1'.
MFC after: 1 month
|
| |
|
|
|
|
| |
Approved by: rwatson (mentor)
|
|
|
|
| |
Found by: trasz
|
|
|
|
| |
suddenly started to work.
|
| |
|
| |
|
|
|
|
|
|
|
| |
- Use -- when needed so Linux getopt(3) won't get confused.
- Follow POSIX more closely.
Submitted by: Szabolcs Szakacsits <szaka@ntfs-3g.org>
|
|
|
|
| |
Automatically detect file system type.
|
| |
|