Red Hat Bugzilla – Bug 840708
misleading (typo) print for "max_report_luns"
Last modified: 2015-07-22 03:58:25 EDT
Description of problem: Got email from Rob Evers when checking max_luns support with him, he found a bug for miss leading print about max_report_luns. Quote: ==== There is a misleading print that is related: From num_luns = (length / sizeof(struct scsi_lun)); if (num_luns > max_scsi_report_luns) { printk(KERN_WARNING "scsi: On %s only %d (max_scsi_report_luns)" " of %d luns reported, try increasing" " max_scsi_report_luns.\n", devname, max_scsi_report_luns, num_luns); num_luns = max_scsi_report_luns; } ==== Version-Release number of selected component (if applicable): quote: "Looks like a bug in rhel6/rhel7/upstream as well." How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Incorrect kernel message for max_support_luns. Expected results: correct info. Additional info:
(In reply to comment #0) > Description of problem: > Got email from Rob Evers when checking max_luns support with him, he found a > bug for miss leading print about max_report_luns. Quote: > ==== > There is a misleading print that is related: > > From > > num_luns = (length / sizeof(struct scsi_lun)); > if (num_luns > max_scsi_report_luns) { > printk(KERN_WARNING "scsi: On %s only %d (max_scsi_report_luns)" > " of %d luns reported, try increasing" > " max_scsi_report_luns.\n", devname, > max_scsi_report_luns, num_luns); > num_luns = max_scsi_report_luns; > } > ==== > looks like print above should be: "try increasing max_report_luns" above.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
Created attachment 980745 [details] Proposed patch v1 Proposed patch v1
Patch(es) available on kernel-2.6.32-529.el6
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1272.html