From owner-freebsd-bugs@FreeBSD.ORG  Sun Nov 16 15:57:11 2014
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 1CE86BC8
 for <freebsd-bugs@FreeBSD.org>; Sun, 16 Nov 2014 15:57:11 +0000 (UTC)
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 04B1E82E
 for <freebsd-bugs@FreeBSD.org>; Sun, 16 Nov 2014 15:57:11 +0000 (UTC)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id sAGFvAQ3065620
 for <freebsd-bugs@FreeBSD.org>; Sun, 16 Nov 2014 15:57:10 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 195061] Reproducable kernel panic on 10.1-Release when creating
 a zfs pool
Date: Sun, 16 Nov 2014 15:57:11 +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-RC2
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Many People
X-Bugzilla-Who: smh@FreeBSD.org
X-Bugzilla-Status: Open
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-195061-8-GHfLbxXIi9@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-195061-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-195061-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 16 Nov 2014 15:57:11 -0000

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

--- Comment #6 from Steven Hartland <smh@FreeBSD.org> ---
Created attachment 149484
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=149484&action=edit
Disable free on file backed vdevs

Looking at what vdev_file_io_start is doing (calling vn_rdwr) its not clear to
me why there should be any difference between in behaviour ZFS backed and UFS
backed as they would both end up doing a write, which is of course incorrect in
both cases.

The Disable free on file backed vdevs patch extends Xin's patch to ensure
ZIO_TYPE_FREE can never get through to a file backed vdev even if we're called
without checking vdev_notrim.

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