From owner-freebsd-fs@freebsd.org  Fri Oct 16 12:54:26 2015
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@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 3FB50A16062
 for <freebsd-fs@mailman.ysv.freebsd.org>; Fri, 16 Oct 2015 12:54:26 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2CDF71B86
 for <freebsd-fs@FreeBSD.org>; Fri, 16 Oct 2015 12:54:26 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id t9GCsQrf006298
 for <freebsd-fs@FreeBSD.org>; Fri, 16 Oct 2015 12:54:26 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-fs@FreeBSD.org
Subject: [Bug 201912] panic in smbfs during mount
Date: Fri, 16 Oct 2015 12:54:24 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: rmacklem@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-201912-3630-McrqjjdCtb@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-201912-3630@https.bugs.freebsd.org/bugzilla/>
References: <bug-201912-3630@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 16 Oct 2015 12:54:26 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201912

Rick Macklem <rmacklem@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rmacklem@FreeBSD.org

--- Comment #5 from Rick Macklem <rmacklem@FreeBSD.org> ---
Created attachment 162117
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162117&action=edit
fix a race between smb_iod_destroy() and the smd_iod thread that destroys
mutexes and frees the iod structure prematurely

I think this patch might fix the problem that caused
your crash. Your crash does look somewhat different than
PR#172942, but it does call smb_iod_destroy() via
smb_vc_gone() and that is where the race was.

Unfortunately your crash does suggest that the mount
was trying to do another smb_iod_destroy() when it
had already happened and this might suggest an additional
race that the patch doesn't address.

Since it is somewhat different, I haven't marked it as
a duplicate of PR#172942. I will do that if Martin
reports back that the patch seems to have stopped
the crashes from occurring. (I have no idea how reproducible
these crashes are?

-- 
You are receiving this mail because:
You are the assignee for the bug.