From nobody Sat Mar 19 08:00:28 2022 X-Original-To: dev-commits-ports-main@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 9AFEE1A2DD3A; Sat, 19 Mar 2022 08:00:31 +0000 (UTC) (envelope-from SRS0=/PPU=T6=FreeBSD.org=mfechner@anny.lostinspace.de) Received: from anny.lostinspace.de (anny.lostinspace.de [195.30.95.33]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4KLCwv30Y9z3s07; Sat, 19 Mar 2022 08:00:31 +0000 (UTC) (envelope-from SRS0=/PPU=T6=FreeBSD.org=mfechner@anny.lostinspace.de) Received: from server.idefix.lan (194-153-117-131.ip-addr.inexio.net [131.117.153.194]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: idefix@fechner.net) by anny.lostinspace.de (Postfix) with ESMTPSA id 3CA468A70B; Sat, 19 Mar 2022 09:00:29 +0100 (CET) Received: from [IPV6:2a02:6d40:36c1:ac01:98be:9a8b:5f96:e575] (unknown [IPv6:2a02:6d40:36c1:ac01:98be:9a8b:5f96:e575]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by server.idefix.lan (Postfix) with ESMTPSA id 81CB0245C0; Sat, 19 Mar 2022 09:00:28 +0100 (CET) Content-Type: multipart/alternative; boundary="------------e78iz0BzfR7EYQuopA8BwvuH" Message-ID: <579f562b-8add-d3f7-77c9-1a6126bd282b@FreeBSD.org> Date: Sat, 19 Mar 2022 09:00:28 +0100 List-Id: Commits to the main branch of the FreeBSD ports repository List-Archive: https://lists.freebsd.org/archives/dev-commits-ports-main List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-dev-commits-ports-main@freebsd.org X-BeenThere: dev-commits-ports-main@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.7.0 Subject: Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n Content-Language: en-US To: Christoph Moench-Tegeder , Thomas Zander Cc: Bernard Spil , "ports-committers@FreeBSD.org" , dev-commits-ports-all@freebsd.org, dev-commits-ports-main@freebsd.org References: <202203161919.22GJJBoa095195@gitrepo.freebsd.org> <57fe4987-b67a-50db-677f-0823230297b1@FreeBSD.org> <689663a5a86e27cc5649b2a378ed1cf3@freebsd.org> From: Matthias Fechner In-Reply-To: X-Rspamd-Server: anny.lostinspace.de X-Rspamd-Queue-Id: 4KLCwv30Y9z3s07 X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; none X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[] X-ThisMailContainsUnwantedMimeParts: N 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
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--