b3fc296326
and dom_sa_len members from struct domain. Pools of fixed-size objects are too rigid for sockaddr_dls, whose size can vary over a wide range. Return sockaddr_dl to its "historical" size. Now that I'm using malloc(9) instead of pool(9) to allocate sockaddr_dl, I can create a sockaddr_dl of any size in the kernel, so expanding sockaddr_dl is useless. Avoid using sizeof(struct sockaddr_dl) in the kernel. Introduce sockaddr_dl_alloc() for allocating & initializing an arbitrary sockaddr_dl on the heap. Add an argument, the sockaddr length, to sockaddr_alloc(), sockaddr_copy(), and sockaddr_dl_setaddr(). Constify: LLADDR() -> CLLADDR(). Where the kernel overwrites LLADDR(), use sockaddr_dl_setaddr(), instead. Used properly, sockaddr_dl_setaddr() will not overrun the end of the sockaddr. |
||
|---|---|---|
| .. | ||
| xebec | ||
| Makefile | ||
| README | ||
| argo_debug.h | ||
| clnl.h | ||
| clnp.h | ||
| clnp_debug.c | ||
| clnp_er.c | ||
| clnp_frag.c | ||
| clnp_input.c | ||
| clnp_options.c | ||
| clnp_output.c | ||
| clnp_raw.c | ||
| clnp_stat.h | ||
| clnp_subr.c | ||
| clnp_timer.c | ||
| cltp_usrreq.c | ||
| cltp_var.h | ||
| cons.h | ||
| cons_pcb.h | ||
| eonvar.h | ||
| esis.c | ||
| esis.h | ||
| files.netiso | ||
| idrp_usrreq.c | ||
| idrp_var.h | ||
| if_eon.c | ||
| iso.c | ||
| iso.h | ||
| iso_chksum.c | ||
| iso_errno.h | ||
| iso_pcb.c | ||
| iso_pcb.h | ||
| iso_proto.c | ||
| iso_snpac.c | ||
| iso_snpac.h | ||
| iso_var.h | ||
| tp.trans | ||
| tp_astring.c | ||
| tp_clnp.h | ||
| tp_cons.c | ||
| tp_driver.c | ||
| tp_emit.c | ||
| tp_events.h | ||
| tp_inet.c | ||
| tp_input.c | ||
| tp_ip.h | ||
| tp_iso.c | ||
| tp_meas.c | ||
| tp_meas.h | ||
| tp_output.c | ||
| tp_param.h | ||
| tp_pcb.c | ||
| tp_pcb.h | ||
| tp_seq.h | ||
| tp_stat.h | ||
| tp_states.h | ||
| tp_states.init | ||
| tp_subr.c | ||
| tp_subr2.c | ||
| tp_timer.c | ||
| tp_timer.h | ||
| tp_tpdu.h | ||
| tp_trace.c | ||
| tp_trace.h | ||
| tp_user.h | ||
| tp_usrreq.c | ||
| tp_var.h | ||
README
In case you were wondering why this code is still present: The ISO (or OSI) stack is still in use by many router vendors (e.g., using IS-IS the OSI equivalent of OSPF, to carry IP routes). Chris. chopps@NetBSD.org