This series contains a couple of fixes:
1/ Check the kernel policy for onlining blocks. If that is set to
'online', and if daxctl is passed --no-online or is onlining to
ZONE_MOVABLE (default), then fail the reconfigure command as we know
we can't satisfy that ask. (Prior to these patches, the reconfigure
would succeed, and we'd print a warning after the fact, which may
result in a surprising experience).
2/ For ndctl disable-namespace (and destroy-namespace), fail the
operation if the dax device is active as system-ram.
Additionally, augment the daxctl-devices.sh unit test to test for both
of these conditions and the expected (fixed) behavior in both cases.
Vishal Verma (3):
daxctl: fail reconfigure-device based on kernel onlining policy
libdaxctl: add an API to check if a device is active
libndctl: check for active system-ram before disabling daxctl devices
.../daxctl/daxctl-reconfigure-device.txt | 12 ++++-
daxctl/lib/libdaxctl-private.h | 1 +
daxctl/lib/libdaxctl.c | 31 +++++++++++
ndctl/lib/libndctl.c | 25 ++++++++-
daxctl/libdaxctl.h | 2 +
daxctl/device.c | 10 ++++
daxctl/lib/libdaxctl.sym | 6 +++
test/daxctl-devices.sh | 52 +++++++++++++++++++
8 files changed, 137 insertions(+), 2 deletions(-)