Date: Sat, 19 Mar 2022 09:00:28 +0100 From: Matthias Fechner <mfechner@FreeBSD.org> To: Christoph Moench-Tegeder <cmt@burggraben.net>, Thomas Zander <riggs@freebsd.org> Cc: Bernard Spil <brnrd@freebsd.org>, "ports-committers@FreeBSD.org" <ports-committers@freebsd.org>, dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org Subject: Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n Message-ID: <579f562b-8add-d3f7-77c9-1a6126bd282b@FreeBSD.org> In-Reply-To: <YjTrVsQi0ZTdadQK@elch.exwg.net> References: <202203161919.22GJJBoa095195@gitrepo.freebsd.org> <57fe4987-b67a-50db-677f-0823230297b1@FreeBSD.org> <689663a5a86e27cc5649b2a378ed1cf3@freebsd.org> <b3b4e822-bc87-357f-8e15-3492526c5a9c@FreeBSD.org> <CAFU734wn1kqoQfpuxT%2BSQdZ--VFKawhHwwFimj6Z8RyzLD-bfQ@mail.gmail.com> <YjTV6f5B8IAUFoWm@elch.exwg.net> <YjTb28jXMkJplc8s@elch.exwg.net> <CAFU734zacFy_%2BDvwG6W55X1=Yu8FYLvTV6DbyhW1azkUwXzG3Q@mail.gmail.com> <YjTrVsQi0ZTdadQK@elch.exwg.net>
next in thread | previous in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
--------------e78iz0BzfR7EYQuopA8BwvuH
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Am 18.03.2022 um 21:28 schrieb Christoph Moench-Tegeder:
>> Could the zfs fixes in 13.0-RELEASE-p8 cause new problems?
> Feels like. I reverted all the zfs patches from -p8, and that one port
> which previously reliably created broken files now just works fine.
> For the record, that's commits
> 210991b1f28bfebfff889252445e4fe41b714c7d
> FreeBSD: fix world build after de198f2d9
> f5be20afc3568876c44269420a542627238e4da0
> Fix lseek(SEEK_DATA/SEEK_HOLE) mmap consistency
> 0abaf7f630235933aca9dd5819d4c0aea9985f3a
> FreeBSD: Clean up zfsdev_close to match Linux
> 9dc74c5a4b3d10b20d14ada2db605d73af8a33f0
> Fix handling of errors from dmu_write_uio_dbuf() on FreeBSD
> My gut feeling is on the last one, but I haven't tried analyzing that
> yet (and I've never worked with that code before, so I'm not sure if
> I would spot the problem if I did).
>
> Also, I've to pour one for git: just creating a local branch and revert
> and poke around in there is so much easier than it ever was with svn.
> (Having worked with cvs, svn, hg and git I knew that - but here's the
> example for those who still want to go back).
I can confirm now, the problem is definitely related to the -p8 update.
I rolled back now to -p7 using `freebsd-update rollback`.
I removed complete ccache in `/var/cache/ccache`
I removed all build poudriere packages and rebuild all packages
System is now up and running again.
This all works even if poudriere jail is using -p8. No need to downgrade
the jail/base version poudriere is using.
It is caused by the kernel so the ZFS patch seems to be broken and -p8
should maybe not rolled out to not break more systems of users.
Gruß
Matthias
--
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook
--------------e78iz0BzfR7EYQuopA8BwvuH
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Am 18.03.2022 um 21:28 schrieb
Christoph Moench-Tegeder:<br>
</div>
<blockquote type="cite" cite="mid:YjTrVsQi0ZTdadQK@elch.exwg.net">
<blockquote type="cite" style="color: #007cff;">
<pre class="moz-quote-pre" wrap="">Could the zfs fixes in 13.0-RELEASE-p8 cause new problems?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">Feels like. I reverted all the zfs patches from -p8, and that one port
which previously reliably created broken files now just works fine.
For the record, that's commits
210991b1f28bfebfff889252445e4fe41b714c7d
FreeBSD: fix world build after de198f2d9
f5be20afc3568876c44269420a542627238e4da0
Fix lseek(SEEK_DATA/SEEK_HOLE) mmap consistency
0abaf7f630235933aca9dd5819d4c0aea9985f3a
FreeBSD: Clean up zfsdev_close to match Linux
9dc74c5a4b3d10b20d14ada2db605d73af8a33f0
Fix handling of errors from dmu_write_uio_dbuf() on FreeBSD
My gut feeling is on the last one, but I haven't tried analyzing that
yet (and I've never worked with that code before, so I'm not sure if
I would spot the problem if I did).
Also, I've to pour one for git: just creating a local branch and revert
and poke around in there is so much easier than it ever was with svn.
(Having worked with cvs, svn, hg and git I knew that - but here's the
example for those who still want to go back).</pre>
</blockquote>
<p>I can confirm now, the problem is definitely related to the -p8
update.<br>
I rolled back now to -p7 using `freebsd-update rollback`.</p>
<p>I removed complete ccache in `/var/cache/ccache`<br>
I removed all build poudriere packages and rebuild all packages</p>
<p>System is now up and running again.</p>
<p>This all works even if poudriere jail is using -p8. No need to
downgrade the jail/base version poudriere is using.<br>
It is caused by the kernel so the ZFS patch seems to be broken and
-p8 should maybe not rolled out to not break more systems of
users.<br>
</p>
<p><br>
</p>
<pre class="moz-signature" cols="72">
Gruß
Matthias
--
"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook
</pre>
</body>
</html>
--------------e78iz0BzfR7EYQuopA8BwvuH--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?579f562b-8add-d3f7-77c9-1a6126bd282b>