FreeBSD source tree https://cgit-dev.freebsd.org/src-test/atom?h=main 2020-12-03T11:59:40Z 2020-12-03T11:59:40Z Andriy Gapon avg@FreeBSD.org 2020-12-03T11:59:40Z urn:sha1:b946eede043435cad44e6fec9e553bdf1760c5b8 Note that the public documentation on dtrace.org fails to mention %T and incorrectly documents %Y. The latter actually uses format "%Y %b %e %T" where %b is always in C locale. Discussed with: markj MFC after: 1 month Sponsored by: Panzura 2020-11-20T17:26:02Z Jonathan T. Looney jtl@FreeBSD.org 2020-11-20T17:26:02Z urn:sha1:96fbe51956c9df8bdb8317413b1c487b14e4ee68 encode 0-length (i.e. "") structure and union member names as offset 0. This ensures that we don't confuse other parts of the CTF code which expect this encoding. This resolves a Dtrace error resolving members of anonymous structs/unions within the (struct mbuf) type which some users were seeing after r366908. While here, update the code in ctf_add_generic() to encode 0-length type names as offset 0. Reviewed by: markj MFC after: 2 weeks Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D27246 2020-11-17T14:07:27Z Jonathan T. Looney jtl@FreeBSD.org 2020-11-17T14:07:27Z urn:sha1:3cbb4cc200f8a0ad7ed08233425ea54524a21f1c always copy intrinsic data types before copying bitfields which are based on those types. This ensures the type ordering in the destination CTF container matches the assumption made elsewhere in the CTF code that instrinsic data types will always appear before bitfields based on those types. This resolves the following error message some users have seen after r366908: "/usr/lib/dtrace/ipfw.d", line 121: failed to copy type of 'ip6p': Conflicting type is already defined Reviewed by: markj Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D27213 2020-11-16T17:20:35Z Brooks Davis brooks@FreeBSD.org 2020-11-16T17:20:35Z urn:sha1:73734d6eb1431928a4e2766c64b84d8845aea4ed Without this "SUBDIR.${MK_TESTS}=tests" would always expand to "SUBDIR.=tests" resulting in the tests not being built. Sponsored by: DARPA 2020-10-01T01:10:51Z Kyle Evans kevans@FreeBSD.org 2020-10-01T01:10:51Z urn:sha1:7cc42f6d25ef2e19059d088fa7d4853fe9afefb5 Repeating the default WARNS here makes it slightly more difficult to experiment with default WARNS changes, e.g. if we did something absolutely bananas and introduced a WARNS=7 and wanted to try lifting the default to that. Drop most of them; there is one in the blake2 kernel module, but I suspect it should be dropped -- the default WARNS in the rest of the build doesn't currently apply to kernel modules, and I haven't put too much thought into whether it makes sense to make it so. 2020-09-21T09:01:10Z Toomas Soome tsoome@FreeBSD.org 2020-09-21T09:01:10Z urn:sha1:e307eb94ae520d98dc1d346a0c53667a41beab5d bootonce feature is temporary, one time boot, activated by "bectl activate -t BE", "bectl activate -T BE" will reset the bootonce flag. By default, the bootonce setting is reset on attempt to boot and the next boot will use previously active BE. By setting zfs_bootonce_activate="YES" in rc.conf, the bootonce BE will be set permanently active. bootonce dataset name is recorded in boot pool labels, bootenv area. in case of nextboot, the nextboot_enable boolean variable is recorded in freebsd:nvstore nvlist, also stored in boot pool label bootenv area. On boot, the loader will process /boot/nextboot.conf if nextboot_enable is "YES", and will set nextboot_enable to "NO", preventing /boot/nextboot.conf processing on next boot. bootonce and nextboot features are usable in both UEFI and BIOS boot. To use bootonce/nextboot features, the boot loader needs to be updated on disk; if loader.efi is stored on ESP, then ESP needs to be updated and for BIOS boot, stage2 (zfsboot or gptzfsboot) needs to be updated (gpart or other tools). At this time, only lua loader is updated. Sponsored by: Netflix, Klara Inc. Differential Revision: https://reviews.freebsd.org/D25512 2020-09-19T16:15:22Z Mark Johnston markj@FreeBSD.org 2020-09-19T16:15:22Z urn:sha1:c6989859ae9388eeb46a24fe88f9b8d07101c710 Reported by: Jenkins MFC after: 1 week 2020-09-19T12:08:16Z Alex Richardson arichardson@FreeBSD.org 2020-09-19T12:08:16Z urn:sha1:79e02149fcb480c95cfda65e2145ed021dfde5a6 This required surprisingly few build system changes and only two changes to the openZFS compat headers which have been upstreamed as https://github.com/openzfs/zfs/pull/10863 Reviewed By: #zfs, freqlabs Differential Revision: https://reviews.freebsd.org/D26193 2020-09-18T23:21:24Z Matt Macy mmacy@FreeBSD.org 2020-09-18T23:21:24Z urn:sha1:2c48331d28f16c0efce5a72a81e7d71668c4a158 - Fixes divide by zero for unusual hz - remove cryptodev dependency 2020-09-14T16:12:28Z Andrew Turner andrew@FreeBSD.org 2020-09-14T16:12:28Z urn:sha1:2a6803de1cdbc7e34dfe4dc185a2dd98b9a787fb Use MACHINE_CPUARCH with arm64 (aarch64) when we build code that could run on any 64-bit Arm instruction set. This will simplify checks in downstream consumers targeting prototype instruction sets. The only place we check for MACHINE_ARCH == aarch64 is when building the device tree blobs. As these are targeting current generation ISAs. Sponsored by: Innovate UK Differential Revision: https://reviews.freebsd.org/D26370