Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 2 Apr 2022 14:04:21 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        Christian Weisgerber <naddy@mips.inka.de>
Cc:        FreeBSD-STABLE Mailing List <freebsd-stable@freebsd.org>
Subject:   Re: FreeBSD 13.1-RC1 Now Available
Message-ID:  <CANCZdfoU7bWxCm3FVqnp4oDyKC0pGkxteaW%2B8SXfy5mCOVS-EA@mail.gmail.com>
In-Reply-To: <YkiqyGMaLK6k6/SV@lorvorc.mips.inka.de>
References:  <20220401024029.GR76435@FreeBSD.org> <a16fe272-3e1a-c9d5-6e02-4b76f2502ee9@nicandneal.net> <8dc4c525-7117-4fc6-8b10-812128bf07c1@www.fastmail.com> <CANCZdfqx2pCDBeags7=pcC5pOEaKY5Gajy-uOHsQVUcGF1JdNw@mail.gmail.com> <YkiqyGMaLK6k6/SV@lorvorc.mips.inka.de>

next in thread | previous in thread | raw e-mail | index | archive | help
--0000000000005424a205dbb167ca
Content-Type: text/plain; charset="UTF-8"

On Sat, Apr 2, 2022 at 2:01 PM Christian Weisgerber <naddy@mips.inka.de>
wrote:

> Warner Losh:
>
> > This suggests that we've broken the KBI we were trying to keep stable
> > between 13.0
> > and 13.1....
>
> When I updated my stable/13 machine from source, from
> March 16 to March 30, DRM was broken (did nothing).
> Rebuilding graphics/drm-fbsd13-kmod fixed it.
>
> So there was an ABI break in this time window.  This entry from
> UPDATING implicates LinuxKPI changes as a likely candidate:
>
> 20220327:
>         Bump __FreeBSD_verion to 1301501 after merging LinuxKPI and
>         net80211 changes in order to help out-of-tree consumers to deal
>         accordingly.
>

Yes. So there was. https://reviews.freebsd.org/D33915 should unbreak the
KPI and give us wiggle room in the future after 13.0 is no longer
supported. That will restore the KBI and we'll pretend that March 27 -
April 2nd/3rd never happened (the least bad of several bad alternatives).

Warner

--0000000000005424a205dbb167ca
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sat, Apr 2, 2022 at 2:01 PM Christ=
ian Weisgerber &lt;<a href=3D"mailto:naddy@mips.inka.de">naddy@mips.inka.de=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
Warner Losh:<br>
<br>
&gt; This suggests that we&#39;ve broken the KBI we were trying to keep sta=
ble<br>
&gt; between 13.0<br>
&gt; and 13.1....<br>
<br>
When I updated my stable/13 machine from source, from<br>
March 16 to March 30, DRM was broken (did nothing).<br>
Rebuilding graphics/drm-fbsd13-kmod fixed it.<br>
<br>
So there was an ABI break in this time window.=C2=A0 This entry from<br>
UPDATING implicates LinuxKPI changes as a likely candidate:<br>
<br>
20220327:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Bump __FreeBSD_verion to 1301501 after merging =
LinuxKPI and<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 net80211 changes in order to help out-of-tree c=
onsumers to deal<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 accordingly.<br></blockquote><div><br></div><di=
v>Yes. So there was. <a href=3D"https://reviews.freebsd.org/D33915">https:/=
/reviews.freebsd.org/D33915</a> should unbreak the KPI and give us wiggle r=
oom in the future after 13.0 is no longer supported. That will restore the =
KBI and we&#39;ll pretend that March 27 - April 2nd/3rd never happened (the=
 least bad of several bad alternatives).</div><div><br></div><div>Warner</d=
iv></div></div>

--0000000000005424a205dbb167ca--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfoU7bWxCm3FVqnp4oDyKC0pGkxteaW%2B8SXfy5mCOVS-EA>