From 1845f530cba5145fb492c5215954971bef542381 Mon Sep 17 00:00:00 2001 From: rwatson Date: Sun, 9 Jan 2005 05:15:59 +0000 Subject: Protect ipx_pexseq with the IPX PCB list mutex. When processing socket options against IPX PCBs, generally protect PCB fields using the IPX PCB mutex. Where possible, use unlocked reads on integer values to avoid locking overhead. MFC after: 3 weeks --- sys/netipx/ipx_input.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'sys/netipx/ipx_input.c') diff --git a/sys/netipx/ipx_input.c b/sys/netipx/ipx_input.c index d0d01a4..ee1ca23 100644 --- a/sys/netipx/ipx_input.c +++ b/sys/netipx/ipx_input.c @@ -95,7 +95,7 @@ struct ipxpcbhead ipxrawpcb_list; static int ipxqmaxlen = IFQ_MAXLEN; static struct ifqueue ipxintrq; -long ipx_pexseq; +long ipx_pexseq; /* Locked with ipxpcb_list_mtx. */ static int ipx_do_route(struct ipx_addr *src, struct route *ro); static void ipx_undo_route(struct route *ro); -- cgit v1.1