Date: Tue, 23 Jun 2015 10:48:22 +0000 (GMT) From: jenkins-admin@freebsd.org To: jenkins-admin@FreeBSD.org, freebsd-stable@freebsd.org Subject: FreeBSD_stable_10 - Build #1518 - Fixed Message-ID: <865892623.19.1435056503013.JavaMail.jenkins@jenkins-9.freebsd.org> In-Reply-To: <615945691.15.1435030977676.JavaMail.jenkins@jenkins-9.freebsd.org> References: <615945691.15.1435030977676.JavaMail.jenkins@jenkins-9.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
FreeBSD_stable_10 - Build #1518 - Fixed: Check console output at https://jenkins.freebsd.org/job/FreeBSD_stable_10/1518/ to view the results. From owner-freebsd-stable@FreeBSD.ORG Tue Jun 23 11:37:12 2015 Return-Path: <owner-freebsd-stable@FreeBSD.ORG> Delivered-To: freebsd-stable@nevdull.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 C1AAEEDB for <freebsd-stable@nevdull.freebsd.org>; Tue, 23 Jun 2015 11:37:12 +0000 (UTC) (envelope-from reko.turja@liukuma.net) Received: from cerebro.liukuma.net (cerebro.liukuma.net [IPv6:2a00:d1e0:1000:1b00::2]) by mx1.freebsd.org (Postfix) with ESMTP id 7EB53FF1 for <freebsd-stable@freebsd.org>; Tue, 23 Jun 2015 11:37:12 +0000 (UTC) (envelope-from reko.turja@liukuma.net) Received: from cerebro.liukuma.net (localhost [127.0.0.1]) by cerebro.liukuma.net (Postfix) with ESMTP id 734488A0497; Tue, 23 Jun 2015 14:37:08 +0300 (EEST) DKIM-Filter: OpenDKIM Filter v2.8.3 cerebro.liukuma.net 734488A0497 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=liukuma.net; s=liukudkim; t=1435059428; bh=ozibXZ7mcRLpAd2G9my3oCPgiuDkGiwa4pU/PB1T+3Q=; h=From:To:References:In-Reply-To:Subject:Date; b=Xdiu74ijg+jShvExmEdymQQGtkbeo7jQ7VocYrbhYOULIiwCQ4lMBs+1/JCWOTS5g 29X0ljW56NxmTdoEwDUVlq5v5Lqp2rD0xn3pesCEHynkDIvYryMYy6zeCDkV5z98dQ 8ozjr4qc44HZcIQk+2XkZMbnYoQntcBB6OBRE8Dg= X-Virus-Scanned: amavisd-new at liukuma.net Received: from cerebro.liukuma.net ([127.0.0.1]) by cerebro.liukuma.net (cerebro.liukuma.net [127.0.0.1]) (amavisd-new, port 10027) with LMTP id OWl2D64oWoR6; Tue, 23 Jun 2015 14:37:07 +0300 (EEST) Received: from Rivendell (dsl-kmibrasgw1-50dfdd-193.dhcp.inet.fi [80.223.221.193]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: ignatz@cerebro.liukuma.net) by cerebro.liukuma.net (Postfix) with ESMTPSA id 6DB758A0494; Tue, 23 Jun 2015 14:37:07 +0300 (EEST) DKIM-Filter: OpenDKIM Filter v2.8.3 cerebro.liukuma.net 6DB758A0494 Message-ID: <D72E17A41F94460C9F827E2933335847@Rivendell> From: "Reko Turja" <reko.turja@liukuma.net> To: "Willem Jan Withagen" <wjw@digiware.nl>, "Daniel Genis" <daniel@byte.nl>, <freebsd-stable@freebsd.org> References: <5588173C.30608@byte.nl> <55887483.1050505@digiware.nl> In-Reply-To: <55887483.1050505@digiware.nl> Subject: Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ? Date: Tue, 23 Jun 2015 14:36:19 +0300 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal Importance: Normal X-Mailer: Microsoft Windows Live Mail 15.4.3555.308 X-MimeOLE: Produced By Microsoft MimeOLE V15.4.3555.308 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org> List-Unsubscribe: <http://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: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>, <mailto:freebsd-stable-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 23 Jun 2015 11:37:12 -0000 -----Original Message----- From: Willem Jan Withagen Sent: Monday, June 22, 2015 11:48 PM To: Daniel Genis ; freebsd-stable@freebsd.org Subject: Re: can the l2arc memory leak fix be pulled into 10.1-RELEASE ? >> We are kind of new to FreeBSD, so we're wondering what are the plans to >> merge these fixes into the 10.1-RELEASE branch ? >> >> We'd love to get these fixes without having to rebuild the kernel. >> Is there any chance for the merge to happen in the near future, or >> should we compile the kernel to get the fixes? >The RELEASE branch is exactly what it says, RELEASE. And is only done >once per version when the actual official RELEASE is. So the next one >will be the upcoming 10.2-RELEASE. Which is schedules for August 2015 >according to: There are actually 2 branches tracking release: RELEASE which is the original release itself and RELENG which is the release+security and some errata fixes. In practice one should always track and compile RELENG sources with production servers, unless there's a bugfix or added driver that's only available in STABLE. > The other way to get to the front of the like is starting and tracking > 10-STABLE which is the running front of the kernel/software development. STABLE means stable ABI, not necessarily that the branch is running stable. It should be considered more as a beta, than something to track if one does want. (Yes, there can be even major breakages in STABLE. It's not usual but it can happen.) The running front of development is HEAD, which is 11.0 at this time - once latest major release gets first "dot" release, the major version number of HEAD gets advanced. HEAD is more or less recommended for those who can deal with debugging breakages and whatnot and can be severely broken from time to time. It looks like at the moment the fix for you would be temporarily track/compile 10.1 STABLE and then once 10.2 is released start tracking 10.2 RELENG -Reko
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?865892623.19.1435056503013.JavaMail.jenkins>