From owner-freebsd-stable@FreeBSD.ORG Wed Feb 15 09:53:33 2012 Return-Path: Delivered-To: stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AD92E106564A; Wed, 15 Feb 2012 09:53:33 +0000 (UTC) (envelope-from asmrookie@gmail.com) Received: from mail-wi0-f182.google.com (mail-wi0-f182.google.com [209.85.212.182]) by mx1.freebsd.org (Postfix) with ESMTP id 103368FC21; Wed, 15 Feb 2012 09:53:32 +0000 (UTC) Received: by wibhn14 with SMTP id hn14so604844wib.13 for ; Wed, 15 Feb 2012 01:53:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=h/KvYmiuqWSxxgzTGIPh+XLkMAogI3Mzqc+tVhIGj6c=; b=F4QLPfaQC+AHZaS+9ZItddLgCKAdtA38O8YeuQf0zfy0FUl5JKOeKqXNrzlR1N/ijN GwAIRW1wJQ788TGzXhkW1jtGsI1s6HNip9cSXw9LTO7d/3aiXrXQPfs4kUQRTLl9UG5t iplhBv6q6GNItOLV6pRQKDPZndmwfzBZEtjtg= MIME-Version: 1.0 Received: by 10.180.106.67 with SMTP id gs3mr7138866wib.7.1329298000086; Wed, 15 Feb 2012 01:26:40 -0800 (PST) Sender: asmrookie@gmail.com Received: by 10.216.177.73 with HTTP; Wed, 15 Feb 2012 01:26:40 -0800 (PST) In-Reply-To: References: Date: Wed, 15 Feb 2012 09:26:40 +0000 X-Google-Sender-Auth: VcyPMcb-QEYeyOLCSmue1ed6mzU Message-ID: From: Attilio Rao To: Pavel Polyakov Content-Type: text/plain; charset=UTF-8 Cc: stable@freebsd.org, daichi@freebsd.org Subject: Re: lock violation in unionfs (9.0-STABLE r230270) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Feb 2012 09:53:33 -0000 2012/2/13, Pavel Polyakov : > http://www.freebsd.org/cgi/query-pr.cgi?pr=165087 > > Occurs simply trying to use unionfs: > mount -t unionfs -o noatime /usr /mnt > > insmntque: mp-safe fs and non-locked vp: 0xfffffe01d96704f0 is not > exclusive locked but should be > KDB: enter: lock violation Pavel, can you give a spin to this patch?: http://www.freebsd.org/~attilio/unionfs_missing_insmntque_lock.patch I think that the unlocking is due at that point as the vnode lock can be switch later on. Let me know what you think about it and what the test does. Attilio -- Peace can only be achieved by understanding - A. Einstein