Re: git: 43741377b143 - main - security/openssl: Security update to 1.1.1n

From: Christoph Moench-Tegeder <cmt_at_burggraben.net>
Date: Fri, 18 Mar 2022 20:28:06 UTC
## Thomas Zander (riggs@freebsd.org):

> And look what I found:
> 
> root@p13xRamd64-default:~ # hexdump -C
> /usr/local/lib/python3.8/site-packages/setuptools/__init__.py
> 00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
> *
> 00001e00

Exactly.

> 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).

Regards,
Christoph

-- 
Spare Space