Page MenuHomeFreeBSD

mem(4): allow configuring livedump via ioctl
AbandonedPublic

Authored by mhorne on Feb 8 2022, 8:14 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sep 19 2024, 6:30 PM
Unknown Object (File)
Sep 19 2024, 5:15 AM
Unknown Object (File)
Sep 19 2024, 2:10 AM
Unknown Object (File)
Sep 18 2024, 12:49 AM
Unknown Object (File)
Sep 17 2024, 11:54 AM
Unknown Object (File)
Sep 16 2024, 4:17 PM
Unknown Object (File)
Sep 4 2024, 5:53 PM
Unknown Object (File)
Sep 3 2024, 10:44 PM

Details

Reviewers
kib
markj
Summary

This should implement the functionality covered by D34069.

Test Plan

Tested that dumpon -z|Z /dev/mem succeeds and results in a compressed dump.

Need to test the encryption paths.

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Passed
Unit
No Test Coverage
Build Status
Buildable 44343
Build 41231: arc lint + arc unit

Event Timeline

mhorne requested review of this revision.Feb 8 2022, 8:14 PM
mhorne edited the test plan for this revision. (Show Details)
mhorne added reviewers: kib, markj.

I'm sorry for the delay.

sys/dev/mem/memdev.c
160

Why exactly do we have separate ioctls for configuring and invoking a livedump? Is it only so that we can have dumpon perform configuration and have savecore actually retrieve the dump? If so I'd really prefer to have savecore do everything, but I see it's a bit inconvenient to have to shoehorn everything there...

OTOH I still can't see a reason we'd want the kernel to perform encryption and compression rather than doing it in userspace. Did we discuss this somewhere already?

Is this review obsolete now?

Is this review obsolete now?

Yep, along with D34069.