From nobody Wed Dec 15 03:10:18 2021 X-Original-To: freebsd-stable@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 0048418F4CFF; Wed, 15 Dec 2021 03:10:27 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4JDKxZ6Bk3z4hMy; Wed, 15 Dec 2021 03:10:26 +0000 (UTC) (envelope-from mavbsd@gmail.com) Received: by mail-qt1-x82d.google.com with SMTP id o17so20511073qtk.1; Tue, 14 Dec 2021 19:10:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=sender:subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=53GxFRmVi32R2rqyJTmTPm+ja/p1teL1phSAW9IlCV4=; b=oSlfkEGv346hCR4aWbu9U5IzqcwpRhKfD8telcxBbHBL1dQBpyiB7mRtlNm1PSd1Nx EjJKV98bFdCtnvQqH7sduGB0qnTraiZGayFthgp2UC7BZxns15g9SE94Ez0H/KX7ZSGq nyTlnxUQVydd/3YEB36LvSdASDYKGzMichG8uanNquFZuPM95ctAKPJujknbHwpyWtAg WuLTSDuA2ggQrYQFoKDhXZTmOiSgv66TeDDBK/XvfAyvJSVEvXe87CsPqkLs5m5DOXTd jIaQQJu+eoyshN7A0k7GE6PONDpkH0XIMbgIGUHCNKzirr9xHpdDvZqOTArrb3tO8CM1 0v3Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:sender:subject:to:cc:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=53GxFRmVi32R2rqyJTmTPm+ja/p1teL1phSAW9IlCV4=; b=BWCtdGxjiUemlpmmDUIeqJM1yTfXA99j39jWEjyztM/sTLfr9UvDE2jpZM0C+YtboW Dmtnl2LG+Qm7aflnPK86mL6EhJhILSoD4CR5XwjVTsuJVyrLLFeMJ/mZYqfCI18Ldcnd i5Vn4emj7bawRKfyv5OPWXW89pc0cpxYm0uB7N8uDkKNbQnLGs/Uu/aEsmiHWURxlwfd lk2w4auDYNIhqODjjE2V7Ff7QnRFzyITwMpFiDsvlEUvBGMjf2lTtZ2vQ1/HezIe2tZr g78tq4ucXZdRFjxvz/pdcS+C1B/7TiWI8VEBrsp1Re8oB6c8FfHMc982VKOZ1pE6ps/d hF5w== X-Gm-Message-State: AOAM533VObFIdyIdVnYyStkUiJVfaUagQWw74+JNOs2yAI9WaT+MJ12i apQAeCfSFPjgRT68eBeussjZaQ533/s= X-Google-Smtp-Source: ABdhPJyf1pnHvBpFbxlgiO9v9+9A23P3JG/dsthk/zuL5azkdoIhits4zHjAIon7Wc5wzQ/y+pJL+A== X-Received: by 2002:ac8:7d11:: with SMTP id g17mr10220712qtb.460.1639537819794; Tue, 14 Dec 2021 19:10:19 -0800 (PST) Received: from spectre.mavhome.dp.ua (104-55-12-234.lightspeed.knvltn.sbcglobal.net. [104.55.12.234]) by smtp.gmail.com with ESMTPSA id e17sm563634qtw.18.2021.12.14.19.10.19 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 14 Dec 2021 19:10:19 -0800 (PST) Subject: Re: /usr/share/zfs/compatibility.d/openzfs-2.1-freebsd vs. openzfs-2.1-linux vs. FreeBSD main [so: 14]: edonr status To: Mark Millard Cc: freebsd-current , FreeBSD-STABLE Mailing List References: <928FE23E-C9DB-4473-B8C2-DB3A32529AF4.ref@yahoo.com> <928FE23E-C9DB-4473-B8C2-DB3A32529AF4@yahoo.com> <0C484963-D833-4B12-A9C8-8FADC0EF1D9B@yahoo.com> From: Alexander Motin Message-ID: Date: Tue, 14 Dec 2021 22:10:18 -0500 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0 List-Id: Production branch of FreeBSD source code List-Archive: https://lists.freebsd.org/archives/freebsd-stable List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-stable@freebsd.org X-BeenThere: freebsd-stable@freebsd.org MIME-Version: 1.0 In-Reply-To: <0C484963-D833-4B12-A9C8-8FADC0EF1D9B@yahoo.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Rspamd-Queue-Id: 4JDKxZ6Bk3z4hMy X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N On 14.12.2021 22:00, Mark Millard wrote: > On 2021-Dec-14, at 17:35, Alexander Motin wrote: > >> On 14.12.2021 20:21, Mark Millard wrote: >>> I presume that because of FreeBSD's releng/13.0 and stable/13 (and >>> releng/13.? futures) that: >>> >>> /usr/share/zfs/compatibility.d/openzfs-2.1-freebsd >>> >>> will never have edonr added to the file. Sound right? >> >> FreeBSD stable/13 is tracking still alive upstream zfs-2.1-release >> branch. It is still updated periodically, but primarily with bug fixes. > > I infer from the above that: > > /usr/share/zfs/compatibility.d/openzfs-2.1-freebsd > > is unlikely to be changed to be inaccurate relative to releng/13.0 , at > least as long as 13.0 is a supported FreeBSD release, but probably for > all the releng/13.? . Yes, that would be my personal assumption. >>> Is there going to be a /usr/share/zfs/compatibility.d/openzfs-2.*-freebsd* >>> that has edonr as well (instead of using a openzfs-2.1-linux file for >>> such)? If yes, when does the file show up? Does main get drafts of the >>> file over time until there is a releng/14.0 that would have the final >>> version? >> >> FreeBSD main though tracks openzfs master branch, and as a moving target >> it has no compatibility definitions. I'd expect by the time of FreeBSD >> stable/14 branching there to be some new openzfs branch it could switch >> to, but so far AFAIK there were no specific announcements yet. And >> enabled edonr is a step toward not differentiating FreeBSD and Linux >> compatibility settings any more. > > I infer from the above that it will be much closer to releng/14.0 's > time frame before there will be an additional: > > /usr/share/zfs/compatibility.d/openzfs-*-freebsd* > > ( or a name that does not even mention freebsd or linux but > applies to releng/14.0 ). Good to know. Right. There would be nothing bad to have more openzfs releases before stable/14 branching though, just not after. We'll need to coordinate that with upstream. -- Alexander Motin