From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mescal.linbit (office.linbit [213.229.1.138]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.linbit.com (LINBIT Mail Daemon) with ESMTP id 6468A2CF8373 for ; Fri, 15 Sep 2006 15:18:43 +0200 (CEST) From: Philipp Reisner To: drbd-dev@lists.linbit.com Subject: Re: [Drbd-dev] DRBD-8: crash due to incorrect thread termination Date: Fri, 15 Sep 2006 15:19:16 +0200 References: <342BAC0A5467384983B586A6B0B37671038B07C7@EXNA.corp.stratus.com> In-Reply-To: <342BAC0A5467384983B586A6B0B37671038B07C7@EXNA.corp.stratus.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Message-Id: <200609151519.16668.philipp.reisner@linbit.com> List-Id: Coordination of development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Am Freitag, 15. September 2006 00:49 schrieb Graham, Simon: > I reported the issue with threads being stopped synchronously from the > wrong context a while ago but now I've found an actual case that causes > a panic() - if BOTH sides are detached, and you attach one side, the > other will crash apparently because the code attempts to synchronously > stop the sender thread, fails, then discards all the network connection > data as the sender thread is still attempting to use it... > > Just thought I'd pass on an easy test case (since I don't know how to > fix this one ;-). > Great, a test case, is a nice motivation to fix the issue ! But I am=20 running out of time today, probably on Monday... =2Dphil =2D-=20 : Dipl-Ing Philipp Reisner Tel +43-1-8178292-50 : : LINBIT Information Technologies GmbH Fax +43-1-8178292-82 : : Sch=F6nbrunnerstr 244, 1120 Vienna, Austria http://www.linbit.com :