| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
ifdef list that currently lists all the non-i386 platforms that bpf
currently works on.
|
| |
|
|
|
|
| |
Submitted by: tmm
|
| |
|
|
|
|
|
|
| |
is an application space macro and the applications are supposed to be free
to use it as they please (but cannot). This is consistant with the other
BSD's who made this change quite some time ago. More commits to come.
|
|
|
|
| |
Remove a stale comment from bpf_validate().
|
| |
|
|
|
|
|
|
|
|
|
| |
of the additional checks in rev.1.12 was wrong. The others are a
bit inconsistent and are probably unnecessarily pessimal. Checking
for overflow of addition, if necessary at all, should be done in
bpf_validate().
PR: 12484
|
| |
|
|
|
|
|
|
|
|
| |
conditionals to be fully resistent against overflow in unsigned
computations.
Potential problem pointed out by: bde
Reviewed by: bde
|
| |
|
|
|
|
|
|
| |
* On the alpha, make sure memory accesses are only made to aligned boundaries.
Submitted by: Alex Nash <nash@mcs.net>
|
| |
|
|
|
|
| |
ready for it yet.
|
|
|
|
|
|
|
|
| |
This will make a number of things easier in the future, as well as (finally!)
avoiding the Id-smashing problem which has plagued developers for so long.
Boy, I'm glad we're not using sup anymore. This update would have been
insane otherwise.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In rare cases, when the filter specified accesses an multi-byte value that
is split across mbuf's, the value loaded is incorrect. And if you are very
unlucky (like me) it will index off the end of the mbuf and into an
unallocated page and panic the system.
If you look at the code you will discover the the index *k* is added to
the pointer *cp* and the used AGAIN as a subscript.
|
| |
|
|
|
|
|
| |
Reviewed by: Rodney W. Grimes
Submitted by: John Dyson and David Greenman
|
|
|