| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
It is no longer necessary to construct long paths consisting of repeated
"../" which may be slow to process and may exceed PATH_MAX.
|
|
|
|
|
|
|
| |
ENOLINK, EPROTO, ENOTCAPABLE.
Submitted by: Alan R. S. Bueno <alan.bsd at gmail.com>
MFC after: 3 days (most)
|
|
|
|
|
|
|
| |
This is required by POSIX and matches open(2).
Reviewed by: kib, jhb
MFC after: 1 month
|
|
|
|
|
| |
whole process. Also explicitely name the parameter that specifies
sleep interval.
|
| |
|
|
|
|
|
|
|
|
| |
operation on a file descriptor that is not authorized by the descriptor's
capability flags.
MFC after: 1 month
Sponsored by: Google
|
|
|
|
|
|
|
|
| |
a caller-allocated buffer of at least MAXPATHLEN, rather than using a
global buffer.
MFC after: 1 month
Sponsored by: Google
|
|
|
|
|
|
|
|
|
| |
one path. When the list is empty (contain only a NULL pointer), return
EINVAL instead of pretending to succeed, which will cause a NULL pointer
deference in a later fts_read() call.
Noticed by: Christoph Mallon (via rdivacky@)
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
| |
Also modify the "-k list" option to display only fields with a certain prefix.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Tolerate applications that pass a NULL pointer for the buffer and
claim that the capacity of the buffer is nonzero.
- If an application passes in a non-NULL buffer pointer and claims the
buffer has zero capacity, we should free (well, realloc) it
anyway. It could have been obtained from malloc(0), so failing to
free it would be a small memory leak.
MFC After: 2 weeks
Reported by: naddy
PR: ports/138320
|
|
|
|
| |
Reviewed by: jkoshy
|
|
|
|
|
|
|
|
|
| |
the type argument. This is known to fix some pthread_mutexattr_settype()
invocations, especially when it comes to pulseaudio.
Approved by: kib
deischen (threads)
MFC after: 3 days
|
|
|
|
|
|
| |
trying backup servers.
PR: kern/103764, misc/139214
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- F_READAHEAD: specify the amount for sequential access. The amount is
specified in bytes and is rounded up to nearest block size.
- F_RDAHEAD: Darwin compatible version that use 128KB as the sequential
access size.
A third argument of zero disables the read-ahead behavior.
Please note that the read-ahead amount is also constrainted by sysctl
variable, vfs.read_max, which may need to be raised in order to better
utilize this feature.
Thanks Igor Sysoev for proposing the feature and submitting the original
version, and kib@ for his valuable comments.
Submitted by: Igor Sysoev <is rambler-co ru>
Reviewed by: kib@
MFC after: 1 month
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
a large page size that is greater than malloc(3)'s default chunk size but
less than or equal to 4 MB, then increase the chunk size to match the large
page size.
Most often, using a chunk size that is less than the large page size is not
a problem. However, consider a long-running application that allocates and
frees significant amounts of memory. In particular, it frees enough memory
at times that some of that memory is munmap()ed. Up until the first
munmap(), a 1MB chunk size is just fine; it's not a problem for the virtual
memory system. Two adjacent 1MB chunks that are aligned on a 2MB boundary
will be promoted automatically to a superpage even though they were
allocated at different times. The trouble begins with the munmap(),
releasing a 1MB chunk will trigger the demotion of the containing superpage,
leaving behind a half-used 2MB reservation. Now comes the real problem.
Unfortunately, when the application needs to allocate more memory, and it
recycles the previously munmap()ed address range, the implementation of
mmap() won't be able to reuse the reservation. Basically, the coalescing
rules in the virtual memory system don't allow this new range to combine
with its neighbor. The effect being that superpage promotion will not
reoccur for this range of addresses until both 1MB chunks are freed at some
point in the future.
Reviewed by: jasone
MFC after: 3 weeks
|
|
|
|
| |
PR: threads/135462
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
query umtx also if the shared waiters bit is set on a shared lock.
The writer starvation avoidance technique, infact, can lead to shared
waiters on a shared lock which can bring to a missed wakeup and thus
to a deadlock if the right bit is not checked (a notable case is the
writers counterpart to be handled through expired timeouts).
Fix that by checking for the shared waiters bit also when unlocking the
shared locks.
That bug was causing a reported MySQL deadlock.
Many thanks go to Nick Esborn and his employer DesertNet which provided
time and machines to identify and fix this issue.
PR: thread/135673
Reported by: Nick Esborn <nick at desert dot net>
Tested by: Nick Esborn <nick at desert dot net>
Reviewed by: jeff
|
|
|
|
|
|
| |
Turn the "AUTHORS" section into a full sentence.
Pointed out by: ru [1]
|
| |
|
|
|
|
|
|
|
|
|
| |
to avoid using incorrect geometry.
It seems that this is the same problem in g_part_bsd_read()@g_part_bsd.c.
Reviewed by: rink
MFC after: 3 days
|
|
|
|
|
|
|
| |
sizes or some number of the sizes themselves. It is functionally
compatible with a function by the same name under Solaris.
Reviewed by: jhb
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
| |
PR: 133765
Submitted by: Konstantin Zolotukhin <erebus@gorodok.net>
MFC after: 3 days
|
|
|
|
|
|
| |
needed to satisfy static libraries that are compiled with -fpic
and linked into static binary afterwards. Several libraries in
gcc are examples of such static libs.
|
|
|
|
|
|
|
| |
following an OOR2 operator.
PR: 130504
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
| |
EV_RECEIPT is useful to disambiguating error conditions when multiple
events structures are passed to kevent(2). The error code is returned
in the data field and EV_ERROR is set.
Approved by: rwatson (co-mentor)
|
|
|
|
|
|
|
|
| |
When the EV_DISPATCH flag is used the event source will be disabled
immediately after the delivery of an event. This is similar to the
EV_ONESHOT flag but it doesn't delete the event.
Approved by: rwatson (co-mentor)
|
|
|
|
|
|
|
|
|
| |
Add user events support to kernel events which are not associated with any
kernel mechanism but are triggered by user level code. This is useful for
adding user level events to an event handler that may also be monitoring
kernel events.
Approved by: rwatson (co-mentor)
|
|
|
|
|
|
|
|
|
|
| |
An additional one coming from http://www.research.att.com/~gsf/testregex/
was not added; at some point the entire AT&T regression test harness
should be imported here.
But that would also mean commitment to fix the uncovered errors.
PR: 130504
Submitted by: Chris Kuklewicz
|
|
|
|
|
|
|
|
| |
if necessary, in the future, adds of new states without breaking ABI
between revisions.
Proposed by: kib
Approved by: imp
|
|
|
|
|
|
| |
PR: threads/138603
Submitted by: Mikulas Patocka
MFC after: 1 week
|
|
|
|
| |
files with NetBSD / OpenBSD versions.
|
|
|
|
|
| |
Add a comment about keeping the private namespace at the end of
the dependency chain.
|
|
|
|
|
|
|
|
|
| |
API, keeping backward compatibility.
First consumer for this functionality is going to become forthcoming MPD-5.4,
supporting CoA and DR of RFC 3576: Dynamic Authorization Extensions to RADIUS.
MFC after: 1 month
|
|
|
|
|
|
|
| |
If you have a one-byte sequence, `w', `b' is the second character. Not
the third.
Submitted by: Christoph Mallon
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Add vesa kernel options for amd64.
- Connect libvgl library and splash kernel modules to amd64 build.
- Connect manual page dpms(4) to amd64 build.
- Remove old vesa/dpms files.
Submitted by: paradox <ddkprog yahoo com> [1], swell k at gmail.com
(with some minor tweaks)
|
|
|
|
|
|
|
|
|
|
|
| |
in a seperate array. As such we need to use kvm_read rather than bcopy
to populate the ki_groups field.
This fixes a crash when running ps -ax on a coredump.
Reported by: brucec
Tested by: brucec
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
(incorrect handling of zero-length reads before the copy buffer is
allocated) is masked by the iso9660 taster. Tar and cpio both enable
that taster so were protected from the bug; unzip is susceptible.
This both fixes the bug and updates the test harness to exercise
this case.
Submitted by: Ed Schouten diagnosed the bug and drafted a patch
MFC after: 7 days
|
|
|
|
|
|
| |
on iso9660 images were returned. While I'm poking around, update
some comments around this area to try to clarify what's going on and
what still remains to be improved.
|
| |
|
|
|
|
|
|
|
| |
according to the 'V' option.
PR: standards/138307
MFC after: 1 week
|
| |
|
|
|
|
| |
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
|
|
|
| |
and acl_calc_mask(3) return error instead of crashing when acl passed
to them is NULL.
Submitted by: markus
Reviewed by: rwatson
MFC after: 3 days
|