Date: Wed, 9 Nov 2005 07:58:44 -0600 (CST) From: Mark Tinguely <tinguely@casselton.net> To: snezhko@indorsoft.ru, tinguely@casselton.net Cc: max@love2party.net, freebsd-current@freebsd.org Subject: Re: CURRENT + amd64 + user-ppp = panic Message-ID: <200511091358.jA9DwiC0045661@casselton.net> In-Reply-To: <upspai5xa.fsf@indorsoft.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Thank-you for correcting me, I mistakenly did not look at which case was caught in the trash_dtor(). I also was not thinking MBUF when I suggested trace locations. m_sanity() in kern/uipc_mbuf.c will also set "0xdeadc0de" if the "sanitize" option is requested. But common sense says that your trash_dtor() code should catch this before it gets set, but if you wish to test there also it would put my mind at ease. In the mean time, I will look for callouts that are not stopped before they are freed. So far, I found the &sp->ifstart_callout in the file net/if_spppsubr.c started but not stopped before freed, but you are not using that routine. I will concentrate on the files that you listed were changed. --Mark Tinguely
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200511091358.jA9DwiC0045661>