| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
| |
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D2152
|
|
|
|
|
|
|
| |
are ignored.
MFC after: 1 month
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
|
|
| |
Both .weak and .alias assembler directives only work when assembling
the file which defines the symbol.
Reported and tested by: andrew
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
Per Austin group issue #884, sh should not import IFS from the environment
but always set it to $' \t\n'. For wordexp(), however, it is documented and
useful for it to use IFS from the environment.
Since sh currently imports IFS from the environment, this change has no
functional effect.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Note that to cancel blocked kevent(2) call, changelist must be empty,
since we cannot cancel a call which already made changes to the
process state. And in reverse, call which only makes changes to the
kqueue state, without waiting for an event, is not cancellable. This
makes a natural usage model to migrate kqueue loop to support
cancellation, where existing single kevent(2) call must be split into
two: first uncancellable update of kqueue, then cancellable wait for
events.
Note that this is ABI-incompatible change, but it is believed that
there is no cancel-safe code that relies on kevent(2) not being a
cancellation point. Option to preserve the ABI would be to keep
kevent(2) as is, but add new call with flags to specify cancellation
behaviour, which only value seems to add complications.
Suggested and reviewed by: jilles
Sponsored by: The FreeBSD Foundation
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
https://svnweb.freebsd.org/base?view=revision&revision=169622
This fixes
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=197783
Thanks to Jukka Ukkonen for reporting the bug and providing a fix.
MFC after: 3 days
|
|
|
|
|
| |
The kern.proc.umask.<pid> sysctl allows querying the umask without
temporarily modifying it.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
only adds support for kernel-toolchain, however it is expected further
changes to add kernel and userland support will be committed as they are
reviewed.
As our copy of binutils is too old the devel/aarch64-binutils port needs
to be installed to pull in a linker.
To build either TARGET needs to be set to arm64, or TARGET_ARCH set to
aarch64. The latter is set so uname -p will return aarch64 as existing
third party software expects this.
Differential Revision: https://reviews.freebsd.org/D2005
Relnotes: Yes
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
| |
support it in nlist(3).
Reviewed by: emaste
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
|
|
|
| |
CID: 1016705
CID: 1016706
CID: 1016707
Differential Revision: https://reviews.freebsd.org/D2023
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
| |
This should also save and restore non-volatile Altivec registers, but that
needs to wait on solving two problems:
1. Adding the nonvolatile vector registers means we need 5 more than _JBLEN
entries in jmp_buf on 32-bit targets (64-bit is OK).
2. Need to figure out how to determine if saving/restoring vector regs
is supported on the current CPU from userland.
MFC after: 1 month
|
| |
|
|
|
|
| |
Submitted by: Justin Cormack
|
|
|
|
| |
CID: 1018731
|
|
|
|
|
| |
Basically spaces vs. tabs.
No functional change.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Implement a small enhancement to the original qsort implementation:
If the data is 32 bit aligned we can side-step the long type
version and use int instead.
The change brings a modest but significant improvement in
32 bit workloads.
Relnotes: yes
PR: 135718
Taken from: ache
|
|
|
|
|
|
|
|
|
| |
We do not use iconv.alias file, so avoid using the vestiges
of the code that do.
Differential Revision: https://reviews.freebsd.org/D1729
Reviewed by: emaste
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
| |
Commit r279154 changed the API and ABI significantly, and {NZERO} is still
wrong.
Also, preserve errno on success instead of setting it to 0.
PR: 189821
Reported by: bde
Relnotes: yes
|
|
|
|
|
|
|
| |
interposes the symbol.
Noted by: rpaulo
MFC after: 3 days
|
|
|
|
|
|
| |
CID: 978412
Reviewed by: brooks, delphij
CodeReview: https://reviews.freebsd.org/D1976
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On FreeBSD socklen_t is unsigned so the check negative len
in inet6_opt_append() is redundant and likely to be optimized
away by the compiler.
On other operating systems this is not necessarily so, and
in the future we may want to sign it so leave the check in
but place it in a secondary position as a subtle indication
that the bogus check is intentional.
Discussed with: rpaulo
CID: 1017783
|
|
|
|
|
|
|
|
| |
any applications which need unpredictable random numbers, not merely those
which are cryptographic in nature.
If you work for a lottery and you're using random(3) to select the winning
numbers, please let me know.
|
|
|
|
|
|
|
|
|
|
| |
Our man page already documented this partially but now
we have some consistent behavior.
PR: 136669
Obtained from: NetBSD (CVS rev. 1.31, 1.33)
Relnotes: yes
MFC after: 3 weeks
|
|
|
|
|
|
| |
PR: 189821
Obtained from: NetBSD
Relnotes: yes
|
|
|
|
|
| |
As a follow up to r279090, if dp hasn't been defined, we
shouldn't attempt to do an optimization here.
|
|
|
|
|
| |
CID: 405582 (also clang static checker)
CID: 1018724
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
"The dbm_store() and dbm_delete() functions shall return 0 when they
succeed and a negative value when they fail."
Reference:
http://pubs.opengroup.org/onlinepubs/9699919799/functions/dbm_clearerr.html
PR: 42422
Suggested by: delphij
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
These only occur upon error.
Code Review: https://reviews.freebsd.org/D1849
Reviewed by: delphij
CID: 1016715
CID: 1016717
|
|
|
|
| |
information, and is not really bugs, but limitations for other reasons...
|
|
|
|
|
|
|
| |
These were found by gcc 5.0 on Dragonfly BSD, however I
made no attempt to silence the false positives.
Obtained from: DragonFly (cf515c3a6f3a8964ad592e524442bc628f8ed63b)
|
|
|
|
|
|
|
|
|
|
|
| |
rlim_t is at least as large as long, so we don't need the
extra variable to keep the intermediate step. We don't
need the volatile either.
The code was tested on i386 and amd64.
Suggested by: bde
X-MFC with: r278803
|
|
|
|
|
| |
Sponsored by: The FreeBSD Foundation
MFC after: 3 days
|
|
|
|
|
|
|
| |
trampoline as part of the MD __sys_sigaction again.
Submitted by: kib (initial versions)
MFC after: 3 days
|
|
|
|
|
|
|
| |
The risk of an overrun here is very low but check the
length, JIC.
CID: 1019039
|
|
|
|
|
|
| |
It does no harm but this is not needed after the
correction in r278805 and I prefer to keep this
code very similar to it's original state.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
As a followup to r278363, there is one more case where
stayopen can be accessed uninitialized, but even after
swapping arguments, access is possible in some other
cases so prevent it completely by initializing stayopen.
CID: 1018729
CID: 1018732
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The existing implementation had a broken comparison that could
overflow and return confusing values. Replace this with a check
that avoids the overflow before it happens.
Consistently return a maximum value also on the case of negative
arguments since negative is considered an overflow and means
infinity for our current setrlimit().
New revamped version is credited to Bruce Evans.
CID: 1199295
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
| |
particular, stdio locking was affected.
Reported and tested by: "Matthew D. Fuller" <fullermd@over-yonder.net>
Sponsored by: The FreeBSD Foundation
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
overflow size_t.
Obtained from: DragonFly (2841837793bd095a82f477e9c370cfe6cfb3862c dillon)
Security: CERT VU#695940
MFC after: 3 days
|
|
|
|
| |
Will be back, with proper compiler workarounds.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The existing implementation had a broken comparison that could overflow.
Replace this with a check that avoids the overflow before it happens.
Consistently return a maximum value also on the case of negative
arguments since negative is considered an overflow and means
infinity for our current setrlimit().
Discussed with: bde (rather extensively)
CID: 1199295
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
| |
from r202992. The refcount on the cache entry is not initialized, so
any attempt to clean the cache will skip over this item since it likely
has a >0 value.
This change is currently a NOP. There is work in progress to support
freeing the cache which requires this change to avoid a memory leak.
MFC after: 2 weeks
Sponsored by: EMC / Isilon Storage Division
|
|
|
|
|
|
|
|
|
|
| |
In a couple of cases a variable "stayopen" can be checked
unitialized. This is of no danger as the complementary
condition is false but prevent the access by switching
the checks.
CID: 1018729
CID: 1018732
|
|
|
|
|
| |
MFC after: 1 month
Sponsored by: The FreeBSD Foundation
|
|
|
|
|
| |
The NetBSD revisions correspond to changes we have already done
like __P() removal and ANSI-fication of definitions.
|
|
|
|
|
|
|
|
|
| |
This was a local addition to the original change from NetBSD.
Being this libc there is some chance for it to interfere with
user's cget*() functions usage. The memory leak was finely
plugged by r278300.
Pointed out by: ache
|