sys/tmpfs: use getnanotime() like FFS and MFS
Editing files on tmpfs uses nanotime() to update mtime, and touch uses
utimensat(UTIME_NOW) which uses getnanotime() which is cached and which
can be smaller.
So, sed ... A && touch B leads to mtime(A) > mtime(B) which isn't excted.
"Yep" deraadt@
p5-XML-Parser: update to 2.54.
2.54 2026-03-27 (by Todd Rinaldo)
Fixes:
- PR #196 Plug XS memory leaks on error paths in Expat.xs
(externalEntityRef, parse_stream, ParserCreate)
- PR #204 Add defensive NULL checks in Expat.xs to prevent crashes
on memory exhaustion and undefined behavior on short input lines
- PR #203 Add explicit package main after inline package declarations
in test files to clarify scope
Improvements:
- PR #207 GH #205 Add GitHub Actions workflow to auto-create GitHub
Releases on tag push, enabling downstream notification via
GitHub's release watch
- PR #209 Update AUTHORS POD in Parser.pm and Expat.pm to reflect
full maintainer history
- PR #210 Add CI badge to POD via =for markdown directive so it
[42 lines not shown]
amd64 sendsig(): explicitly copy registers from trapframe to ucontext
With the IDT event delivery, previously reserved fields in tf_cs and
tf_ss are guaranteed to be zero. With FRED, these fields are not zero,
which affects the values copied to userspace.
Reviewed by: markj
Sponsored by: The FreeBSD Foundation
MFC after: 1 week
Differential revision: https://reviews.freebsd.org/D56141
py-matplotlib: disable link-time optimization for ports-gcc, ok daniel
The combination of a modern compiler with antique binutils isn't expected
in the ecosystem. On sparc64, LTO is enabled because the ports-gcc supports
it which then emits "e" sections which are to be excluded from executables
and shared objects by the link editor, such as
.section .gnu.lto_.profile.5712db33fb59d8ee,"e",@progbits
As reported by kmos, Fred Flintstone's gas trips over these with
Fatal error: unrecognized .section attribute: want a,w,x,M,S,G,T
mvc: a bit of spring cleaning for setActionHook(), result is never used and throwing a UserException is preferred in cases where can't pin a message to a field. closes https://github.com/opnsense/core/pull/10046
