From owner-freebsd-stable@freebsd.org Sun Jan 3 18:30:19 2016 Return-Path: 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 82332A60C33 for ; Sun, 3 Jan 2016 18:30:19 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: from mail-pf0-x22d.google.com (mail-pf0-x22d.google.com [IPv6:2607:f8b0:400e:c00::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 5999B14AC; Sun, 3 Jan 2016 18:30:19 +0000 (UTC) (envelope-from yaneurabeya@gmail.com) Received: by mail-pf0-x22d.google.com with SMTP id q63so154294427pfb.0; Sun, 03 Jan 2016 10:30:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=i9KqJkK1vHrD5Hu1oZ+tb7AwsqRv1/46cHzeT48HDiM=; b=hlJhy5NGXW/RsCcwtNMoTaDemhyE6WxiX0g2wQFktByEaOyJMfMKfgb5Wh4y3f3Sv5 w9NZfqK3q4STraCtVjWz1iVYbvIIAF15GOZWp2El2teaDG6qEs0+flY0V9Rxc59EibM0 QodR2HIiP7YOtc9I1wZXcrfaLcFTHVdOSMUXvj7hWp0oMCbv1EmJH8NQAKzTU+IJ35Fq FYSN4w2mjQQIgyMyubMWpmi4gDYPpxwaMm/VzYjWPngg1MejTEzcASnlbTJv5jAxy09z 46zRIFTmjLSLMS/4ritlSCP0bZv1IwtprUPowgimn1JevZsPhCbWyma548diNIGFCA2k W2kg== X-Received: by 10.98.2.78 with SMTP id 75mr88736966pfc.14.1451845818916; Sun, 03 Jan 2016 10:30:18 -0800 (PST) Received: from ?IPv6:2601:601:800:126d:44c7:137c:1c65:f048? ([2601:601:800:126d:44c7:137c:1c65:f048]) by smtp.gmail.com with ESMTPSA id k77sm33723469pfb.37.2016.01.03.10.30.17 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 03 Jan 2016 10:30:17 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\)) Subject: Re: [HEADS UP] "options ZFS" broken on stable/10; please use zfs(4) module for the time being From: NGie Cooper In-Reply-To: Date: Sun, 3 Jan 2016 10:30:16 -0800 Cc: FreeBSD-Stable ML , Marcel Moolenaar Content-Transfer-Encoding: quoted-printable Message-Id: <67AA1D00-44B5-4F45-8699-C9BEA5713D17@gmail.com> References: To: Mariusz Zaborski X-Mailer: Apple Mail (2.2104) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 03 Jan 2016 18:30:19 -0000 > On Jan 3, 2016, at 06:42, Mariusz Zaborski = wrote: >=20 > Hi, >=20 > Did you merge the changes made in = ./sys/cddl/compat/opensolaris/sys/nvpair.h and = https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D201356 ? Those twos = should repair the problem. >=20 > Thanks for doing all the work around merging it. Hi Mariusz! I figured out the missing revisions to get things working again = on stable/10 (the revisions I listed below were the sticking point to = getting this working 100%). There are a lot of changes around pci(9) / = nv(9) that I=E2=80=99ll be putting out for review soon, so the backport = of pci_iov(9) and nv(9) can be completed (I need to do some more testing = soon and some careful inspection to ensure KBI guarantees and the like = are maintained). All in all I=E2=80=99m hoping that this can be fixed =E2=80=9Csoon= =E2=80=9D (sometime in the next week or so). Thanks! -NGie r293093 | ngie | 2016-01-03 01:11:55 -0800 (Sun, 03 Jan 2016) | 21 lines MFC r279437,r284107: r279437 (by rstone): Allow Illumos code to co-exist with nv(9) Suggested by: pjd r284107 (by avg): compat nvpair.h: make sure that the names are mangled only for kernel Currently there is no good reason to mangle the userland API. The change was introduced in eac1d566b46edef765754203bef22c75c1699966, r279437. Also see https://reviews.freebsd.org/D1881. I am still convinced that nv should not have introduced intentionally conflicting API. Discussed with: rstone=