| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
the idea and a good chunk of the implementation is copied from
bridge(4).
note that IP packets inside "service delimited" traffic, ie, vlan,
svlan, or bpe encapsulated traffic, are not considered IP and will
therefore not be given to pf to look at. if you want to filter that
you'll need to configure vlan/svlan/bpe interfaces to get past their
headers, and then configure them with their own tpmrs. hopefully
the interface input handlers were established in the right order.
|
|
the spec says we should filter packets destined to a list of ethernet
addresses. im currently interpreting "filter" as meaning dropping,
which this diff does.
however, one of the addresses to filter is the one lacp uses by
default and not a lot of lacp implementations (read switches) support
the configuration of a different address. i still need lacp to go
over tpmr, and because i can't change the address, this diff also
has a way to configure tpmr to still allow the packets through.
|
|
- the symbol it found, returned via the second argument
- the base offset of the the object it was found in, via the return value
- optionally: the object it was found in, returned via the last argument
Instead, return a struct with the symbol and object pointers and let the
caller get the base offset from the object's obj_base member. On at least
aarch64, amd64, mips64, powerpc, and sparc64, a two word struct like this
is passed in registers.
ok mpi@, kettenis@
|
|
(stirng -> string)
ok kettenis@ who pointed out I should fix the new arm64 smbiosvar.h too
|
|
or sending an IPI.
|
|
|
|
|
|
differences between the i386 and amd64 versions of the code and
switch to using the standard C integer exact width integer types.
ok deraadt@
|
|
|
|
|
|
ok deraadt@, jsg@
|
|
directories obtained by chdir(2).
|
|
|
|
|
|
approach was not right, and there is still room for improvement.
OK deraadt@
|
|
if the parent and the lookup vnode are equal, namei(9) reference
counts both. So release the parent vnode uncoditionally.
OK visa@
|
|
ok jmatthew
|
|
|
|
Use umount(8) to check that the mountpoint leaks no vnode.
|
|
|
|
release.
|
|
|
|
|
|
ok kettenis@
|
|
ok deraadt@, kettenis@
|
|
ok kettenis
|
|
so the file cannot be re-executed upon the next boot. This provides a
stronger one-shot-upgrade model than the upgrade script's rm /bsd.upgrade.
Now various forms of upgrade failure will reboot into /bsd, which is probably
more recoverable. Performing fchmod -x depends on (1) use of MI boot.c
(not alpha/macppc/sparc64/sgi/octeon) and (2) "can write blocks" functionality
in the IO layer. Most architectures have this support now.
Two diagnostics "fchmod a-x %s: failed" and "/bsd.upgrade is not u+x" will
remain in the tree while refinements happen for some of the laggard
architectures.
based upon a discussion florian
tested in snapshots for more than a week without any complaints
|
|
for lapic timer init to avoid calibrating against the 8254 clock.
Some newer machines are shipping with the 8254 clock gated for power
saving, so it may not be usable.
ok mlarkin
discussed with deraadt
|
|
processor identification purposes. Use the name instead of the ID as
the sentinel in the various tables since X-Gene has PartNum zero.
Note that this means Ampere eMAG gets recognized as Applied Micro
X-Gene r3p2. That makes sense as the CPU started its life as X-Gene 3.
Apparently future Ampere parts will use the new Ampere Implementer ID.
ok jsg@
|
|
|
|
|
|
|
|
delete unimportant .Pp rule and shorten overly specific selectors
|
|
Also, inject fault and verify that package does indeed not get fully deleted
|
|
omission reported by Andras Farkas <deepbluemistake at gmail dot com>;
OK deraadt@ jmc@, and Andras Farkas also checked the patch
|
|
enough memory for the device table to cover the entire DeviceID space.
ok patrick@
|
|
files into the common namei.h header.
OK deraadt@
|
|
|
|
get updated when handling an AST after an interrupt.
OK deraadt@
|
|
per-process itimers: itimerval -> itimerspec
Loongson runs at 128hz. 128 doesn't divide evenly into a million,
but it does divide evenly into a billion. So if we do the per-process
itimer bookkeeping with itimerspec structs we can have error-free
virtual itimers on loongson just as we do on most other platforms.
This change doesn't fix the virtual itimer error alpha, as 1024 does not
divide evenly into a billion. But this doesn't make the situation any
worse, either.
ok deraadt@
|
|
Loongson runs at 128hz. 128 doesn't divide evenly into a million,
but it does divide evenly into a billion. So if we do the per-process
itimer bookkeeping with itimerspec structs we can have error-free
virtual itimers on loongson just as we do on most other platforms.
This change doesn't fix the virtual itimer error alpha, as 1024 does not
divide evenly into a billion. But this doesn't make the situation any
worse, either.
ok deraadt@
|
|
bz#3037 from Jitendra Sharma
|
|
|
|
the crash is caused by a logic error leading to a fatal()
ok deraadt@ bluhm@ benno@
|
|
tweaked along the way by at least myself and tj;
ok tj deraadt
|
|
|
|
|
|
|
