summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/bin/stackcollapse-record
diff options
context:
space:
mode:
authorMartin Wilck <mwilck@suse.com>2022-01-27 15:13:51 +0100
committerMartin K. Petersen <martin.petersen@oracle.com>2022-02-07 23:06:13 -0500
commit7cddf7e8d1e88603d0e86997259fdec98da6f70a (patch)
treed351f665c539a1ef258210fb5f886f50d17d992d /tools/perf/scripts/python/bin/stackcollapse-record
parentd1d87c33f47dc69f948d51dcfed344e34c75c406 (diff)
downloadlinux-7cddf7e8d1e88603d0e86997259fdec98da6f70a.tar.gz
linux-7cddf7e8d1e88603d0e86997259fdec98da6f70a.zip
scsi: core: Make "access_state" sysfs attribute always visible
If a SCSI device handler module is loaded after some SCSI devices have already been probed (e.g. via request_module() by dm-multipath), the "access_state" and "preferred_path" sysfs attributes remain invisible for these devices, although the handler is attached and live. The reason is that the visibility is only checked when the sysfs attribute group is first created. This results in an inconsistent user experience depending on the load order of SCSI low-level drivers vs. device handler modules. This patch changes user space API: attempting to read the "access_state" or "preferred_path" attributes will now result in -EINVAL rather than -ENODEV for devices that have no device handler, and tests for the existence of these attributes will have a different result. Link: https://lore.kernel.org/r/20220127141351.30706-1-mwilck@suse.com Reviewed-by: Christoph Hellwig <hch@lst.de> Reviewed-by: Hannes Reinecke <hare@suse.de> Signed-off-by: Martin Wilck <mwilck@suse.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'tools/perf/scripts/python/bin/stackcollapse-record')
0 files changed, 0 insertions, 0 deletions