cel [Wed, 24 May 2006 18:29:37 +0000 (18:29 +0000)]
While reviewing NFS client for another PR, noticed this omission in the
NFSv4 client READDIR logic. This change matches the logic in the version
2 and 3 code.
emax [Wed, 24 May 2006 00:51:22 +0000 (00:51 +0000)]
MFC:
Add new SIOC_HCI_RAW_NODE_LIST_NAMES ioctl. User-space applications can
use this ioctl to obtain the list of HCI nodes. User-space application
is expected to preallocate 'ng_btsocket_hci_raw_node_list_names' structure
and set limit in 'num_nodes' field. The 'nodes' field should be allocated
as well and it should have space for at least 'num_nodes' elements.
The SIOC_HCI_RAW_NODE_LIST_NAMES should be issued on bound raw HCI socket.
It does not really really matter what HCI name the socket is bound to, as
long as it is not empty.
maxim [Sun, 21 May 2006 09:04:31 +0000 (09:04 +0000)]
MFC rev. 1.32 fsdb.c, rev. 1.11 fsdb.h, rev. 1.19 fsdbutil.c: do
recrack(arguments) for commands which actually take NAME as arguments;
be consistent and print argc - 1 as a command arguments number in
all cases.
date: 2006/05/14 20:23:00; author: krion; state: Exp; lines: +1 -4
The last execution of -exec {} + is not done if the -exec primary is
not on the top-level -and sequence, e.g. inside of ! or -or.
Create a separate linked list of all active -exec {} + primaries and
do the last execution for all at termination.
csjp [Sat, 20 May 2006 02:54:34 +0000 (02:54 +0000)]
MFC revision 1.288
date: 2006/04/10 14:07:28; author: csjp; state: Exp; lines: +0 -2
Kill the last Giant acquisition in the exit(2) code. This Giant acquisition
doesn't appear to be protecting anything. Most of consumers funsetownlst(9)
do not appear to be picking up Giant anywhere. This was originally a part
of my Giant exit(2) clean up revision 1.272 but I thought it was a good idea
to leave it out until we were able to analyze it better.
emax [Sat, 20 May 2006 00:44:00 +0000 (00:44 +0000)]
MFC v1.59 and v1.60
Add kqueue(2) support on if_tap(4) interfaces. While I'm here, replace
K&R style function declarations with ANSI style. Also fix endian bugs
accessing ioctl arguments that are passed by value.
Do not call knlist_destroy() in tapclose(). Instead call it when device is
actually destroyed. Also move call to knlist_init() into tapcreate(). This
should fix panic described in kern/95357.
PR: kern/93897, kern/95357
Submitted by: Vilmos Nebehaj < vili at huwico dot hu >
mux [Fri, 19 May 2006 21:09:20 +0000 (21:09 +0000)]
Fix the build with NO_LIBPTHREAD or NO_LIBTHR depending on the
arch, by merging revision 1.292 from ru@ who was nice enough to
fix this problem in HEAD, but I wasn't paying attention :-).
ps [Fri, 19 May 2006 19:15:05 +0000 (19:15 +0000)]
MFC: rev 1.126
Fix the interrupt handler to do the mandatory PCI flush before looking at
DMA memory. The could contribute towards missed link state changes under
heavy bus load.
emax [Fri, 19 May 2006 16:46:19 +0000 (16:46 +0000)]
MFC:
Correct BD_ADDR entry for "Dummy" device in the default hcsecd.conf.
Each byte in BD_ADDR should exactly two nibbles, i.e
"1:2:3:4:5:6" is NOT valid and "01:02:03:04:05:06" is valid BD_ADDR.
jhb [Thu, 18 May 2006 22:07:01 +0000 (22:07 +0000)]
MFC: Cache the value of the lower half of each I/O APIC redirection table
entry and thus cut the execution time for masking and unmasking I/O APIC
pins in half.
Structural changes: Make a level-2 section for contrib stuff to
mirror the structure on HEAD, move the existing tzdata item (which was
in the wrong place anyway) into it. Add a level-3 section for rc.d
scripts (empty for now)...I probably nuked this accidentally in
rev. 1.883.2.16.
maxim [Wed, 17 May 2006 19:03:33 +0000 (19:03 +0000)]
MFC rev. 1.28 iostat.8 and revs. 1.29 - 1.31 iostat.c: implement
Solaris-like -x and -z flags: show extended disk statistics, omit
lines for devices with no activity. Style and re-register locals.
trhodes [Wed, 17 May 2006 13:26:01 +0000 (13:26 +0000)]
MFC 1.14:
Fix a bug where, for 6-byte sequences, the top 6 bits get compared to
111111 rather than the top 7 bits being compared against 1111110 causing
illegal bytes fe and ff being treated the same as legal bytes fc and fd.
anholt [Wed, 17 May 2006 07:40:12 +0000 (07:40 +0000)]
Merge DRM from -current, including:
- i915 attachment and running fixed
- i915 vblank support
- Radeon's new memory map support, which should fix a host of stability issues
when combined with new userland.
- ATI PCI/PCIE GART fix.
- r300 fixes
Also adds a hack to the radeon module Makefile to quiet gcc's fatal warnings
about inlines in this contrib code.
csjp [Wed, 17 May 2006 00:18:57 +0000 (00:18 +0000)]
MFC revision 1.56
date: 2006/03/03 09:12:21; author: thompsa; state: Exp; lines: +22 -7
Since we are using random ethernet addresses for the bridge, it is possible
that we might have address collisions, so make sure that this hardware address
isn't already in use on another bridge.
csjp [Wed, 17 May 2006 00:11:27 +0000 (00:11 +0000)]
MFC revision 1.55
Slightly re-worked bpf(4) code associated with bridging: if we have a
destination interface as a member of our bridge or this is a unicast packet,
push it through the bpf(4) machinery.
For broadcast or multicast packets, don't bother with the bpf(4) because it will
be re-injected into ether_input. We do this before we pass the packets through
the pfil(9) framework, as it is possible that pfil(9) will drop the packet or
possibly modify it, making it very difficult to debug firewall issues on the
bridge.
Further, implemented IFF_MONITOR for bridge interfaces. This does much the same
thing that it does for regular network interfaces: it pushes the packet to any
bpf(4) peers and then returns. This bypasses all of the bridge machinery,
saving mutex acquisitions, list traversals, and other operations performed by
the bridging code.
This change to the bridging code is useful in situations where individuals use a
bridge to multiplex RX/TX signals from two interfaces, as is required by some
network taps for de-multiplexing links and transmitting the RX/TX signals
out through two separate interfaces. This behaviour is quite common for network
taps monitoring links, especially for certain manufacturers.
csjp [Wed, 17 May 2006 00:09:24 +0000 (00:09 +0000)]
MFC revision 1.215
Unbreak byte counters when network interfaces are in monitor mode by
re-organizing the monitor return logic. We perform interface monitoring
checks after we have determined if the CRC is still on the packet, if
it is, m_adj() is called which will adjust the packet length. This
ensures that we are not including CRC lengths in the byte counters for
each packet.
csjp [Wed, 17 May 2006 00:07:42 +0000 (00:07 +0000)]
MFC revision 1.164
Pickup locks for the BPF interface structure. It's quite possible that
bpf(4) descriptors can be added and removed on this interface while we
are processing stats.
pav [Mon, 15 May 2006 20:53:44 +0000 (20:53 +0000)]
Sync with HEAD except for powerpc bits:
- Add -s flag to limit the length of string fields in the output
brian Jan 2, 2006
- Accept zero len sockaddr_in types
alfred Oct 15, 2005
marius [Mon, 15 May 2006 19:57:59 +0000 (19:57 +0000)]
MFC: 1.97, 1.98. 1.106 (partial)
- Add if_arl_load, if_ath_load, if_axe_load, if_aue_load, if_cs_load,
if_cue_load, if_gem_load, if_hme_load, if_le_load, if_nve_load,
if_rue_load and if_udav_load to the Networking drivers section.
- Remove trailing whitespace in the description of the kern.nbuf entry.
ps [Mon, 15 May 2006 18:53:00 +0000 (18:53 +0000)]
MFC: rev 1.329
Don't try to kill embryonic processes in killpg1(). This prevents
a race condition between fork() and kill(pid,sig) with pid < 0 that
can cause a kernel panic.
emax [Mon, 15 May 2006 16:52:15 +0000 (16:52 +0000)]
MFC:
Teach bthidd(8) to reload its config when SIGHUP is received.
Properly convert L2CAP PSM values in sockaddr_l2cap to LE16 byte order.
Properly map mouse buttons.
Fix typo.
PR: bin/94577
Submitted by: Iain Hibbert, Krzysztof Jedruczyk
cokane [Mon, 15 May 2006 02:09:41 +0000 (02:09 +0000)]
MFC: rev. 1.36
The -b parameter incorrectly stated that pax archives over ~32kB violate
POSIX. Fixed to describe that block size larger than 32256 bytes are
actually what violates POSIX.
jkoshy [Mon, 15 May 2006 01:43:53 +0000 (01:43 +0000)]
MFC {r1.14--r1.16}:
- Spelling/grammar fixes.
- Typo fix: "ing" -> "in".
- Document the EOPNOTSUPP returned by hwpmc(4) if a sampling
mode PMC is requested on a CPU without an APIC.
tegge [Sun, 14 May 2006 01:12:56 +0000 (01:12 +0000)]
MFC: Bring the call to softdep_releasefile() within the region protected by
vn_start_secondary_write() since it might cause file system write
activity (e.g. ffs_snapremove()).
tegge [Sun, 14 May 2006 00:46:13 +0000 (00:46 +0000)]
MFC: Temporarily unlock vnode for new image being executed to avoid lock
order reversals that can lead to deadlocks. Normally vn_close(),
namei() or vrele() should not be called while holding vnode locks.
tegge [Sat, 13 May 2006 23:52:59 +0000 (23:52 +0000)]
MFC: A side effect of calling runningbufwakeup() is that
bp->b_runningbufspace is cleared. Save old value and restore
bp->b_runningbufspace before returning from ffs_copyonwrite().
tegge [Sat, 13 May 2006 23:49:45 +0000 (23:49 +0000)]
MFC: Close a race when VOP_LOCK() on a snapshot file is attempted at the
same time as it is changed back into a normal file. The locker would
get the shared "snaplk" lock which would no longer be the correct lock
for the vnode.