From owner-freebsd-net Tue Feb 22 7: 5:27 2000 Delivered-To: freebsd-net@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 70B3837B697; Tue, 22 Feb 2000 07:05:23 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA07676; Tue, 22 Feb 2000 10:05:16 -0500 (EST) (envelope-from wollman) Date: Tue, 22 Feb 2000 10:05:16 -0500 (EST) From: Garrett Wollman Message-Id: <200002221505.KAA07676@khavrinen.lcs.mit.edu> To: Yoshinobu Inoue Cc: asmodai@bart.nl, freebsd-current@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Panic (TCP) In-Reply-To: <20000222132327B.shin@nd.net.fujitsu.co.jp> References: <20000221134724.J84100@lucifer.bart.nl> <20000221223459W.shin@nd.net.fujitsu.co.jp> <20000221144858.O84100@lucifer.bart.nl> <20000222132327B.shin@nd.net.fujitsu.co.jp> Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org < said: > If persist timer is working, and if it happen to timeout between > callout_reset(tp->tt_rexmt, tp->t_rxtcur, > tcp_timer_rexmt, tp); > and > callout_stop(tp->tt_persist); > then the panic might happen at tcp_setpersist(). This should never happen, since this code is supposed to be running at splnet(), which is supposed to block timeouts. Rather than papering over the problem, I'd like to understand how it's possible. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message