summaryrefslogtreecommitdiff
path: root/scripts/gdb/linux/utils.py
diff options
context:
space:
mode:
authorAdrian Hunter <adrian.hunter@intel.com>2025-10-24 11:59:18 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2025-11-13 23:37:48 +0300
commitdf96dbe1af7f6591c09f862f1226d3619b07e1b6 (patch)
tree1277817832329012d679eae93417aeac414be461 /scripts/gdb/linux/utils.py
parentdbd6c27d45b9a60609026b36266a17a560ae6318 (diff)
downloadlinux-df96dbe1af7f6591c09f862f1226d3619b07e1b6.tar.xz
scsi: ufs: core: Fix invalid probe error return value
commit a2b32bc1d9e359a9f90d0de6af16699facb10935 upstream. After DME Link Startup, the error return value is set to the MIPI UniPro GenericErrorCode which can be 0 (SUCCESS) or 1 (FAILURE). Upon failure during driver probe, the error code 1 is propagated back to the driver probe function which must return a negative value to indicate an error, but 1 is not negative, so the probe is considered to be successful even though it failed. Subsequently, removing the driver results in an oops because it is not in a valid state. This happens because none of the callers of ufshcd_init() expect a non-negative error code. Fix the return value and documentation to match actual usage. Fixes: 69f5eb78d4b0 ("scsi: ufs: core: Move the ufshcd_device_init(hba, true) call") Cc: stable@vger.kernel.org Signed-off-by: Adrian Hunter <adrian.hunter@intel.com> Reviewed-by: Bart Van Assche <bvanassche@acm.org> Link: https://patch.msgid.link/20251024085918.31825-5-adrian.hunter@intel.com Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions