| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
the link arguments.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
a set of symbol definitions (VERSION_DEF) and symbol mappings
(SYMBOL_MAPS).
Add an awk script to generate the version map.
Suggested by: ru
Helped by: ru
Reviewed by: ru
|
|
|
|
|
|
|
| |
PR: docs/86044
Noticed by: Dan Langille <dan@langille.org>
Reviewed by: Jose Biskofski <jbiskofski@grmims.com>
Approved by: trhodes (mentor)
|
| |
|
|
|
|
| |
the quad support on 64-bit platforms.
|
|
|
|
|
|
|
| |
userland. The comment indicated that something in userland needed them, but
make universe can't seem to find any traces of it.
Move <sys/queue.h> include up.
|
|
|
|
| |
Submitted by: davidxu
|
| |
|
|
|
|
|
|
|
| |
usr.sbin/pcvt/keycap source directory.
Found by: phk
MFC after: 3 days
|
|
|
|
|
|
| |
consumers ignore the return value, soabort() is required to succeed,
and protocols produce errors here to report multiple freeing of the
pcb, which we hope to eliminate.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
especially for vchans. It turns out that channel numbering always depend
on d->devcount counter (which keep increasing), while PCMMKMINOR() truncate
everything to 8bit length. At some point the truncation cause the newly
created character device overlapped with the existence one, causing erratic
overall system behaviour and panic. Easily reproduce with something like:
(Luckily, only root can reproduce this)
while : ; do
sysctl hw.snd.pcm0.vchans=200
sysctl hw.snd.pcm0.vchans=100
done
- Enforce channel/chardev numbering within 8bit boundary. Return E2BIG
if necessary.
- Traverse d->channels SLIST and try to reclaim "free" counter during channel
creation. Don't rely on d->devcount at all.
- Destroy vchans in reverse order.
Anyway, this is not the fault of vchans. It is just that vchans are so cute
and begging to be abused ;) . Don't blame her.
Old, hidden bugs.. sigh..
MFC after: 3 days
|
|
|
|
| |
are required for NLS catalog support.
|
|
|
|
|
|
|
|
| |
all other threads at user boundary, the race can crash kernel
under stress testing.
Reviewed by: jhb
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
this corrects problems with drivers that rely on the host to do
crypto (iwi, ipw, ral, ural, wi (hostap), awi)
Hard work by: luigi, mlaier
Reviewed by: luigi, mlaier
MFC after: 1 week
|
|
|
|
|
|
|
| |
common USA ISO rather than index 0 (Belgian).
Reviewed by: jhb
MFC after: 1 day
|
|
|
|
|
|
|
| |
m_unshare and the caller can now control how mbufs are allocated
Reviewed by: andre, luigi, mlaier
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
| |
will be recommitted with the remainder of the change in the next day or
two.
Submitted by: thompsa
|
| |
|
|
|
|
|
|
| |
MD5_DIGEST_STRING_LENGTH.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
applications.
Open[BGP|OSPF]D make use of this to determine the link status of
interfaces to make the right routing descisions.
Obtained from: OpenBSD
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Allow RTM_CHANGE to change a number of route flags as specified by
RTF_FMASK.
- The unused rtm_use field in struct rt_msghdr is redesignated as
rtm_fmask field to communicate route flag changes in RTM_CHANGE
messages from userland. The use count of a route was moved to
rtm_rmx a long time ago. For source code compatibility reasons
a define of rtm_use to rtm_fmask is provided.
These changes faciliate running of multiple cooperating routing
daemons at the same time without causing undesired interference.
Open[BGP|OSPF]D make use of these features to have IGP routes
override EGP ones.
Obtained from: OpenBSD (claudio@)
MFC after: 3 days
|
| |
|
|
|
|
| |
Discussed with: phk
|
|
|
|
|
|
| |
a 42k patch seemed easier to retype than apply, but apparently not. :-)
Submitted by: pjd
|
|
|
|
| |
Pointed out by: Suken Woo, Martin Wilke, Wesley Morgan
|
| |
|
|
|
|
|
| |
PR: kern/93952
Submitted by: Antoine Brodin <antoine.brodin laposte.net>
|
| |
|
| |
|
|
|
|
| |
Pointed out by: ceri, ru, delphij
|
|
|
|
|
| |
without GC'ing the socket if a strong protocol reference to the socket
is present (SS_PROTOREF).
|
|
|
|
|
|
|
|
|
|
| |
protocol to the socket. Normally protocol references are weak: that is,
the socket layer can tear down the socket (and hence protocol state)
when it finds convenient. This flag will allow the protocol to
explicitly declare to the socket layer that it is maintaining a
strong reference, rather than the current implicit model associated
with so_pcb pointer values and repeated attempts to possibly free the
socket.
|
|
|
|
| |
If we don't want manpages, we might still want HTML docs.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
MFC after: 3 days
Submitted by: Kostik Belousov <kostikbel at gmail dot com>
|
|
|
|
| |
PR: kern/75008
|
|
|
|
|
| |
PR: bin/71594
Submitted by: Dan Lukes <dan@obluda.cz>
|
| |
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
| |
it first.
Approved by: andre
|
|
|
|
|
|
|
|
|
| |
if the target is a fifo. After opening a trace file, check that it is a
regular file, and if not, return an error.
MFC after: 3 days
Reported by: kris
PR: 94278
|
|
|
|
|
|
|
|
|
|
|
| |
rather than panicking later. This can occur if the kernel calls
vn_open() on a fifo, as there will be no associated file descriptor,
and therefore the file descriptor operations cannot be modified to
point to the fifo operation set.
MFC after: 3 days
Reported by: Martin <nakal at nurfuerspam dot de>
PR: 94278
|
|
|
|
|
| |
Submitted by: Iain Hibbert < plunky at rya-online dot net >
MFC after: 3 days
|
|
|
|
|
|
| |
'BOOT_HIDE_SERIAL_NUMBERS' knob.
Suggested by: ceri
|
|
|
|
| |
Approved by: portmgr (implicit)
|