| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
a RealTek 8169SB.
PR: 74262
Submitted by: Yoshikazu GOTO-san
# Submitter notes that he's unsure of the revision string for 8169SB
|
|
|
|
|
|
|
|
| |
witness_proc_has_locks(), as they are unused, which results in a compiler
error. This problem was introduced with the implementation of "show
alllocks".
Spotted by: Artem Kuchin <matrix at itlegion dot ru>
|
|
|
|
|
|
| |
can occur after an ibss merge
Submitted by: David Young
|
|
|
|
|
|
|
|
|
| |
objects (message queues, semaphores, shared memory), exercising and
validating MAC labels on these objects.
Submitted by: Dandekar Hrishikesh <rishi_dandekar at sbcglobal dot net>
Obtained from: TrustedBSD Project
Sponsored by: DARPA, SPAWAR, McAfee Research
|
|
|
|
| |
unless our ssid is specified
|
|
|
|
| |
net.wlan.X.inact -> net.wlan.X.inact_run
|
|
|
|
|
|
|
|
| |
objects (message queues, semaphores, shared memory).
Submitted by: Dandekar Hrishikesh <rishi_dandekar at sbcglobal dot net>
Obtained from: TrustedBSD Project
Sponsored by: DARPA, SPAWAR, McAfee Research
|
|
|
|
|
|
|
|
|
|
|
| |
frame includes FCS (requires applications to be updated, but since
we weren't doing the out-of-line FCS stuff anyway app changes
were needed already)
o add a flag to indicate padding exists between the 802.11 header and
the payload (e.g. for Atheros cards)
o diff reducation against netbsd
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
(message queues, semaphores, shared memory).
Submitted by: Dandekar Hrishikesh <rishi_dandekar at sbcglobal dot net>
Obtained from: TrustedBSD Project
Sponsored by: DARPA, SPAWAR, McAfee Research
|
|
|
|
|
|
|
|
| |
queues, semaphores, shared memory).
Submitted by: Dandekar Hrishikesh <rishi_dandekar at sbcglobal dot net>
Obtained from: TrustedBSD Project
Sponsored by: DARPA, SPAWAR, McAfee Research
|
|
|
|
|
|
|
|
|
| |
in mddestroy() to properly free already allocated memory.
This fixes a panic when we want to create too big memory backed device
with preallocate memory (-o reserve).
- Remove redundant { }.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
bad address range through /dev/kmem can panic the machine.
Submitted by: Mark W. Krentel
Reported by: Kris Kennaway
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
Framework entry points for System V IPC shared memory.
Submitted by: Dandekar Hrishikesh <rishi_dandekar at sbcglobal dot net>
Obtained from: TrustedBSD Project
Sponsored by: DARPA, SPAWAR, McAfee Research
|
|
|
|
| |
a bug repeatedly reported.
|
|
|
|
|
|
|
|
| |
Framework entry points for System V IPC semaphores.
Submitted by: Dandekar Hrishikesh <rishi_dandekar at sbcglobal dot net>
Obtained from: TrustedBSD Project
Sponsored by: DARPA, SPAWAR, McAfee Research
|
|
|
|
|
|
|
|
| |
Framework entry points for System V IPC message queues.
Submitted by: Dandekar Hrishikesh <rishi_dandekar at sbcglobal dot net>
Obtained from: TrustedBSD Project
Sponsored by: DARPA, SPAWAR, McAfee Research
|
|
|
|
|
|
|
| |
have more than 256 units, you die. Horribly. Convert them using
unit2minor.
MFC after: 1 week
|
|
|
|
| |
Submitted by: ru
|
|
|
|
|
|
|
| |
I meant trunc_page. It's only a coincidence this hasn't caused
problems yet.
Pointed out by: Antoine Brodin <antoine.brodin@laposte.net>
|
|
|
|
|
|
|
| |
address, nor do we need the alignment requirements, so eliminate them.
This likely means that we can now collapse some of the entries as we
have no need of them anymore (they match other entries and were there
only to get the right attr memory offset of the enet addr).
|
|
|
|
|
|
| |
really a state change.
Reword the info a bit.
|
|
|
|
| |
the plex has no more consumers (e.g. orphaning).
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
designed to help detect tamper-after-free scenarios, a problem more
and more common and likely with multithreaded kernels where race
conditions are more prevalent.
Currently MemGuard can only take over malloc()/realloc()/free() for
particular (a) malloc type(s) and the code brought in with this
change manually instruments it to take over M_SUBPROC allocations
as an example. If you are planning to use it, for now you must:
1) Put "options DEBUG_MEMGUARD" in your kernel config.
2) Edit src/sys/kern/kern_malloc.c manually, look for
"XXX CHANGEME" and replace the M_SUBPROC comparison with
the appropriate malloc type (this might require additional
but small/simple code modification if, say, the malloc type
is declared out of scope).
3) Build and install your kernel. Tune vm.memguard_divisor
boot-time tunable which is used to scale how much of kmem_map
you want to allott for MemGuard's use. The default is 10,
so kmem_size/10.
ToDo:
1) Bring in a memguard(9) man page.
2) Better instrumentation (e.g., boot-time) of MemGuard taking
over malloc types.
3) Teach UMA about MemGuard to allow MemGuard to override zone
allocations too.
4) Improve MemGuard if necessary.
This work is partly based on some old patches from Ian Dowse.
|
| |
|
|
|
|
| |
config handler. Tidy up various local apic initialization.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
cards work. These changes depend on the expanded funce parsing that
just was committed to pccard_cis.c. In NetBSD the ethernet address
was read out of attr memory directly. We rely on the kernel pccard
parser to pulll this information out of what appears to be an obsolete
funce with the information in it.
# I'm still getting the no rx interrupt sometimes with some hub/switches
# for reasons unknown... But usually only one and only when dhclient
# runs.
|
|
|
|
|
|
|
|
|
| |
as type 0, rather than the usualy type 4. Assume that this format is
from an old standard and go with it. The Fujitsu FMV-186A and Silicom
Ethernet cards I have both have tuples with this format, and they are
both pretty old cards.
# if somebody knows for sure, please let me know.
|
|
|
|
| |
a process that has mmap'd device mem exits.
|
|
|
|
| |
Submitted by: John Cagle
|
|
|
|
| |
While I'm there, remove dead code.
|
|
|
|
|
|
|
|
|
|
| |
in BSD class, ie. if provider below us uses the same metadata, don't
create slices based on the metadata.
This allows to create slices on geoms with rank != 1 without hacks.
Discussed with: phk
Approved by: phk
MFC after: 2 weeks
|
|
|
|
|
| |
expected to be unknown in some cases, and printing it clutters up
things too much.
|
| |
|
|
|
|
|
|
| |
aware of any fe based cards that do anything except network (well,
maybe the fujitsu scsi/lan card, but I've only seen two of those on
ebay in the last 3 years).
|
| |
|
|
|
|
|
|
| |
(from a PC Card sense), so this should be a nop. The
pseudo-multifunction cards (eg Silicom ones) need a special driver
anyway..
|
|
|
|
|
| |
(pccard sense) sn based cards, but this won't hurt. The
pseudo-multifunction cards need a special driver anyway...
|
|
|
|
| |
aware of any multi-function cs cards, but it doesn't hurt).
|
| |
|
| |
|
|
|
|
| |
Fix a comment
|
|
|
|
| |
intersil IDs but their own name in the CIS.
|
|
|
|
|
|
|
|
|
| |
replacement address for an rdr rule. Some rdr rules have no address family
(when the replacement is a table and no other criterion implies one AF).
In this case, pf would fail to select a replacement address and drop the
packet due to translation failure.
Found by: Gustavo A. Baratto
|
|
|
|
| |
Info submitted by: Paulo Fragoso
|
| |
|
|
|
|
|
|
|
| |
into a small array. Also, re-save the dev in attach to avoid
depending on side effects of the probe.
Weird stuff Reported by: jeffr
|