From owner-freebsd-current@freebsd.org  Mon Nov  6 17:57:01 2017
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@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 A2D49E63CD5
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Mon,  6 Nov 2017 17:57:01 +0000 (UTC) (envelope-from ian@freebsd.org)
Received: from outbound1a.eu.mailhop.org (outbound1a.eu.mailhop.org
 [52.58.109.202])
 (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 3FCD67CCC3
 for <freebsd-current@freebsd.org>; Mon,  6 Nov 2017 17:57:00 +0000 (UTC)
 (envelope-from ian@freebsd.org)
X-MHO-User: d5f9102f-c31b-11e7-b805-f37e907b5733
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 73.78.92.27
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from ilsoft.org (unknown [73.78.92.27])
 by outbound1.eu.mailhop.org (Halon) with ESMTPSA
 id d5f9102f-c31b-11e7-b805-f37e907b5733;
 Mon, 06 Nov 2017 17:56:53 +0000 (UTC)
Received: from rev (rev [172.22.42.240])
 by ilsoft.org (8.15.2/8.15.2) with ESMTP id vA6Hub2H001454;
 Mon, 6 Nov 2017 10:56:37 -0700 (MST) (envelope-from ian@freebsd.org)
Message-ID: <1509990997.99235.92.camel@freebsd.org>
Subject: Re: [HEADS UP] posix_fallocate support removed from ZFS, lld affected
From: Ian Lepore <ian@freebsd.org>
To: Allan Jude <allanjude@freebsd.org>, freebsd-current@freebsd.org
Date: Mon, 06 Nov 2017 10:56:37 -0700
In-Reply-To: <65d93f93-31d9-0caa-d1b2-4ed21e90df21@freebsd.org>
References: <7e5599e4-2faa-29b6-4fb2-a0744a12681a@FreeBSD.org>
 <1509989176.99235.79.camel@freebsd.org>
 <65d93f93-31d9-0caa-d1b2-4ed21e90df21@freebsd.org>
Content-Type: text/plain; charset="ISO-8859-1"
X-Mailer: Evolution 3.18.5.1 FreeBSD GNOME Team Port 
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Nov 2017 17:57:01 -0000

On Mon, 2017-11-06 at 12:49 -0500, Allan Jude wrote:
> On 2017-11-06 12:26, Ian Lepore wrote:
> > 
> > On Mon, 2017-11-06 at 17:40 +0200, Andriy Gapon wrote:
> > > 
> > > From UPDATING:
> > > The naive and non-compliant support of posix_fallocate(2) in ZFS
> > > has been removed as of r325320.  The system call now returns EINVAL
> > > when used on a ZFS file.  Although the new behavior complies with the
> > > standard, some consumers are not prepared to cope with it.
> > > One known victim is lld prior to r325420.
> > > 
> > It just popped into my head... does this mean that kernels running
> > r325320+ on systems using ZFS will be unable to host build jails for
> > earlier versions / branches because lld will fail in the jail?
> > 
> > I think that will be a big problem for the ports team's package
> > building process, and for anyone using poudriere.
> > 
> > -- Ian
> > 
> lld is not the default on amd64 yet. So only people who have set the
> src.conf knob, or are building a platform like aarch64 that uses lld by
> default, would be impacted.
> 

Oh, right.  lld != ld.

-- Ian