o Add a mutex (sb_mtx) to struct sockbuf. This protects the data in a
socket buffer. The mutex in the receive buffer also protects the data
in struct socket.
o Determine the lock strategy for each members in struct socket.
o Lock down the following members:
- so_count
- so_options
- so_linger
- so_state
o Remove *_locked() socket APIs. Make the following socket APIs
touching the members above now require a locked socket:
- sodisconnect()
- soisconnected()
- soisconnecting()
- soisdisconnected()
- soisdisconnecting()
- sofree()
- soref()
- sorele()
- sorwakeup()
- sotryfree()
- sowakeup()
- sowwakeup()
Reviewed by: alfred
fix a comment that suggested setting ipv6_ipv4mapping to blank. This
will aid in merging with rcng which requires all veriables to be
explicitly set.
Submitted by: Mike Makonnen
MFC after: 1 week
make_dev() to create device nodes for each of the serial port channels
(ttym%d and cuam%d respectively, as borrowed from MAKEDEV). This allows
the rc driver to work in 5.0. I've tested it with only one card, but
will try sticking in a second card tomorrow and see what happens.
Obtained from: mark
Pointy hat to: grog
Change msU macros to mU.
This is only a partial solution; the whole issue of building the
documentation needs to be revisited.
combining too much conditions and as such ended up with the
kernel map instead of the corresponding process map. While
here, remove code to allow access to the stackgap and restyle
slightly to improve readability.
This fix specifically fixes the procfs failure we're having
when reading the process map (cat /proc/curproc/map)
As a minor positive side-effect, code at -O0 is more optimal. As a
minor negative side-effect, certain boundary cases yield no better
code than non-boundary cases. For example, atomic_set_acq_32(p, 0)
does a useless logical OR with value 0. This was previously elimina-
ted as part of if/while optimizations. Non-boundary cases yield
identical code at -O1 and -O2.
checking, followed by a lookup of the process. Do not call
ptrace() for permission checking, but do it inline.
Spotted by: rwatson
o While here, copy-in arguments before we lock. This fixes
a possible permanent lock.
Reviewed by: rwatson
01.cacm 02.implement 03.iosys 04.uprog 06.Clang 15.yacc 16.lex 17.m4
Some of these produce a number of warnings. I don't want to remove
them yet, because some noble soul may decide to remove the cause of
the warnings, but they won't if it doesn't bite them.
Add Caldera license.
Approved by: David Taylor <davidt@caldera.com>
Make buildable under FreeBSD. This one was relatively easy, though it
still contains obscenities.
Add Caldera license.
Approved by: David Taylor <davidt@caldera.com>
Make buildable under FreeBSD.
This one's a real mess. It's full of undefined macros, and in one
place deliberately causes syntax warnings. I've decided against
taking out the undefined macros: they don't alter the format of the
output document, and maybe one day somebody will put in the macro
definitions.
Note that this file corrects a number of format errors which appear in
the O'Reilly 4.4BSD manual set.
Add Caldera license.
Approved by: David Taylor <davidt@caldera.com>
Make buildable under FreeBSD. This was relatively complicated: the
original text used the msU macros, which are available in a number of
different kinds. This version uses a number of mm-like macros,
including AL and BL, which just aren't available in ms, and the msU
macros I've found (even the ones in 4.4BSD) don't have them either. I
replaced them with ms constructs, which makes it format better than
the O'Reilly document, but I wasn't able to get the table of contents
(ms doesn't have that facility).
Add a prominent comment that this is not a reference for any modern
version of C.
`/2' with `>>1'. In the context `>>1' is more appropriate
because it looks like the division is used to restore a
shifted value.
GCC GNATS PR: c/6677
This fixes a problem where wheel-up movement is taken as wheel-down
in the sysmouse protocol.
Do not assume the plain char's are signed; use `signed char' where
char's need to be signed.
Discussed on: audit
Pointed out by: bde
