nvmm_x86_vmx.c: fixes tprof stalls
the current implementation of nvmm nmi handling is
simple; just drops them. it interferes other nmi-using
components in the system, including tprof.
this commit makes nvmm try to dispatch nmis by itself.
while this is imperfect, it's good enough to give
tprof a chance to unmask LAPIC_LVT_PCINT.
i guess svm VMCB_EXITCODE_NMI needs something similar.
but i have no hardware. if someone wants to test a patch,
please let me know.
reproduce recipe:
1. run "tprof top" in a terminal. leave it running.
2. run an nvmm-based vm in another terminal.
3. observe some cpus in the "tprof top" stopped counting.
py-pdf: update to 6.9.1.
Security fix.
## Version 6.9.1, 2026-03-17
### Security (SEC)
- Improve performance and limit length of array-based content streams (#3686)
[Full Changelog](https://github.com/py-pdf/pypdf/compare/6.9.0...6.9.1)
## Version 6.9.0, 2026-03-15
### New Features (ENH)
- Expose /Perms verification result on Encryption object (#3672)
### Performance Improvements (PI)
- Fix O(n²) performance in NameObject read/write (#3679)
- Batch-parse all objects in ObjStm on first access (#3677)
[6 lines not shown]
Re-factor m68k FP exception handling:
- Move the FP exception stubs into the shared trap_subr.s. Remove as
many conditionals from the stubs as feasible, having separate stubs
for each case that needs to be handled. This doesn't really result
in any more (or duplicated) code, and makes it all a lot easier to
read.
- All platforms now call the new fpu_init() function, which is renamed
from fpu_probe(), and centralizes all of the FP-related initialization.
Platforms that don't need to probe for the FPU aren't forced to do so;
the probe only occurs if the fputype is FPU_UNKNOWN at the time fpu_init()
is called.
- Even on platforms that don't actually need to probe the FPU, make sure
the "nofault" code is present in trap() to do so; this is meant to reduce
diffs that need to be resolved later then the trap() function is re-factored.
- On Amiga and Atari, remove the bespoke vectab code and just use the shared
vec_init(). Additional cleanup is possible in this area.
(missed this file in larger commit)
Re-factor m68k FP exception handling:
- Move the FP exception stubs into the shared trap_subr.s. Remove as
many conditionals from the stubs as feasible, having separate stubs
for each case that needs to be handled. This doesn't really result
in any more (or duplicated) code, and makes it all a lot easier to
read.
- All platforms now call the new fpu_init() function, which is renamed
from fpu_probe(), and centralizes all of the FP-related initialization.
Platforms that don't need to probe for the FPU aren't forced to do so;
the probe only occurs if the fputype is FPU_UNKNOWN at the time fpu_init()
is called.
- Even on platforms that don't actually need to probe the FPU, make sure
the "nofault" code is present in trap() to do so; this is meant to reduce
diffs that need to be resolved later then the trap() function is re-factored.
- On Amiga and Atari, remove the bespoke vectab code and just use the shared
vec_init(). Additional cleanup is possible in this area.
ddb(4): improve markup readability for the list of commands
Add empty (single dot) lines around commands to make them more visible
in the man page source. Split long chains of Ij Kl Mn Op into
multiple source lines with Xo/Xc. While here mark up literal comma in
commands with Cm to make it more visible in the PostScript output.
www/chromium: update to 146.0.7680.153
* 146.0.7680.153
This update includes 26 security fixes. Please see the
Chrome Security Page for more information.
[TBD][475877320] Critical CVE-2026-4439: Out of bounds memory access
in WebGL. Reported by Goodluck on 2026-01-15
[TBD][485935305] Critical CVE-2026-4440: Out of bounds read and write
in WebGL. Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-02-20
[TBD][489381399] Critical CVE-2026-4441: Use after free in Base.
Reported by Google on 2026-03-03
[TBD][484751092] High CVE-2026-4442: Heap buffer overflow in CSS.
Reported by Syn4pse on 2026-02-16
[TBD][485292589] High CVE-2026-4443: Heap buffer overflow in WebAudio.
Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-02-18
[TBD][486349161] High CVE-2026-4444: Stack buffer overflow in WebRTC.
Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-02-21
[TBD][486421953] High CVE-2026-4445: Use after free in WebRTC.
Reported by c6eed09fc8b174b0f3eebedcceb1e792 on 2026-02-22
[40 lines not shown]
