CONFIG_SCSI_WAIT_SCAN configure error
http://bugzilla.kernel.org/show_bug.cgi?id=9769
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected], | |[email protected]
------- Comment #1 from [email protected] 2008-02-07 23:28 ------- This appears to be a dependency, but these are not dependent defines. CONFIG_SCSI_SCAN_ASYNC defines the default scan type, which can be overridden by the module parameter.
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=9769
------- Comment #2 from [email protected] 2008-02-08 07:01 -------
Reply-To: [email protected]
Quoted 13 lines · On Thu, 2008-02-07 at 23:28 -0800, [email protected] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=9769
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------CC| |[email protected], | |[email protected]
Quoted 4 lines
------- Comment #1 from [email protected] 2008-02-07 23:28 ------- This appears to be a dependency, but these are not dependent defines.
CONFIG_SCSI_SCAN_ASYNCdefines the default scan type, which can be overridden by the module parameter.
Yes, this is exactly right. CONFIG_SCSI_ASYNC_SCAN doesn't affect the code (async scan is always included) it affects the boot default. In either case, with the correct kernel parameters, you can boot either sync or async scanning.
James
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=9769
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |REJECTED
Resolution| |INVALID------- Comment #3 from [email protected] 2008-02-08 07:56 ------- Thanks, closing the bug.
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=9769
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REJECTED |REOPENED
Resolution|INVALID |------- Comment #4 from [email protected] 2008-02-18 05:16 ------- This is NOT an invalid bug!
In all previous kernels, if
# CONFIG_SCSI_SCAN_ASYNC is not set
thenCONFIG_SCSI_WAIT_SCAN=m
does not even appear in the .config file, and the module scsi_wait_scan.ko is not built.
The module is NOT built, only in 2.6.24 is it getting built regardless.
For 2.6.23.x and all earlier kernels, the module is not built.
Ditto when doing 'make menuconfig', in all previous kernels, if CONFIG_SCSI_SCAN_ASYNC is turned off then the option to build the module is not even offered. However in 2.6.24 it continues to be offered regardless.
So, I repeat, this is a BUG!
Or, if you have made a change that requires the module to be built regardless, can you please explain why it is needed in the case of '.CONFIG_SCSI_SCAN_ASYNC is not set' and why this change from all previous kernels.
Barry Kauler
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=9769
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected] Status|REOPENED |REJECTED Resolution| |INVALID
------- Comment #5 from [email protected] 2008-02-18 06:19 ------- Sorry, it is an invalid bug. This has been discussed a few times on linux-scsi. If you have any SCSI driver built as a module, you (or the distro you are running) may need it. We can't tell in Kconfig -- and you might choose to build another driver as a module later. Or out of tree.
If you're sure you don't need it, then don't run 'make modules_install'. It's about 2500 bytes ... why waste so much energy being angry?
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
http://bugzilla.kernel.org/show_bug.cgi?id=9769
Stefan Richter <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]. | |de Regression|--- |No
--- Comment #6 from Stefan Richter <[email protected]> 2009-06-17 10:21:20 ---
Quoted 1 line
why waste so much energy being angry?
The waste and anger is because the implementation is so strange, compared to how kernel modules are normally used, and because it is unexplained except in list archives.
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.
http://bugzilla.kernel.org/show_bug.cgi?id=9769
Stefan Richter <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REJECTED |RESOLVED
Resolution|INVALID |DUPLICATE--- Comment #7 from Stefan Richter <[email protected]> 2009-06-17 10:21:35 ---
*** This bug has been marked as a duplicate of bug 8763 ***
Signature · 3 lines
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug.