From owner-freebsd-fs@freebsd.org  Sat Oct 17 01:40:36 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 DFCF8A168CE
 for <freebsd-fs@mailman.ysv.freebsd.org>; Sat, 17 Oct 2015 01:40:36 +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 CCD4D25C
 for <freebsd-fs@FreeBSD.org>; Sat, 17 Oct 2015 01:40:36 +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 t9H1eaII056783
 for <freebsd-fs@FreeBSD.org>; Sat, 17 Oct 2015 01:40:36 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: Sat, 17 Oct 2015 01:40:36 +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: attachments.created
Message-ID: <bug-201912-3630-0I46cqXdrG@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: Sat, 17 Oct 2015 01:40:37 -0000

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

--- Comment #6 from Rick Macklem <rmacklem@FreeBSD.org> ---
Created attachment 162138
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=162138&action=edit
fixes smbfs so that it doesn't do a disconnect when vc_iod == NULL

This patch (which includes the 162117 one) adds a check for
vc_iod != NULL to the code in smb_vc_disconnect(), since this
function is called when smb_vc_create() fails and vc_iod == NULL
for that case. It also fixes smb_iod_create() so it returns with
vc_iod == NULL when it fails, since it has free'd the iod and it
also adds code to destroy the mutexes for this case.

I believe this patch will fix the crash reported here.

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