sysutils/py-google-compute-engine: revive port
This reverts commit 5a7ff5102154b08055c37868810192a9dca8044b and uses
www/py-boto3 instead of the removed devel/py-boto, and releng-gce@
assumes maintainership.
This is meant to be a temporary measure as we are exploring alternatives
for GCE support.
MFH: 2025Q2
(cherry picked from commit 592b450ab9275d2b5423132059ca9e2c231746d1)
sysutils/py-google-compute-engine: revive port
This reverts commit 5a7ff5102154b08055c37868810192a9dca8044b and uses
www/py-boto3 instead of the removed devel/py-boto, and releng-gce@
assumes maintainership.
This is meant to be a temporary measure as we are exploring alternatives
for GCE support.
MFH: 2025Q2
vm_page: make iter_insert() public
In places where vm_page_insert() is used after lookups, or for
consecutive pages, use vm_page_iter_insert instead, to exploit
locality.
Reviewed by: kib, markj
Differential Revision: https://reviews.freebsd.org/D50248
vm_page_grab_pages: fetch page ranges
Define an iterator based function for reading a range of consecutive,
non-NULL leaves from a pctrie. Adapt it to vm pages. Use it in
vm_page_grab_pages to fetch more than one page at a time.
Reviewed by: markj
Differential Revision: https://reviews.freebsd.org/D50253
crypto: Remove uses of CRYPTO_F_DONE
Previously OCF set CRYPTO_F_DONE prior to invoking the completion
callback, even if the request failed. This isn't particularly useful
and leads to bugs when consumers retry a failed request, since OCF also
asserts that CRYPTO_F_DONE is clear in crypto_dispatch(). (Really, OCF
should retry requests that fail with EAGAIN, but that's a larger
change.)
For now, just stop setting CRYPTO_F_DONE to simplify consumers (and fix
those which fail to clear the flag before retrying a request).
PR: 286321
Reviewed by: jhb
Differential Revision: https://reviews.freebsd.org/D50104
krb5: Fix handling of transient crypto request failures
- Instead of using CRYPTO_F_DONE to decide whether a request has
completed, use a custom protocol of setting crp_opaque = NULL in the
callback and checking that instead. CRYPTO_F_DONE is set independent
of whether an error occurred, but for transient errors signaled by
EAGAIN, we want to simply retry the request.
- Clear CRYPTO_F_DONE before retrying the request.
- Panic if the request truly failed, as we currently have no way to
pass hard errors back up.
Reviewed by: jhb
MFC after: 2 weeks
Differential Revision: https://reviews.freebsd.org/D50238
net80211: fix a race between ieee80211_sta_join and scan entries
We were seeing panics during ieee80211_sta_join() which seemed that
the ni->ni_chan was not valid anymore, which was true.
We also saw errors indicating data put into ni_ies became inalid.
The problem was that the ieee80211_scan_entry passed into
ieee80211_sta_join() (in the observed case from setmlme_assoc_sta())
became invalid during ieee80211_alloc_node().
As a result for the ni_chan case the the rateset and len in rates[1]
became invalid. Similarly for the IEs.
Make a (deep)copy of the scan entry in setmlme_assoc_sta() and return
the copy as once we leave ieee80211_scan_iterate() we can no longer
rely on the scan entry to be valid.
Sponsored by: The FreeBSD Foundation
Reported by: rm, ziaee, bz
Tested by: rm, ziaee, bz
[7 lines not shown]
databases/postgresql??-*: Update to latest version
PostgreSQL 17.5, 16.9, 15.13, 14.18, and 13.21 Released!
The PostgreSQL Global Development Group has released an update to all
supported versions of PostgreSQL, including 17.5, 16.9, 15.13, 14.18,
and 13.21. This release fixes 1 security vulnerability and over 60 bugs
reported over the last several months.
Security: 78b8e808-2c45-11f0-9a65-6cc21735f730
Release notes: https://www.postgresql.org/about/news/postgresql-175-169-1513-1418-and-1321-released-3072/
loader: i386: use -z nostart-stop-gc for bfd as well
binutils 2.37 seems to have added the knob, so let's just use that
version here (it's not clear if GC'ing start/stop symbols was actually
made the default at the time, and it didn't seem worth it to dig much
further). This fixes misbehavior when built with more recent binutils,
as we do rely on linker sets for loader commands that we use.
Reported by: sjg
Reviewed by: dim, sjg
Differential Revision: https://reviews.freebsd.org/D50252
net/openrsync: Update 0.0.20200401 => 0.0.20250127 (latest commit)
Commit log:
https://github.com/kristapsdz/openrsync/compare/8b61216...a257c0f
Improve port:
- split long lines,
- reduce number of run ${REINPLACE_CMD} from 12 to 4,
- add strip binary (warning from poudriere testport).
PR: 285938
Approved by: Timothy Beyer <beyert at cs.ucr.edu> (maintainer)
Co-authored-by: Herbert J. Skuhra <herbert at gojira.at>
