summaryrefslogtreecommitdiffstats
path: root/sys
Commit message (Collapse)AuthorAgeFilesLines
* Bring in support for SUGOI LAN GIGA NIC made by System TALKS, Inc fromimp2005-01-222-0/+4
| | | | | | | | | a RealTek 8169SB. PR: 74262 Submitted by: Yoshikazu GOTO-san # Submitter notes that he's unsure of the revision string for 8169SB
* When DDB is not defined, don't implement witness_thread_has_locks() andrwatson2005-01-221-0/+2
| | | | | | | | 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>
* handle potential stale values of bssid in neighbor nodes thatsam2005-01-221-1/+5
| | | | | | can occur after an ibss merge Submitted by: David Young
* Update mac_test for MAC Framework policy entry points System V IPCrwatson2005-01-221-0/+378
| | | | | | | | | 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
* when ssid suppression is enabled don't respond to probe requestssam2005-01-221-0/+8
| | | | unless our ssid is specified
* be consistent in naming inactivity timers;sam2005-01-221-1/+1
| | | | net.wlan.X.inact -> net.wlan.X.inact_run
* Update mac_stub for MAC Framework policy entry points System V IPCrwatson2005-01-221-5/+213
| | | | | | | | 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
* o replace out-of-line copy of FCS w/ a flag that indicates thesam2005-01-221-9/+18
| | | | | | | | | | | 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
* Implement MLS confidentiality protection for System V IPC objectsrwatson2005-01-221-5/+391
| | | | | | | | (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
* Implement Biba integrity protection for System V IPC objects (messagerwatson2005-01-221-5/+394
| | | | | | | | queues, semaphores, shared memory). Submitted by: Dandekar Hrishikesh <rishi_dandekar at sbcglobal dot net> Obtained from: TrustedBSD Project Sponsored by: DARPA, SPAWAR, McAfee Research
* - Don't destroy UMA zone on error in mdcreate_malloc(), because we need itpjd2005-01-221-4/+1
| | | | | | | | | 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
* Guard against address wrap in kernacc(). Otherwise, a program accessing aalc2005-01-221-0/+5
| | | | | | | | bad address range through /dev/kmem can panic the machine. Submitted by: Mark W. Krentel Reported by: Kris Kennaway MFC after: 1 week
* Invoke label initialization, creation, cleanup, and tear-down MACrwatson2005-01-221-0/+95
| | | | | | | | 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
* Add a couple of mtx_asserts() to try to narrow down the window onphk2005-01-221-0/+2
| | | | a bug repeatedly reported.
* Invoke label initialization, creation, cleanup, and tear-down MACrwatson2005-01-221-0/+83
| | | | | | | | 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
* Invoke label initialization, creation, cleanup, and tear-down MACrwatson2005-01-221-0/+162
| | | | | | | | 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
* Don't pass unadulterated unit numbers to make_dev and its ilk- if youmjacob2005-01-222-5/+6
| | | | | | | have more than 256 units, you die. Horribly. Convert them using unit2minor. MFC after: 1 week
* Embellish rev 1.61. If we're not building a debug kernel, use -O2 as before.obrien2005-01-221-2/+7
| | | | Submitted by: ru
* s/round_page/trunc_page/gbmilekic2005-01-221-4/+4
| | | | | | | I meant trunc_page. It's only a coincidence this hasn't caused problems yet. Pointed out by: Antoine Brodin <antoine.brodin@laposte.net>
* we don't need the offset in the attr memory to get the ethernetimp2005-01-211-14/+12
| | | | | | | 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).
* Only report state changes of subdisks and plexes when there'sle2005-01-211-2/+14
| | | | | | really a state change. Reword the info a bit.
* Don't initialize error with ENXIO as we might end up here whenle2005-01-211-2/+1
| | | | the plex has no more consumers (e.g. orphaning).
* we don't need to make fake sockaddr_in6 to compare subject address.ume2005-01-211-13/+2
| | | | MFC after: 1 week
* Bring in MemGuard, a very simple and small replacement allocatorbmilekic2005-01-216-0/+317
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* Remove prototype of undefined function so this compiles again.phk2005-01-211-2/+0
|
* JumboMFi386: use bitmapped IPI handler. Update elcr and default mptablepeter2005-01-2113-138/+298
| | | | config handler. Tidy up various local apic initialization.
* MFi386: handle PSL_T properly across fork. Typo fix.peter2005-01-211-1/+13
|
* MFi386: whitespace, copyright header, etc updatespeter2005-01-216-7/+3
|
* MFi386: use %rip - 1 for the symbol search address (for noreturn funcs)peter2005-01-211-2/+8
|
* Rework pccard attachment a little. Now both of my fe based ethernetimp2005-01-211-26/+22
| | | | | | | | | | | | 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.
* Some older PC Cards have a weird format for FUNCE tuples. They appearimp2005-01-212-2/+15
| | | | | | | | | 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.
* Fix (accidental?) lock order reversal in pmap_remove. Found whengrehan2005-01-213-3/+3
| | | | a process that has mmap'd device mem exits.
* Remove 6422, V100 and add the P600.ps2005-01-201-2/+1
| | | | Submitted by: John Cagle
* Remove references to non-existing symbols DO_corb and got_mmu.cognet2005-01-201-7/+0
| | | | While I'm there, remove dead code.
* Protect against recursive slices creation in simlar way as it is donepjd2005-01-201-7/+33
| | | | | | | | | | 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
* Don't print 'unknown id' in the ep_pccard_identify routine. It isimp2005-01-201-2/+1
| | | | | expected to be unknown in some cases, and printing it clutters up things too much.
* Remove now-stale commentimp2005-01-201-10/+2
|
* Only attach to network functions. This should be a nop since I'm notimp2005-01-201-0/+10
| | | | | | 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).
* Include necessary declarationsimp2005-01-201-0/+3
|
* Only match ethernet functions. I've not seen any multifunction cardsimp2005-01-201-0/+7
| | | | | | (from a PC Card sense), so this should be a nop. The pseudo-multifunction cards (eg Silicom ones) need a special driver anyway..
* Only attach to network functions. I'm not aware of any multifunctionimp2005-01-201-0/+10
| | | | | (pccard sense) sn based cards, but this won't hurt. The pseudo-multifunction cards need a special driver anyway...
* Only attach to network functions (unlikely to matter since I'm notimp2005-01-201-0/+10
| | | | aware of any multi-function cs cards, but it doesn't hurt).
* u_intXX_t -> uintXX_t while I'm here.imp2005-01-206-33/+33
|
* Only attach to network functions.imp2005-01-202-0/+20
|
* u_intXX_t -> uintXX_timp2005-01-201-9/+9
| | | | Fix a comment
* Use Intersil chip names for the symbols, since many makers use theimp2005-01-202-5/+6
| | | | intersil IDs but their own name in the CIS.
* Use the packet's address family instead of the rule's when selecting adhartmei2005-01-201-1/+1
| | | | | | | | | 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
* Add support for SENAO SL-2511CDimp2005-01-201-1/+2
| | | | Info submitted by: Paulo Fragoso
* Minor tweaks to properly order things.imp2005-01-201-4/+4
|
* Mask off the upper bits of the resource before using it as an indeximp2005-01-201-3/+10
| | | | | | | 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
OpenPOWER on IntegriCloud