Date: Thu, 27 Nov 2003 19:31:49 +1100 From: Tim Robbins <tjr@freebsd.org> To: ?????? ????????? ?????????? <tiamat@komi.mts.ru> Cc: freebsd-current@freebsd.org Subject: Re: recent current panic Message-ID: <20031127083149.GA13249@wombat.robbins.dropbear.id.au> In-Reply-To: <026c01c3b414$e653e7f0$b901320a@komi.mts.ru> References: <026c01c3b414$e653e7f0$b901320a@komi.mts.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Nov 26, 2003 at 03:00:35PM +0300, ?????? ????????? ?????????? wrote: > i got a panic on recent -CURRENT: > > # tcpdump -i lo0 port 23 & > [1] 507 > listening on lo0 This is a known bug; silby@ is working to fix "lo" and the rest of the affected network drivers. See PR kern/59576. Here's the local patch to if_loop.c I'm using until this gets fixed. I've patched if_tun.c similarly. Index: if_loop.c =================================================================== RCS file: /home/ncvs/src/sys/net/if_loop.c,v retrieving revision 1.92 diff -u -r1.92 if_loop.c --- if_loop.c 20 Nov 2003 20:07:37 -0000 1.92 +++ if_loop.c 27 Nov 2003 08:18:33 -0000 @@ -262,6 +262,7 @@ * will only read from the mbuf (i.e., it won't * try to free it or keep a pointer a to it). */ + bzero(&m0, sizeof(m0)); m0.m_next = m; m0.m_len = 4; m0.m_data = (char *)⁡
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031127083149.GA13249>