| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
only one set is needed for either endianess. This also completes them for
big endian archs and fixes the compilation of libncp, netncp, etc. there.
Reviewed by: bp, rwatson
Compile tested on: i386, sparc64
MFC after: 1 week
|
| |
|
|
|
|
| |
alternative is much worse.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o Move the sysctls under debug.psm.* and hw.psm.* making them a bit
clearer and more consistent with other drivers.
o Remove the debug.psm_soft_timeout sysctl. It was introduced many
moons ago in r1.64 but never referenced anywhere.
o Introduce hw.psm.tap_threshold and hw.psm.tap_timeout to control
the behaviour of taps on touchpads. People might like to fiddle
with these if tapping seems to slow or too fast for them.
o Add debug.psm.loglevel as a tunable so that verbosity can be set
easily at boot-time (to watch probes and such) without having to
compile a kernel with options PSM_DEBUG=N.
|
|
|
|
|
|
| |
Spell NULL right in a KASSERT() panic message.
MFC after: 1 week
|
| |
|
|
|
|
|
|
| |
Submitted by: bkoenig at cs dot tu-berlin dot de
PR: 72238
MFC after: 2 weeks
|
|
|
|
|
|
|
|
| |
which doesn't end in \n, since it may be very confusing. Also this should
increase consistency, since most other config files work just fine regardless
of the presence of traling \n in the last line.
MFC After: 2 weeks
|
|
|
|
|
|
| |
what is going on, to replace it. Slight formatting changes
Code here is alredy different to NetBSD.
MFC after: 1 week
|
|
|
|
|
|
| |
scatter gather segments.
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
| |
that the RFC 793 specification for accepting RST packets should be
following. When followed, this makes one vulnerable to the attacks
described in "slipping in the window", but it may be necessary in
some odd circumstances.
|
|
|
|
|
|
| |
Large thanks to the easy-to-read and well-documented
sys/isofs/cd9660 source code, which provided many of the
details I needed for this exercise.
|
| |
|
|
|
|
| |
an error that there is no aicasm.1 man page.
|
|
|
|
|
|
| |
particular, enabling interpreter workarounds for bad ASL.
MFC after: 1 day
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Reference-count the directory data so that
we don't leak memory.
* Correctly step through the directory records
(skipping unrecognized extensions)
* Use better defaults for file modes
* Sort directory entries by offset of the end of the file
rather than the beginning of the file. This fixes a
lot of "out-of-order" problems with zero-length files,
in particular.
* Style fixes, remove some debug code, add some error messages.
|
| |
|
| |
|
|
|
|
|
|
| |
potentially panicking.
MFC after: 1 week
|
|
|
|
|
| |
ia64 subdirectory. All ia64 specific regression tests live under
the ia64 directory.
|
|
|
|
|
|
| |
float, double and long double types. No post-increment tests yet.
All tests are skipped if the debug.unaligned_test sysctl variable
cannot be set to 1.
|
|
|
|
| |
LIST_FOREACH() is difficult to use correctly, so don't try to.
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
| |
Reviewed by: brueffer
MFC after: 3 days
|
|
|
|
| |
multiple reads of receive buffer state to be performed atomically.
|
|
|
|
|
|
| |
spx_reass() to increase atomicity across multiple operations on the
socket buffer when iterating over the SPX fragment reassembly list
for the ipxpcb, as well a to reduce the number of locking operations.
|
|
|
|
|
|
|
|
| |
record loop for ACK'd data, rather than relying on lokcing in
sbdroprecord() and sowwakeup(), reducing the number of lock operations
as well as eliminating a possible race against the head of the send
buffer mbuf chain. Use the _locked variants of sbdroprecord() and
sowwakeup().
|
|
|
|
| |
avoiding a goto.
|
|
|
|
|
|
| |
the peer address by using M_WAITOK in ipx_setpeeraddr() to prevent
allocation failure. The socket reference used to reach these calls
will prevent the ipxpcb from being released prematurely.
|
| |
|
| |
|
| |
|
|
|
|
| |
been documented.
|
|
|
|
|
|
| |
alignment problems.
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
properly handle the case where a connection is disconnected. The
queue(9)-enabled version of this code broke from the inner but not
outer loop, and so potentially frobbed an ipxpcb flag after the ipxpcb
was free'd, which might be picked up later by the malloc debugging
code. Properly break from the loop context and avoid touching the
cb/ipxpcb after free.
|
| |
|
|
|
|
|
| |
Extend the annotation as to why spx_close() isn't called in spx_reass(),
and mark this code more clearly as broken.
|
|
|
|
| |
Spotted by: Simon L. "Eagle Eye" Nielsen
|
|
|
|
|
|
|
| |
tree.
MFC after: 3 days
Submitted by: bkoenig at cs dot tu-berlin dot de
|
|
|
|
|
|
| |
- bump .Dd
Submitted by: Carl Makin <carl@stagecraft.cx>
|
| |
|
|
|
|
| |
In particular, bsdtar should now recognize ISO9660 images.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This seems to be able to extract a TOC and extract files from
the couple of ISO images I've tested it with.
Treat this as experimental proof-of-concept code for the
moment. There are still a bunch of debug messages (there
are a few oddities in ISO9660 that I haven't yet figured
out how to handle), a lot of bugs to be addressed (this
code leaks memory very badly), and a lot of missing features (no
Rockridge support, in particular). I'd appreciate
feedback from anyone who understands ISO9660 format
better than I do. ;-)
Suggested by: Robert Watson
|
|
|
|
|
|
| |
PR: 68362
Submitted by: Carl Makin <carl@stagecraft.cx>
MFC after: 1 week
|
|
|
|
|
|
|
| |
recent versions of gcc will insert an extra 16 bits of padding in
the structure, corrupting all IPX packet output.
MFC after: 3 days
|
|
|
|
| |
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
connection rates, which is causing problems for some users.
To retain the security advantage of random ports and ensure
correct operation for high connection rate users, disable
port randomization during periods of high connection rates.
Whenever the connection rate exceeds randomcps (10 by default),
randomization will be disabled for randomtime (45 by default)
seconds. These thresholds may be tuned via sysctl.
Many thanks to Igor Sysoev, who proved the necessity of this
change and tested many preliminary versions of the patch.
MFC After: 20 seconds
|
|
|
|
|
|
|
|
| |
expects a locked route reference. This removes a panic that occurs
when connected ipxpcb is closed and its route free'd, and may have been
present since the route locking took place.
MFC after: 2 weeks
|