Date: Tue, 13 Mar 2007 14:27:46 -0800 From: "Kip Macy" <kip.macy@gmail.com> To: "Kris Kennaway" <kris@obsecurity.org> Cc: Dag-Erling Sm?rgrav <des@des.no>, kmacy@freebsd.org, Julian Elischer <julian@elischer.org>, FreeBSD Current <current@freebsd.org> Subject: Re: LOCK_PROFILING variant struct sizes (Re: netstat wierdness?) Message-ID: <b1fa29170703131527l443ffb3m71a5e8e0a03a8f@mail.gmail.com> In-Reply-To: <20070313214823.GA13287@xor.obsecurity.org> References: <45F388D4.2080900@elischer.org> <45F45172.8070601@elischer.org> <86r6rt6z27.fsf@dwp.des.no> <45F706A2.5020106@elischer.org> <20070313214823.GA13287@xor.obsecurity.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Kip made some changes to this recently, perhaps he can comment.
I haven't actually fixed this yet - but having a LOCK_PROFILING kernel
panic with a non-LOCK_PROFILING kernel module is very annoying. I'm
not sure how to handle, I'm debating about adding a pointer to the
lock object and moving the lock profiling data elsewhere.
-Kip
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1fa29170703131527l443ffb3m71a5e8e0a03a8f>