aboutsummaryrefslogtreecommitdiff
path: root/lib/libclang_rt/asan/Makefile
diff options
context:
space:
mode:
authorAndriy Gapon <avg@FreeBSD.org>2021-11-27 18:49:08 +0000
committerAndriy Gapon <avg@FreeBSD.org>2022-01-26 09:25:31 +0000
commit1abf1e8c6b13f50eed08fef6fb1ade280894f1e4 (patch)
treee406043cecf29a4493b1f0db535b9cae4e92d9bf /lib/libclang_rt/asan/Makefile
parent94ff1d9cc8ffc2b88caafed35168a258f969915c (diff)
downloadsrc-1abf1e8c6b13f50eed08fef6fb1ade280894f1e4.tar.gz
src-1abf1e8c6b13f50eed08fef6fb1ade280894f1e4.zip
cam_get_device: resolve path links before parsing device name
The CAM subsystem uses bus:taget:lun tuple to address peripherals. But for convenience many userland programs such as camcontrol accept devices names such as da0. There is a libcam function, cam_open_device, to support that. It first calls cam_get_device() to parse the device name as a driver name and a unit (and handle some special device name prefixes) and then uses cam_lookup_pass() to find a matching pass device. This change extends cam_get_device() to apply realpath(3) to the device name before parsing it. This will allow to use tools such as camcontrol and smartctl with symbolic links that could be friendlier (more distinguished) names for devices. MFC after: 3 weeks Relnotes: maybe
Diffstat (limited to 'lib/libclang_rt/asan/Makefile')
0 files changed, 0 insertions, 0 deletions