| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
parameter.
MFC after: 3 days
|
| |
| |
| |
| |
| |
| |
| |
| | |
with r265456 _r_debug_postinit can be used for RD_POSTINIT events. rtld(1)
uses r_debug_state for dl state transitions, so we use its address for
RD_DLACTIVITY events.
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
allowed range or when one or more pages are not mapped. This according to
The Open Group Base Specifications Issue 7.
Discussed with: attilio, Bruce Evans
Reviewed by: alc, Garrett Cooper
Reported by: ATF
MFC after: 2 weeks
Sponsored by: EMC / Isilon storage division
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
file are always built the same.
(Note that Header and Localstuff must appear first and in that order, the
sorting does not affect as a coincident effect).
Submitted by: sjg
MFC after: 3 days
|
| |
| |
| |
| | |
from the latter.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Use of calloc instead of malloc in regex (from OpenBSD).
In this case the change makes no sense since we are using realloc() later.
Reported by: ache
|
| |
| |
| |
| |
| |
| |
| | |
Mostly to reduce differences with OpenBSD.
Obtained from: OpenBSD (CVS rev. 1.17)
MFC after: 3 days
|
| |
| |
| |
| |
| |
| | |
to ensure that the signal is forwarded when proc_continue() is called.
MFC after: 3 weeks
|
| |
| |
| |
| | |
MFC after: 3 days
|
| |
| |
| |
| |
| |
| |
| | |
are found. This improves compatibility with Solaris' libproc and fixes a
number of failing DTrace tests that rely on this feature.
MFC after: 3 weeks
|
| |
| |
| |
| |
| |
| | |
CID: 1007032
Found with: Coverity Prevent(tm)
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is based on a much bigger cleanup done in Illumos.
Reference:
https://www.illumos.org/issues/2077
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
From the OpenBSD log:
The UTF-8 decoder should not accept byte sequences which decode to unicode
code positions U+D800 to U+DFFF (UTF-16 surrogates), U+FFFE, and U+FFFF.
http://www.cl.cam.ac.uk/~mgk25/unicode.html#utf-8
http://unicode.org/faq/utf_bom.html#utf8-4
Reported by: Stefan Sperling
Obtained from: OpenBSD
MFC after: 5 days
|
| |
| |
| |
| |
| |
| | |
Reported by: brueffer
Found with: Coverity Prevent(tm)
CID: 1135301
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
From the OpenBSD log:
The UTF-8 decoder should not accept byte sequences which decode to unicode
code positions U+D800 to U+DFFF (UTF-16 surrogates), U+FFFE, and U+FFFF.
http://www.cl.cam.ac.uk/~mgk25/unicode.html#utf-8
http://unicode.org/faq/utf_bom.html#utf8-4
Reported by: Stefan Sperling
Obtained from: OpenBSD
MFC after: 5 days
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
by adding an argument to the VM_SUSPEND ioctl that specifies how the virtual
machine should be suspended, viz. VM_SUSPEND_RESET or VM_SUSPEND_POWEROFF.
The disposition of VM_SUSPEND is also made available to the exit handler
via the 'u.suspended' member of 'struct vm_exit'.
This capability is exposed via the '--force-reset' and '--force-poweroff'
arguments to /usr/sbin/bhyvectl.
Discussed with: grehan@
|
| |
| |
| |
| | |
Submitted by: Keith White <kwhite@site.uottawa.ca>
|
| | |
|
|\ \
| |/ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
since they don't have an easily recognizable signature, was if they
were the default. This commit rewrites crypt_set_format(3) etc to
address this:
- Use a pointer instead of an index to identify the default format.
This pointer is initialized at compile time to point to the first
first element in the list of supported formats, eliminating the
need for crypt_setdefault(). Using a pointer also simplifies
iterating through the list.
- Associate DES with the magic string "_", which takes care of the
Extended DES format.
- Finally, as a special case, if the salt does not match any known
magic string but matches ^[./0-9A-Za-z]{13}$, it is assumed to be a
DES password and is passed on to crypt_des().
MFC after: 1 week
|
|\ \
| |/ |
|
| | |
|
| |
| |
| |
| | |
MK_INSTALLIB=no.
|
| |
| |
| |
| | |
ineffectual NOMAN= lines. These don't change the build at all.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
An execute-only fd (opened with O_EXEC) allows neither read() nor write()
and is therefore incompatible with all stdio modes. Therefore, the [EINVAL]
error applies.
Also adjust the similar check in freopen() with a NULL path, even though
this checks an fd which is already from a FILE.
|
| |
| |
| |
| |
| | |
version of these files. Keep them within this directory so they can be used
to implement the armv6 version of these functions.
|
| | |
|
| |
| |
| |
| |
| | |
Reviewed by: bms
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| | |
support removed in 2008 (prior to 8.0).
Approved by: deischen, imp
MFC after: 3 days
|
| | |
|
| |
| |
| |
| | |
MFC after: 1 week
|
| |
| |
| |
| |
| | |
Reviewed by: grehan, jhb
Approved by: grehan (co-mentor)
|
| |
| |
| |
| |
| | |
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
|
| |
| |
| |
| |
| |
| |
| | |
first address after the end of the map entry and should therefore be
excluded.
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If realpath() is called on pathnames like "/dev/null/." or "/dev/null/..",
it should fail with [ENOTDIR]. Pathnames like "/dev/null/" already failed as
they should.
Also, put the check for non-directories after lstatting the previous
component instead of when the empty component (consecutive or trailing
slashes) is detected, saving an lstat() call and some lines of code.
PR: kern/82980
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| | |
and finish the job. ncurses is now the only Makefile in the tree that
uses it since it wasn't a simple mechanical change, and will be
addressed in a future commit.
|
| |
| |
| |
| |
| |
| | |
APIs to increase the maximum bandwidth limit.
MFC after: 1 week
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
kqueue(2) already supports EVFILT_PROC. Add an EVFILT_PROCDESC that
behaves the same, but operates on a procdesc(4) instead. Only implement
NOTE_EXIT for now. The nice thing about NOTE_EXIT is that it also
returns the exit status of the process, meaning that we can now obtain
this value, even if pdwait4(2) is still unimplemented.
Notes:
- Simply reuse EVFILT_NETDEV for EVFILT_PROCDESC. As both of these will
be used on totally different descriptor types, this should not clash.
- Let procdesc_kqops_event() reuse the same structure as filt_proc().
The only difference is that procdesc_kqops_event() should also be able
to deal with the case where the process was already terminated after
registration. Simply test this when hint == 0.
- Fix some style(9) issues in filt_proc() to keep it consistent with the
newly added procdesc_kqops_event().
- Save the exit status of the process in pd->pd_xstat, as we cannot pick
up the proctree_lock from within procdesc_kqops_event().
Discussed on: arch@
Reviewed by: kib@
|
| |
| |
| |
| |
| |
| |
| |
| | |
Tested with vlc and a test suite [1].
[1] http://www.erg.abdn.ac.uk/~gerrit/udp-lite/files/udplite_linux.tar.gz
Reviewed by: jhb, glebius, adrian
|
| |
| |
| |
| |
| |
| | |
multiple definitions.
Reported by: sbruno
|
| |
| |
| |
| |
| | |
With SUBDIR_PARALLEL, duplicates in ${SUBDIR} cause harmless but verbose
warnings.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
are unaware of RFC 3542 can construct control messages.
The kernel disallows mixing RFC 2292 behaviour with RFC 3542 behaviour.
Only sockets that have specifically been marked as using the RFC 2292
API can use RFC 2292 specific options. This is all good and well, but
libc itself seems inconsistent with this.
The root cause of this inconsistency seems to relate to the definitions
of IPV6_HOPOPTS and IPV6_DSTOPTS. They are defined in RFC 2292 and re-used
in RFC 3542, yet have distinct values in the kernel. It's for this reason
that the kernel also has definitions for IPV6_2292HOPOPTS and
IPV6_2292DSTOPTS. Not so in libc.
For example: some program calls inet6_option_init() (defined by RFC 2292)
with the RFC 2292 defined IPV6_HOPOPTS and IPV6_DSTOPTS. Before RFC 3542,
this was translated to values of 22 and 23 (resp.) The libc implementation
correctly checks that only options IPV6_HOPOPTS and IPV6_DSTOPTS are given
(as per RFC 2292) but since these defines have taken on the values defined
by RFC 3542 (values 49 and 50 resp,) rejects the correct option values
(22 and 23) passed said program and returns -1.
The precisie fix is to have inet6_option_init() and friends only accept the
RFC 2292 defined IPV6_HOPOPTS & IPV6_DSTOPTS, but that breaks other code
(like mld6query(8)), which seem to not be aware of RFC 3542 and how it
hi-jacked the option names. So the best fix is to accept the options from
both.
Obtained from: Juniper Networks, Inc.
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
pointer for the login name (result). Make sure to handle that
case properly. Improve robustness by checking namelen and then
nul-terminating the provided buffer to simplify subsequent logic.
Obtained from: Juniper Networks, Inc.
MFC after: 1 week
|
| | |
|
| |
| |
| |
| |
| | |
in preference to the user WITHOUT_MAN knob, which should never be set
in normal src Makefiles.
|