| commit | fa99d9cd9cbc6aca3245afcfe321b8226985597d | |
| author | Rob Norris <rob.norris@klarasystems.com> | |
| Fri, 10 May 2024 03:54:08 +0000 (10 13:54 +1000) | ||
| committer | Brian Behlendorf <behlendorf1@llnl.gov> | |
| Tue, 14 May 2024 16:48:56 +0000 (14 09:48 -0700) | ||
| tree | 44f15fc371b83e049944232eb81864e97c200427 | treesnapshot (tar.gz zip) |
| parent | 1ea8c59441cd215d4f45cbe839cbfe51c6e32068 | commitdiff |
zfs_dbgmsg_print: make FreeBSD and Linux consistent
FreeBSD was using fprintf(), which might not be signal-safe. Meanwhile,
Linux's locking did not cover the header output. This two quirks are
unrelated, but both have the same response: be like the other one. So
with this commit, both functions are the same except for the names of
their lock and list variables.
Sponsored-by: Klara, Inc.
Sponsored-by: Wasabi Technology, Inc.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Rob Norris <rob.norris@klarasystems.com>
Closes #16181
FreeBSD was using fprintf(), which might not be signal-safe. Meanwhile,
Linux's locking did not cover the header output. This two quirks are
unrelated, but both have the same response: be like the other one. So
with this commit, both functions are the same except for the names of
their lock and list variables.
Sponsored-by: Klara, Inc.
Sponsored-by: Wasabi Technology, Inc.
Reviewed-by: Brian Behlendorf <behlendorf1@llnl.gov>
Signed-off-by: Rob Norris <rob.norris@klarasystems.com>
Closes #16181
| module/os/freebsd/zfs/zfs_debug.c | diffblobblamehistory | |
| module/os/linux/zfs/zfs_debug.c | diffblobblamehistory |