geli tests: Work around a missing MFCThe test assumes commit 96950419f15510287080c557174e0d8409f06956, butthat was never MFCed to stable branches, resulting in a broken test.This is a direct com
geli tests: Work around a missing MFCThe test assumes commit 96950419f15510287080c557174e0d8409f06956, butthat was never MFCed to stable branches, resulting in a broken test.This is a direct commit to stable/14.
show more ...
ggate tests: Use unique ports among testsThis helps avoid failures when running tests in parallel.MFC after: 1 week(cherry picked from commit b5d3f8252fe8b74249ed49e87981d190c3ec3d05)
gnop tests: SerializeSome of these tests make use of test disk devices, but then they can'trun in parallel.MFC after: 2 weeks(cherry picked from commit dc8357de606aa65fc1c35a43d4a5f1d706164ddb)
geli: allocate a UMA pool earlierThe functions g_eli_init_uma and g_eli_fini_uma are used to tracethe number of devices in GELI. There is an issue where the g_eli_createfunction may fail before g
geli: allocate a UMA pool earlierThe functions g_eli_init_uma and g_eli_fini_uma are used to tracethe number of devices in GELI. There is an issue where the g_eli_createfunction may fail before g_eli_init_uma is called, howeverg_eli_fini_uma is still executed in the fail path. This canincorrectly decrease the device count to zero, potentially leading tothe UMA pool being freed. Accessing the device after the pool has beenfreed causes a system panic.This commit resolves the issue by ensuring devices count is increassedeariler.PR: 278828Reported by: Andre Albsmeier <[email protected]>Reviewed by: asomersMFC after: 3 daysDifferential Revision: https://reviews.freebsd.org/D45225(cherry picked from commit 4b3141f5d5373989598f9447ab5a9f87e2d1c9fb)
geli tests: Add a regression test for geli setkey -JMake sure that it can be used to change the passphrase of both attachedand detached providers.Approved by: re (kib)PR: 254966MFC after: 1 w
geli tests: Add a regression test for geli setkey -JMake sure that it can be used to change the passphrase of both attachedand detached providers.Approved by: re (kib)PR: 254966MFC after: 1 weekSponsored by: The FreeBSD Foundation(cherry picked from commit 2b7b09ac9675023869fddbae4911c9b674b1155a)
Remove $FreeBSD$: one-line sh patternRemove /^\s*#[#!]?\s*\$FreeBSD\$.*$\n/
Remove $FreeBSD$: one-line .c comment patternRemove /^/[*/]\s*\$FreeBSD\$.*\n/
Remove $FreeBSD$: one-line .h patternRemove /^\s*\*+\s*\$FreeBSD\$.*$\n/
ggate tests: Serialize
gmirror tests: Serialize
geli tests: Add a regression test for PR 271766This test case catches both of the bugs reported there.PR: 271766Reviewed by: impMFC after: 1 weekSponsored by: The FreeBSD FoundationDifferent
geli tests: Add a regression test for PR 271766This test case catches both of the bugs reported there.PR: 271766Reviewed by: impMFC after: 1 weekSponsored by: The FreeBSD FoundationDifferential Revision: https://reviews.freebsd.org/D40469
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSDThe SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catchup to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSDThe SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catchup to that fact and revert to their recommended match of BSD-2-Clause.Discussed with: pfgMFC After: 3 daysSponsored by: Netflix
Skip sys.geom.class.multipath.failloop.failloop if dtrace fails to runThis test case depends on dtrace and sometimes gets affected if dtracehas issues. Make it report skipped instead of failure w
Skip sys.geom.class.multipath.failloop.failloop if dtrace fails to runThis test case depends on dtrace and sometimes gets affected if dtracehas issues. Make it report skipped instead of failure when dtrace failsto run.Sponsored by: The FreeBSD Foundation
gmultipath tests: Re-enable the failloop test in CISponsored by: The FreeBSD Foundation
Temporarily skip sys.geom.class.multipath.failloop.failloop in CIThis test case uses `dtrace -c` but it has some issues at the moment sodisable it until dtrace fixed.From markj:This is the CTF
Temporarily skip sys.geom.class.multipath.failloop.failloop in CIThis test case uses `dtrace -c` but it has some issues at the moment sodisable it until dtrace fixed.From markj:This is the CTF type ID limit which has come up quite a few timeslately. It'll be fixed with the introduction of CTFv3.PR: 258763Sponsored by: The FreeBSD Foundation
gmultipath tests: Re-enable the failloop test in CIPR: 258763MFC after: 2 weeksSponsored by: The FreeBSD Foundation
gmultipath failloop test: Put the dtrace sanity checker in right placeCheck if dtrace excution is successful or not right after execution.Sponsored by: The FreeBSD Foundation
Fix typoReported by: swillsSponsored by: The FreeBSD Foundation
Temporarily skip sys.geom.class.multipath.failloop.failloop in CIThis test case uses `dtrace -c` but it has some issues at the momentWhile here, add a checker for dtrace executes successfully or
Temporarily skip sys.geom.class.multipath.failloop.failloop in CIThis test case uses `dtrace -c` but it has some issues at the momentWhile here, add a checker for dtrace executes successfully or not to providea more informative error message.PR: 258763Sponsored by: The FreeBSD Foundation
Add a regression test for ggatec remote code executionTests that ggatec appropriately handles unsupported BIO operations,rather than overflowing a buffer.Submitted by: Johannes Bruelltuete <joha
Add a regression test for ggatec remote code executionTests that ggatec appropriately handles unsupported BIO operations,rather than overflowing a buffer.Submitted by: Johannes Bruelltuete <[email protected]>PR: 213479Reviewed by: asomersDifferential Revision: https://reviews.freebsd.org/D31318
gconcat: Add some simple regression tests for the new append verbSponsored by: The FreeBSD Foundation
gmultipath: make physpath distinct from the underlying providers'zfsd uses a device's physical path attribute to automatically replace amissing ZFS disk when a blank disk is inserted into the same
gmultipath: make physpath distinct from the underlying providers'zfsd uses a device's physical path attribute to automatically replace amissing ZFS disk when a blank disk is inserted into the same physicalslot. Currently gmultipath passes through its underlying providers'physical path attribute. That may cause zfsd to replace a missinggmultipath provider with a newly arrived, single-path disk. That wouldbe bad.This commit fixes that problem by simply appending "/mp" to theunderlying providers' physical path, in a manner similar to what gelialready does.Sponsored by: AxcientMFC after: 3 weeksDifferential Revision: https://reviews.freebsd.org/D29941
build: provide a default WARNS for all in-tree buildsThe current default is provided in various Makefile.inc in some top-leveldirectories and covers a good portion of the tree, but doesn't cover p
build: provide a default WARNS for all in-tree buildsThe current default is provided in various Makefile.inc in some top-leveldirectories and covers a good portion of the tree, but doesn't cover partsof the build a little deeper (e.g. libcasper).Provide a default in src.sys.mk and set WARNS to it in bsd.sys.mk if thatvariable is defined. This lets us relatively cleanly provide a default WARNSno matter where you're building in the src tree without breaking thingsoutside of the tree.Crunchgen has been updated as a bootstrap tool to work on this changebecause it needs r365605 at a minimum to succeed. The cleanup necessary tosuccessfully walk over this change on WITHOUT_CLEAN builds has been added.There is a supplemental project to this to list all of the warnings that areencountered when the environment has WARNS=6 NO_WERROR=yes:https://warns.kevans.dev -- this project will hopefully eventually go awayin favor of CI doing a much better job than it.Reviewed by: emaste, brooks, ngie (all earlier version)Reviewed by: emaste, arichardson (depend-cleanup.sh change)Differential Revision: https://reviews.freebsd.org/D26455
Limit gmirror failpoint tests to the test workerThis avoids injecting errors into the test system's mirrors.gnop seems like a good solution here but it injects errors at the wrongplace vs where
Limit gmirror failpoint tests to the test workerThis avoids injecting errors into the test system's mirrors.gnop seems like a good solution here but it injects errors at the wrongplace vs where these tests expect and does not support a 'max global count'like the failpoints do with 'n*' syntax.Reviewed by: cem, vangyzenSponsored by: Dell EMC Isilon
Fix sys.geom.class.eli.onetime_test.onetime after r363402PR: 247954X-MFC with: r363402Sponsored by: The FreeBSD Foundation
12345