| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
net.inet6.ip6.fw with upcomming ipfw2 improvement for IPv6.
Requested by: bz
|
|
|
|
|
|
|
| |
In other words, change pmap_remove_entry() such that it no longer unrefs
the page table page. Now, it only removes the pv entry.
Reviewed by: tegge
|
|
|
|
| |
binaries. A very neat trick.
|
| |
|
|
|
|
| |
result.
|
|
|
|
|
|
|
|
|
| |
#if 0.
- Use pci_enable_busmaster() to enable busmastering instead of frobbing
the command register directly.
- Don't check to see if memory or I/O can be enabled by writing to the
command register. The PCI bus driver's bus_alloc_resource() method
already checks this and will fail if it can't enable the bit.
|
|
|
|
|
|
|
|
| |
everywhere. This means that my_unit is no longer used as well. The
watchdog routine now also prints 'my0: ...' rather than 'm0x0: ...'.
- Don't bzero the softc and don't try to free it in detach or if attach
fails.
- A whitespace fix.
|
|
|
|
|
|
|
|
|
|
|
| |
- Use the driver lock instead of Giant in a bus dma callback.
- Clear IFF_DRV_(RUNNING|OACTIVE) in hme_stop() instead of just clearing
RUNNING in hme_ioctl() to be more like other ethernet drivers.
- Lock the driver lock around mii operations.
- Remove spls.
- Cleanup locking in hme_ioctl().
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
use the station channel properties. Fixes assert failure/bogus
operation when an ap is operating in 11a and has associated stations
then switches to 11g.
Noticed by: Michal Mertl
Reviewed by: avatar
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
code was #ifdef'ed out for a long time.
Submitted by: suz
Obtained from: KAME
|
|
|
|
| |
stirring the hornet's nest. This issue will be resolved by core.
|
|
|
|
|
| |
Submitted by: suz
Obtained from: KAME
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
o add ic_curchan and use it uniformly for specifying the current
channel instead of overloading ic->ic_bss->ni_chan (or in some
drivers ic_ibss_chan)
o add ieee80211_scanparams structure to encapsulate scanning-related
state captured for rx frames
o move rx beacon+probe response frame handling into separate routines
o change beacon+probe response handling to treat the scan table
more like a scan cache--look for an existing entry before adding
a new one; this combined with ic_curchan use corrects handling of
stations that were previously found at a different channel
o move adhoc neighbor discovery by beacon+probe response frames to
a new ieee80211_add_neighbor routine
Reviewed by: avatar
Tested by: avatar, Michal Mertl
MFC after: 2 weeks
|
|
|
|
| |
content of an archive entry to a file descriptor.
|
|
|
|
|
|
| |
lacks ACL_USER).
Thanks to: Marcus Geiger, Joe Esch, and Markus Slopianka
|
|
|
|
| |
Reported by: stefanf
|
| |
|
|
|
|
|
|
| |
- Don't delete the current line when typing `yy'.
- Don't use a possibly stale pointer in cv_paste().
-
|
|
|
|
|
|
| |
vdropl callers expect it to return with interlock still being held.
MFC after: 2 days
|
|
|
|
|
| |
PR: kern/54625
MFC after: 1 week
|
|
|
|
| |
made static.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
(e.g. pim6dd, pim6sd)
MFC after: 3 days
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
least.
Submitted by: osa
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
due to the vm object being locked.
When a process writes large amounts of data to a file, the vm object associated
with that file can contain most of the physical pages on the machine. If the
process is preempted while holding the lock on the vm object, pagedaemon would
be able to move very few pages from PQ_INACTIVE to PQ_CACHE or from PQ_ACTIVE
to PQ_INACTIVE, resulting in unlimited cleaning of dirty pages belonging to
other vm objects.
Temporarily unlock the page queues lock while locking vm objects to avoid lock
order violation. Detect and handle relevant page queue changes.
This change depends on both the lock portion of struct vm_object and normal
struct vm_page being type stable.
Reviewed by: alc
|
|
|
|
| |
nits.
|
|
|
|
|
|
|
| |
to avoid recursing on the driver lock. Not sure why my test box didn't
catch this earlier.
MFC after: 3 days
|
|
|
|
| |
on the P600.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to atomically return either an existing set of IP multicast options for the
PCB, or a newlly allocated set with default values. The inpcb is returned
locked. This function may sleep.
Call ip_moptions() to acquire a reference to a PCB's socket options, and
perform the update of the options while holding the PCB lock. Release the
lock before returning.
Remove garbage collection of multicast options when values return to the
default, as this complicates locking substantially. Most applications
allocate a socket either to be multicast, or not, and don't tend to keep
around sockets that have previously been used for multicast, then used for
unicast.
This closes a number of race conditions involving multiple threads or
processes modifying the IP multicast state of a socket simultaenously.
MFC after: 7 days
|
|
|
|
|
|
| |
PR: docs/84619
Submitted by: Gary W. Swearingen <garys@opusnet.com>
MFC after: 3 days
|
|
|
|
|
|
| |
PR: docs/84660
Submitted by: Dirk Gouders <gouders@et.bocholt.fh-ge.de>
MFC after: 3 days
|
| |
|
| |
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
|
|
| |
list lock, as there has been a report that an alternative lock order
is getting introduced. This should help ferret it out.
Reported by: Ed Maste <emaste at phaedrus dot sandvine dot ca>
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
| |
device driver, owned by the network stack, or initialized by the device
driver before attach and read-only from then on.
Not all device drivers and network stack components currently follow
these rules, especially with respect to IFF_UP, and a few exceptions
with IFF_ALLMULTI.
MFC after: 7 days
|
| |
|
| |
|
| |
|
| |
|
| |
|