www/rustfs: Update 1.0.4 to 1.0.5
Stop forcing fat LTO (WITHOUT_LTO), so the build uses the thin LTO from
upstream's release profile.
Make the data directory modifiable with the RUSTFS_DBDIR variable.
Mark BROKEN on i386: rustc runs out of memory.
Changelog: https://github.com/rustfs/rustfs/releases/tag/1.0.5
Reported by: Mickael Maillot <mmaillot at secuserve.com> (memory)
Reported by: pkg-fallout (i386)
Suggested by: otis (RUSTFS_DBDIR)
Reviewed by: otis
Approved by: jrm (mentor)
Differential Revision: https://reviews.freebsd.org/D61470
ipfw: fix off-by-one in the IP_FW_XADD rule count check
Restore the pre-4a77657cbc0 ">=" comparison, otherwise parse_rules_v1()
writes one rule_check_info beyond the allocated buffer.
Do the same in ip_fw_compat.c, which has a copy of the loop but is not
built at the moment.
stable/14 is not affected.
Reviewed by: ae
Fixes: 4a77657cbc0 ("ipfw: migrate ipfw to 32-bit size rule numbers")
MFC after: 1 week
MFC to: stable/15
Found with: Claude Code Opus 5.5
Differential Revision: https://reviews.freebsd.org/D61727
bhyve.8: mention VM nodes in /dev/vmm
Currently, VM nodes in /dev/vmm are only described in the
EXAMPLES section of bhyvectl.8. Add a FILES section to bhyve.8
to make this information easier to find.
Update the bhyvectl.8 example to say "Existing VMs"
instead of "Running VMs" as the VMs listed in /dev/vmm
are not necessarily running.
Update bhyvectl.8 to refer to vmm(4).
Reviewed by: ziaee
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D61623
tests/sys/pmc: Skip pmc_ss and getmsr_refusals without a hardware PMC
In a guest without a PMU, hwpmc(4) registers only the SOFT class, but
the "instructions" alias still resolves from the pmu-events tables, so
pmc_allocate() fails with EINVAL. pmc_ss_test checked only the alias
and getmsr_refusals required the allocation, so both failed in CI
instead of skipping.
Probe the allocation the tests make and skip if it fails, as
rdpmc_reads_own_counter already does.
PR: 300856 (https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=300856)
Reported by: ngie
Reviewed by: mhorne, ngie
Fixes: d546356523f3 ("tests/sys/pmc: add PERF, RDPMC, row, sampling and unload tests")
Sponsored by: Advanced Micro Devices, Inc.
Signed-off-by: Osvaldo Janeri Filho <ojanerif at amd.com>
Differential Revision: https://reviews.freebsd.org/D61689
hwpmc: keep AMD UMC counters from saturating
UMC counters saturate at 2^48 instead of wrapping, after about a day
and a half of memory clock cycles. Clear bit 47 on a read once it is
set and count the carries in the per-CPU overflow count of the PMC,
like the arm64 and armv7 drivers do for their 32-bit counters.
Reviewed by: mhorne
Sponsored by: Advanced Micro Devices, Inc.
Signed-off-by: Osvaldo Janeri Filho <ojanerif at amd.com>
Differential Revision: https://reviews.freebsd.org/D60771
bhyve.8: mention config files for VM parameters
Mention that virtual CPUs, memory and other options can be configured
with a configuration file, and refer to the -k option.
Reviewed by: ziaee
MFC after: 3 days
Sponsored by: The FreeBSD Foundation
Differential Revision: https://reviews.freebsd.org/D61718
top: fix off-by-one in screenbuf
There is a heap overflow for screenbuf originating from
the top import to the tree. The i_process()/u_process() functions
write a terminating NUL one byte past each screenbuf line slot
when the line fills the slot, which is a 1-byte heap overflow on the last slot.
The display_resize() function allocates screen_width bytes per line.
i_process() and u_process() cut lines to screen_width characters and
then stpcpy() them into the slot, which writes screen_width + 1 bytes.
line_update() can do the same with *old = ch. For inner slots,
the NUL lands in byte 0 of the next slot. This can corrupt the saved
contents used when updating the next line. For the last slot, it writes
one byte past the end of screenbuf.
Fix by allocating (screen_width + 1) bytes per line and updating the
line offsets to fit the terminating NUL.
Reviewed by: kib
[5 lines not shown]
top: fix off-by-one in screenbuf
There is a heap overflow for screenbuf originating from
the top import to the tree. The i_process()/u_process() functions
write a terminating NUL one byte past each screenbuf line slot
when the line fills the slot, which is a 1-byte heap overflow on the last slot.
The display_resize() function allocates screen_width bytes per line.
i_process() and u_process() cut lines to screen_width characters and
then stpcpy() them into the slot, which writes screen_width + 1 bytes.
line_update() can do the same with *old = ch. For inner slots,
the NUL lands in byte 0 of the next slot. This can corrupt the saved
contents used when updating the next line. For the last slot, it writes
one byte past the end of screenbuf.
Fix by allocating (screen_width + 1) bytes per line and updating the
line offsets to fit the terminating NUL.
Reviewed by: kib
[5 lines not shown]
www/opencloud: Fix build on i386
Fix the build failure on architectures where vendored nats-server's
server/pse package lacks non-cgo FreeBSD implementation (such as i386).
PR: 300899
pf: fix nat46 ICMP handling
When porting from OpenBSD I typo'd the variable where we store the ICMP
type, in the nat46 direction. The nat64 direction was correct. Fix this
so ICMP translation works for nat46.
Add a test case for this, as well as basic TCP and UDP cases because
nat46 was entirely untested.
PR: 300461
MFC after: 1 week
Submitted by: Charles Marshall <charles at wozi.com> (pf patch)
Sponsored by: Rubicon Communications, LLC ("Netgate")
pf: fix sctp normalisation cleanup
If we fail to allocate the dst scrub structure we should free the src
one too, but we passed src rather than src->scrub.
Reported by: llm-postcr
MFC after: 1 week
Sponsored by: Rubicon Communications, LLC ("Netgate")
pf tests: run the ioctl tests in their own vnet too
Fix the validation:settflags test, because using a NULL buffer succeeds
if there's no table to set tflags in. Create a table to fix the test.
Sponsored by: Rubicon Communications, LLC ("Netgate")
pf tests: test pfTablesTblCount in snmp_pf
This works fine on main, but not on stable/15 so add a test.
PR: 300818
MFC after: 3 days
Sponsored by: Rubicon Communications, LLC ("Netgate")
x11/nvidia-driver{-devel}, x11/nvidia-kmod{-devel}, x11/linux-nvidia-libs{-devel}, graphics/nvidia-drm*-kmod{-devel}, x11/nvidia-settings, x11/nvidia-xconfig: Update to 620.73.04
Update to latest Production Branch of drivers 620.73.04:
https://www.nvidia.com/en-us/drivers/details/285519/
Linux counterparts for x11/linux-nvidia-libs:
https://www.nvidia.com/en-us/drivers/details/285520/
As this version is newer than exisitng New Feature Branch (NFB)
of drivers, update -devel variants to the same version, too.
PR: 300897
Differential Revision: https://reviews.freebsd.org/D61744
pause fail point: affirm sleeping without a lock
The previous patch to fail_point_pause removed a lock wrapping a sleep.
INVARIANTS assertions require we affirm we are deliberately sleeping
without a lock or timeout via the PNOLOCK flag.
Reported by: netchild
Reviewed by: netchild
Fixes: 331613ddd8a5 ("Pause failpoint: replace mtx_sleep with tsleep")
Differential Revision: https://reviews.freebsd.org/D61730
acpi_pci_link: Handle IRQ values > 255
Some systems use a stub PCI link device for hardwired interrupts
instead of static _PRT entries. These link devices can use an IRQ >
255. The current driver was designed to handle PCI link devices on
x86 used for legacy INTx IRQs which were < 255. These changes handle
larger IRQ values while making a few tradeoffs.
- Expand most IRQ fields from 8 bits to 32-bits. The BIOS IRQ
(read from the PCIR_INTLINE config register which is an 8-bit register)
remains 8 bits.
- Add a wrapper API for managing interrupt weights and avoid tracking
weights for IRQs > 255 and instead report a constant weight of 0 for
IRQs > 255.
Approved by: re (cperciva)
PR: 300476
Reported by: Aviv Bakal <avivb at amazon.com>
[4 lines not shown]
acpi_pci_link: Ignore tunables with negative values
IRQ values are unsigned and negative values do not make sense. The
invalid IRQ value (255) is already ignored, so ignoring other invalid
values is consistent with that behavior.
Approved by: re (cperciva)
Reported by: cperciva
(cherry picked from commit 81dab94a5452f996a063bdba2103eda4aa32b3d1)
(cherry picked from commit 1b71cb09074be51a87a2eb84acb46ee77fceec45)
ctld: Fix namespace IDs for exported NVMe namespaces part 2
This is the same fix as in commit
9c8be6518e2e5f396055ecdab8098ce19c4b2218 just applied to another
method that also accepts namespace IDs. The original commit handled
configuration statements assigning a named LUN to a namespace. This
change handles anonymous namespaces configured within a controller
context.
Approved by: re (cperciva)
Fixes: 66b5296f1b29 ("ctld: Add support for NVMe over Fabrics")
Sponsored by: Chelsio Communications
(cherry picked from commit 9a99fa3932ddd794234becc6eab6519d56ae6947)
(cherry picked from commit 469ac5a9c05f21526f81cb34833bfff53b07a7d5)
ctld: Fix namespace IDs for exported NVMe namespaces
NVMe namespace IDs are 1-based, but CTL LUN IDs are 0-based. The
in-kernel NVMe ctl(4) target accounts for this by adding one to the
LUN ID to compute a namespace ID. ctld was attempting to handle this
by translating namespace IDs from config files to internal LUN IDs,
but it did this incorrectly resulting in the namespace configured for
as namespace N actually showing up as namespace N + 1.
Approved by: re (cperciva)
Fixes: 66b5296f1b29 ("ctld: Add support for NVMe over Fabrics")
Sponsored by: Chelsio Communications
(cherry picked from commit 9c8be6518e2e5f396055ecdab8098ce19c4b2218)
(cherry picked from commit 033c0cd3e89ba87f3d66ceea6436cf2a37148051)