kstat(1) doesn't deal well with uninitialized named kstats
As it turns out, drivers can fail to initialize some named kstats (and apparently, some do – see https://smartos.org/bugview/OS-5723). kstat (1) currently deals very poorly with this condition, dumping random memory for those members. It obviously needs to be more resilient to these kstats.
Updated by Electric Monk over 5 years ago
- Status changed from New to Closed
commit 774814910cba5b65219849ca27b13b2fbe8127ee Author: Bryan Cantrill <firstname.lastname@example.org> Date: 2016-12-30T14:59:04.000Z 7701 kstat -j does not produce valid JSON 7702 kstat(1) doesn't deal well with uninitialized named kstats 7703 in some locales, kstat -j produces invalid JSON Reviewed by: Patrick Mooney <email@example.com> Reviewed by: Robert Mustacchi <firstname.lastname@example.org> Reviewed by: Toomas Soome <email@example.com> Reviewed by: Peter Tribble <firstname.lastname@example.org> Approved by: Richard Lowe <email@example.com>