| 3dc18af5 | 12-Dec-2024 |
Stéphane Rochoy <stephane.rochoy@stormshield.eu> |
savecore: add a test for LOG_PERROR
Signed-off-by: Stéphane Rochoy <stephane.rochoy@stormshield.eu>
Reviewed by: markj, oshogbo MFC after: 2 weeks Pull Request: https://github.com/freebsd/freebsd-s
savecore: add a test for LOG_PERROR
Signed-off-by: Stéphane Rochoy <stephane.rochoy@stormshield.eu>
Reviewed by: markj, oshogbo MFC after: 2 weeks Pull Request: https://github.com/freebsd/freebsd-src/pull/1546
show more ...
|
| 0a5c04a8 | 18-Apr-2022 |
Mitchell Horne <mhorne@FreeBSD.org> |
savecore: add an option to save a live minidump
The new '-L' flag will cause savecore to invoke the new mem(4) kernel dump ioctl, taking a dump of the running system and writing the result to a temp
savecore: add an option to save a live minidump
The new '-L' flag will cause savecore to invoke the new mem(4) kernel dump ioctl, taking a dump of the running system and writing the result to a temporary file. Validation of the dump header is performed, similar to regular crash dumps, and the final result is written to livecore.X[.zst|.gz].
Also added is the '-Z' flag, which instructs the kernel to compress the livedump compressed with zstd, akin to the existing -z flag. This option has no effect in normal savecore(8) operation, but in theory could be extended to perform such compression while reading the dump from the dump device.
Encryption is unsupported for live dumps.
For example: 'savecore -Lz /var/crash' would create: /var/crash/livecore.0.gz
Reviewed by: markj MFC after: 2 weeks Sponsored by: Juniper Networks, Inc. Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D34347
show more ...
|
| cf02cf8d | 18-Apr-2022 |
Mitchell Horne <mhorne@FreeBSD.org> |
savecore: factor out info file handling
Move it to a separate function, allowing its reuse.
Reviewed by: markj MFC after: 3 days Sponsored by: Juniper Networks, Inc. Sponsored by: Klara, Inc. Diffe
savecore: factor out info file handling
Move it to a separate function, allowing its reuse.
Reviewed by: markj MFC after: 3 days Sponsored by: Juniper Networks, Inc. Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D34822
show more ...
|
| fafeb534 | 18-Apr-2022 |
Mitchell Horne <mhorne@FreeBSD.org> |
savecore: decrease filename buffer sizes
All files are now created relative to savedirfd, e.g. with openat(2). Therefore, we do not need character buffers to be PATH_MAX bytes long, just long enough
savecore: decrease filename buffer sizes
All files are now created relative to savedirfd, e.g. with openat(2). Therefore, we do not need character buffers to be PATH_MAX bytes long, just long enough to hold the complete filename. 32 bytes is long enough in all cases. These can be allocated on the stack.
While here, fix an error message that attempts to use an uninitialized infoname.
Reviewed by: markj MFC after: 3 days Sponsored by: Juniper Networks, Inc. Sponsored by: Klara, Inc. Differential Revision: https://reviews.freebsd.org/D34821
show more ...
|