diff options
author | Uday Shankar <ushankar@purestorage.com> | 2024-10-07 12:24:14 -0600 |
---|---|---|
committer | Jens Axboe <axboe@kernel.dk> | 2024-10-22 08:16:37 -0600 |
commit | d00c0ea17955d2fde9ef7ebca480f4c73a594650 (patch) | |
tree | 9c3e93c6ff4c5fcfcdcf87dae8733f6e2a033f59 /tools/perf/scripts/python | |
parent | 110234da18ab482f6f583d28eff26b9569bf5622 (diff) |
ublk: check recovery flags for validity
Setting UBLK_F_USER_RECOVERY_REISSUE without also setting
UBLK_F_USER_RECOVERY is currently silently equivalent to not setting any
recovery flags at all, even though that's obviously not intended. Check
for this case and fail add_dev (with a paranoid warning to aid debugging
any program which might rely on the old behavior) with EINVAL if it is
detected.
Signed-off-by: Uday Shankar <ushankar@purestorage.com>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Link: https://lore.kernel.org/r/20241007182419.3263186-2-ushankar@purestorage.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions