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
show more ...
Clarify when GEOM utilities exit with success or failure.Historically, GEOM utilities (gpart(8), gstripe(8), gmirror(8),etc) used the gctl_error() routine to report errors. If they calledgctl_err
Clarify when GEOM utilities exit with success or failure.Historically, GEOM utilities (gpart(8), gstripe(8), gmirror(8),etc) used the gctl_error() routine to report errors. If they calledgctl_error() they would exit with EXIT_FAILURE, otherwise they wouldreturn with EXIT_SUCCESS. If they used gctl_error() to output aninformational message, for example when run with the -v (verbose)option, they would mistakenly exit with EXIT_FAILURE. A furtherlimitation of the gctl_error() function was that it could only becalled once. Messages from any additional calls to gctl_error()would be silently discarded.To resolve these problems a new function, gctl_msg() has been added.It can be called multiple times to output multiple messages. Italso has an additional errno argument which should be zero if it isan informational message or an errno value (EINVAL, EBUSY, etc) ifit is an error. When done the gctl_post_messages() function shouldbe called to indicate that all messages have been posted. If anyof the messages had a non-zero errno, the utility will EXIT_FAILURE.If only informational messages (with zero errno) were posted, theutility will EXIT_SUCCESS.Tested by: Peter HolmPR: 265184MFC after: 1 week
kerneldump: remove physical argument from d_dumperThe physical address argument is essentially ignored by every dumpermethod. In addition, the dump routines don't actually pass a realaddress; eve
kerneldump: remove physical argument from d_dumperThe physical address argument is essentially ignored by every dumpermethod. In addition, the dump routines don't actually pass a realaddress; every call to dump_append() passes a value of zero forphysical.Reviewed by: markjMFC after: 2 weeksDifferential Revision: https://reviews.freebsd.org/D35173
Avoid dereferencing a possibly null pointer.Reported by: CoverityCID: 1475868
Add casts to printf statements to keep armv6, armv7, and powerpcbuilds happy.
Create a new GEOM utility, gunion(8).The gunion(8) utility is used to track changes to a read-only disk ona writable disk. Logically, a writable disk is placed over a read-onlydisk. Write request
Create a new GEOM utility, gunion(8).The gunion(8) utility is used to track changes to a read-only disk ona writable disk. Logically, a writable disk is placed over a read-onlydisk. Write requests are intercepted and stored on the writabledisk. Read requests are first checked to see if they have beenwritten on the top (writable disk) and if found are returned. Ifthey have not been written on the top disk, then they are read fromthe lower disk.The gunion(8) utility can be especially useful if you have a largedisk with a corrupted filesystem that you are unsure of how torepair. You can use gunion(8) to place another disk over the corrupteddisk and then attempt to repair the filesystem. If the repair fails,you can revert all the changes in the upper disk and be back to theunchanged state of the lower disk thus allowing you to try anotherapproach to repairing it. If the repair is successful you can commitall the writes recorded on the top disk to the lower disk.Another use of the gunion(8) utility is to try out upgrades to yoursystem. Place the upper disk over the disk holding your filesystemthat is to be upgraded and then run the upgrade on it. If it works,commit it; if it fails, revert the upgrade.Further details can be found in the gunion(8) manual page.Reviewed by: Chuck Silvers, kib (earlier version)tested by: Peter HolmDifferential Revision: https://reviews.freebsd.org/D32697