Date: Sun, 6 Sep 1998 08:30:07 +0400 From: "Andrey A. Chernov" <ache@nagual.pp.ru> To: Mike Smith <mike@smith.net.au>, current@FreeBSD.ORG Cc: dfr@FreeBSD.ORG Subject: Re: sbflush 2 panic, uipc_socket2.c Message-ID: <19980906083007.A19996@nagual.pp.ru> In-Reply-To: <19980904143152.A20161@nagual.pp.ru>; from ache@nagual.pp.ru on Fri, Sep 04, 1998 at 02:31:52PM %2B0400 References: <19980904103427.A3368@nagual.pp.ru> <199809040024.AAA01179@word.smith.net.au> <19980904143152.A20161@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Sep 04, 1998 at 02:31:52PM +0400, Andrey A. Chernov wrote: > On Fri, Sep 04, 1998 at 12:24:25AM +0000, Mike Smith wrote: > > > On Thu, Sep 03, 1998 at 01:15:02PM +0000, Mike Smith wrote: > > > > > Approx. once a day I have this panic (see subj.) on heavily loaded > > > > > -current HTTP server. Is any solution possible? Briefly looking through > > > > > code I think some sort of spl protection needed between freeing sb_cc and > > > > > checking it again. > > > > > > > > That sounds reasonable. What have you tried so far? > > > > > > No, just gather more panic details: > > > > How about whacking an splnet() around it and letting us know how it > > goes? > > No, the code already under splnet() from tcp_usr_disconnect() > It means that internal mbuf structure is changed somehow under splnet() I found that the panic trigger is new ip defragmenting code from dfr, there is no such panic before this commit. ssh key exchange (large packets) can effectively cause panic after 10min when someone quickly log in with ssh after machine come after reboot. -- Andrey A. Chernov http://www.nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980906083007.A19996>