tools/testing/selftests/ublk/test_generic_17.sh
Source file repositories/reference/linux-study-clean/tools/testing/selftests/ublk/test_generic_17.sh
File Facts
- System
- Linux kernel
- Corpus path
tools/testing/selftests/ublk/test_generic_17.sh- Extension
.sh- Size
- 1127 bytes
- Lines
- 36
- Domain
- Support Tooling And Documentation
- Bucket
- tools
- Inferred role
- Support Tooling And Documentation: tools
- Status
- atlas-only
Why This File Exists
Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
- Repository support layer: documentation, build tooling, samples, user-space helper tools, generated initramfs support, licenses, and validation utilities.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
#!/bin/bash
# SPDX-License-Identifier: GPL-2.0
. "$(cd "$(dirname "$0")" && pwd)"/test_common.sh
ERR_CODE=0
_prep_test "fault_inject" "teardown after incomplete recovery"
# First start and stop a ublk server with device configured for recovery
dev_id=$(_add_ublk_dev -t fault_inject -r 1)
_check_add_dev $TID $?
state=$(__ublk_kill_daemon "${dev_id}" "QUIESCED")
if [ "$state" != "QUIESCED" ]; then
echo "device isn't quiesced($state) after $action"
ERR_CODE=255
fi
# Then recover the device, but use --die_during_fetch to have the ublk
# server die while a queue has some (but not all) I/Os fetched
${UBLK_PROG} recover -n "${dev_id}" --foreground -t fault_inject --die_during_fetch 1
RECOVER_RES=$?
# 137 is the result when dying of SIGKILL
if (( RECOVER_RES != 137 )); then
echo "recover command exited with unexpected code ${RECOVER_RES}!"
ERR_CODE=255
fi
# Clean up the device. This can only succeed once teardown of the above
# exited ublk server completes. So if teardown never completes, we will
# time out here
_ublk_del_dev "${dev_id}"
_cleanup_test
_show_result $TID $ERR_CODE
Annotation
- Atlas domain: Support Tooling And Documentation / tools.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.