From owner-freebsd-current Thu Sep 3 03:19:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA24071 for freebsd-current-outgoing; Thu, 3 Sep 1998 03:19:15 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA24062 for ; Thu, 3 Sep 1998 03:19:12 -0700 (PDT) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.1/8.9.1) id OAA01097 for current@freebsd.org; Thu, 3 Sep 1998 14:18:08 +0400 (MSD) (envelope-from ache) Message-ID: <19980903141808.A939@nagual.pp.ru> Date: Thu, 3 Sep 1998 14:18:08 +0400 From: "Andrey A. Chernov" To: current@FreeBSD.ORG Subject: sbflush 2 panic, uipc_socket2.c Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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. -- 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