src-test2/sys/net/if.c, branch release/5.2.0_cvs

This commit was manufactured by cvs2svn to create tag

2004-01-10T05:53:29Z

'RELENG_5_2_0_RELEASE'. This commit was manufactured to restore the state of the 5.2-RELEASE image. Releases prior to 5.3-RELEASE are omitting the secure/ and crypto/ subdirs.

Replace the if_name and if_unit members of struct ifnet with new members

2003-10-31T18:32:15Z

if_xname, if_dname, and if_dunit. if_xname is the name of the interface and if_dname/unit are the driver name and instance. This change paves the way for interface renaming and enhanced pseudo device creation and configuration symantics. Approved By: re (in principle) Reviewed By: njl, imp Tested On: i386, amd64, sparc64 Obtained From: NetBSD (if_xname)

Replace a couple printfs with if_printfs.

2003-10-31T01:35:07Z

Since dp->dom_ifattach calls malloc() with M_WAITOK, we cannot

2003-10-24T16:57:59Z

use mutex lock directly here. Protect ifp->if_afdata instead. Reported by: grehan

Clean up whitespace, remove "register" keyword, ANSIfy.

2003-10-23T13:49:10Z

No functional changes.

protect by IFNET_RLOCK.

2003-10-22T15:10:39Z

- add dom_if{attach,detach} framework.

2003-10-17T15:46:31Z

- transition to use ifp->if_afdata. Obtained from: KAME

AF_LINK sockaddr has to be attached to ifp->if_addrlist until the

2003-10-16T13:38:29Z

end, as many of the code assumes that TAILQ_FIRST(ifp->if_addrlist) is non-null. Submitted by: itojun

Locking for updates to routing table entries. Each rtentry gets a mutex

2003-10-04T03:44:50Z

that covers updates to the contents. Note this is separate from holding a reference and/or locking the routing table itself. Other/related changes: o rtredirect loses the final parameter by which an rtentry reference may be returned; this was never used and added unwarranted complexity for locking. o minor style cleanups to routing code (e.g. ansi-fy function decls) o remove the logic to bump the refcnt on the parent of cloned routes, we assume the parent will remain as long as the clone; doing this avoids a circularity in locking during delete o convert some timeouts to MPSAFE callouts Notes: 1. rt_mtx in struct rtentry is guarded by #ifdef _KERNEL as user-level applications cannot/do-no know about mutex's. Doing this requires that the mutex be the last element in the structure. A better solution is to introduce an externalized version of struct rtentry but this is a major task because of the intertwining of rtentry and other data structures that are visible to user applications. 2. There are known LOR's that are expected to go away with forthcoming work to eliminate many held references. If not these will be resolved prior to release. 3. ATM changes are untested. Sponsored by: FreeBSD Foundation Obtained from: BSD/OS (partly)

I don't know from where the notion that device driver should or

2003-09-28T20:48:13Z

even could call VOP_REVOKE() on vnodes associated with its dev_t's has originated, but it stops right here. If there are things people belive destroy_dev() needs to learn how to do, please tell me about it, preferably with a reproducible test case. Include in bluetooth code rather than rely on to do so. The fact that some of the USB code needs to include still disturbs me greatly, but I do not have time to chase that.