From owner-freebsd-stable@freebsd.org  Fri Dec  2 17:29:13 2016
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@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 933A0C62407
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Fri,  2 Dec 2016 17:29:13 +0000 (UTC) (envelope-from daniel@byte.nl)
Received: from mail-out.s1.byte.nl (mail-out.s1.byte.nl [46.21.235.134])
 (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 5E2FCF77
 for <freebsd-stable@freebsd.org>; Fri,  2 Dec 2016 17:29:13 +0000 (UTC)
 (envelope-from daniel@byte.nl)
Received: from localhost (localhost [127.0.0.1])
 by mail-out.s1.byte.nl (Postfix) with ESMTP id 95DB614530C
 for <freebsd-stable@freebsd.org>; Fri,  2 Dec 2016 18:23:18 +0100 (CET)
Received: from mail-out.s1.byte.nl ([127.0.0.1])
 by localhost (mail-out1.c1.internal [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id qBgMLSXhl5IT for <freebsd-stable@freebsd.org>;
 Fri,  2 Dec 2016 18:23:17 +0100 (CET)
Received: from webmail.byte.nl (gw.c101.byte.nl [46.21.225.7])
 (Authenticated sender: byte0030)
 by mail-out.s1.byte.nl (Postfix) with ESMTPA id 0C4DE145467
 for <freebsd-stable@freebsd.org>; Fri,  2 Dec 2016 18:23:17 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII;
 format=flowed
Content-Transfer-Encoding: 7bit
Date: Fri, 02 Dec 2016 18:23:17 +0100
From: Daniel Genis <daniel@byte.nl>
To: freebsd-stable@freebsd.org
Subject: Any chance that r299900 can be merged to releng-10.3 from stable-10 ?
Message-ID: <2d984d886c9ae01e0b9e14776a573247@webmail.byte.nl>
X-Sender: daniel@byte.nl
User-Agent: Roundcube Webmail/1.2.0
X-Byte-Mail-Received-Via: smtp-auth
X-Byte-SASL-User: byte0030
X-Byte-Domain-ID: 1
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Dec 2016 17:29:13 -0000

Hello everyone!

I'm wondering is there any chance for r299900 (git commit hash 
d99ba5cdb) to be merged to releng-10.3 ?
That error can cause our BSD fileservers to enter a panic and reboot. 
We're running that exact commit hash
on a few servers, and it's been running good for us!

We would love to have that fix and FreeBSD-EN-16:17.vm in our kernel, 
but the above patch is in 10-stable only.

What's our best solution?

Should we cherry-pick the patch into releng-10.3 and basically roll our 
own kernel?


In general we're a bit puzzled about which commits make it from 
10-stable into releng-10.3,
it seams like there are alot of bugfixes inside 10-stable which are not 
exposed to all those
who are not running/compiling their own kernels.


Any suggestions/advice is appreciated! :-)


With kind regards,

Daniel