From owner-freebsd-current@freebsd.org Tue Jun 7 04:09:06 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 06C6EB6D1A9 for ; Tue, 7 Jun 2016 04:09:06 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: from mail-it0-f51.google.com (mail-it0-f51.google.com [209.85.214.51]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id C246E18AB; Tue, 7 Jun 2016 04:09:05 +0000 (UTC) (envelope-from cse.cem@gmail.com) Received: by mail-it0-f51.google.com with SMTP id z189so66167358itg.0; Mon, 06 Jun 2016 21:09:05 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to:cc; bh=Q6YTZQ87PMZ9Ix/uxIom2YvYXU9WEcMY+Xg5PQeP70A=; b=Ynd05VGNpX3qxSP0QqIGLtwFZiLv3zMKT6Jxz5xy1M1RfPpewPXj0KT2xbe5lre/2B qbe6o9xilFWYPGbZCNmfgcguhc3uw3F1DTjrt8Lhc21V/ucKNiPdnDBFqKIACKXW7zLt jeC+3zge4hOVkyYTiuQaBclnB7agPzkAU+3xLI6mVNUCtvLWu+dR4/6kYC1TLXsuZin3 jrFhPVby73l+5wauoqQGIILiF7aoWv539MK04UM1wJidKlZ6LDxdoKZMfHhPkMnBIahW CjjAq25TlC3E+0aFRbnoUvv2yOdksjKPOGcGkMzcXg5PEIQNo2JqS6aY1O3vlo7lh8gg ZBBQ== X-Gm-Message-State: ALyK8tIacw+Or2q0gf9atUiQ/YsI4yB/04p55rt48vwmd6tUEXJzxV1y5/HlkC48whLE3Q== X-Received: by 10.36.32.130 with SMTP id t124mr555323itt.37.1465272539345; Mon, 06 Jun 2016 21:08:59 -0700 (PDT) Received: from mail-it0-f44.google.com (mail-it0-f44.google.com. [209.85.214.44]) by smtp.gmail.com with ESMTPSA id h125sm10793476ioa.20.2016.06.06.21.08.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 06 Jun 2016 21:08:59 -0700 (PDT) Received: by mail-it0-f44.google.com with SMTP id z189so66167059itg.0; Mon, 06 Jun 2016 21:08:58 -0700 (PDT) X-Received: by 10.107.46.158 with SMTP id u30mr26511379iou.162.1465272538801; Mon, 06 Jun 2016 21:08:58 -0700 (PDT) MIME-Version: 1.0 Reply-To: cem@freebsd.org Received: by 10.36.205.70 with HTTP; Mon, 6 Jun 2016 21:08:58 -0700 (PDT) In-Reply-To: <20160607024610.GI38613@kib.kiev.ua> References: <20160604022347.GA1096@wkstn-mjohnston.west.isilon.com> <20160604093236.GA38613@kib.kiev.ua> <20160606171311.GC10101@wkstn-mjohnston.west.isilon.com> <20160607024610.GI38613@kib.kiev.ua> From: Conrad Meyer Date: Mon, 6 Jun 2016 21:08:58 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: thread suspension when dumping core To: Konstantin Belousov Cc: Mark Johnston , freebsd-current Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jun 2016 04:09:06 -0000 On Mon, Jun 6, 2016 at 7:46 PM, Konstantin Belousov wrote: > On Mon, Jun 06, 2016 at 10:13:11AM -0700, Mark Johnston wrote: >> On Sat, Jun 04, 2016 at 12:32:36PM +0300, Konstantin Belousov wrote: >> > Does your fs both set TDF_SBDRY and call lf_advlock()/lf_advlockasync() ? >> >> It doesn't. This code belongs to a general framework for distributed FS >> locks; in this particular case, the application was using it to acquire >> a custom advisory lock. > What statement was not true: that your code sets TDF_SBDRY, or that > the lf_advlock() function was called ? We set TDF_SBDRY; we don't call lf_advlock(). I don't have the core yet, so I can't get the thread information, sorry. Best, Conrad