From owner-freebsd-amd64@freebsd.org  Wed Jan 20 04:50:18 2016
Return-Path: <owner-freebsd-amd64@freebsd.org>
Delivered-To: freebsd-amd64@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 8C255A87A80
 for <freebsd-amd64@mailman.ysv.freebsd.org>;
 Wed, 20 Jan 2016 04:50:18 +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 7C60A1D34
 for <freebsd-amd64@FreeBSD.org>; Wed, 20 Jan 2016 04:50:18 +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 u0K4oH1v091487
 for <freebsd-amd64@FreeBSD.org>; Wed, 20 Jan 2016 04:50:18 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-amd64@FreeBSD.org
Subject: [Bug 206238] FUSE can't enter to DIRECT_IO mode during file create.
Date: Wed, 20 Jan 2016 04:50:17 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: kern
X-Bugzilla-Version: 10.2-STABLE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: rmacklem@uoguelph.ca
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-fs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-206238-6-5THkIwhxIx@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-206238-6@https.bugs.freebsd.org/bugzilla/>
References: <bug-206238-6@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-Mailman-Approved-At: Wed, 20 Jan 2016 05:20:20 +0000
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64/>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
 <mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jan 2016 04:50:18 -0000

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

--- Comment #5 from rmacklem@uoguelph.ca ---
A guess w.r.t. getting these patches in a release would
be 6mon->1year. Now, the patches will probably make it into
what FreeBSD calls head/current in April and in stable/10
in May. (This assumes that head isn't frozen for the FreeBSD11
release in April.)
(It's too late for the 10.3 release and I'm not sure if/when
 a 10.4 release is planned.)

--=20
You are receiving this mail because:
You are on the CC list for the bug.=