Message ID | 24dc30ca-b558-fb6c-d478-967dbfa887c4@infradead.org (mailing list archive) |
---|---|
State | Superseded |
Headers | show |
Series | [v2] target: fix tcm_loop build errors when SCSI=m | expand |
On Mon, 2018-08-06 at 16:20 -0700, Randy Dunlap wrote: > Fixes: 3703b2c5d041 ("[SCSI] tcm_loop: Add multi-fabric Linux/SCSI LLD > fabric module") From drivers/target/Kconfig on Linus' master branch: menuconfig TARGET_CORE tristate "Generic Target Core Mod (TCM) and ConfigFS Infrastructure" depends on SCSI && BLOCK if TARGET_CORE [ ... ] source "drivers/target/loopback/Kconfig" endif In other words, the loopback driver already depends on SCSI. So I doubt that this is a longstanding issue. Did you encounter this with Linus' master branch or rather with linux-next? Thanks, Bart.
On 08/06/2018 04:26 PM, Bart Van Assche wrote: > On Mon, 2018-08-06 at 16:20 -0700, Randy Dunlap wrote: >> Fixes: 3703b2c5d041 ("[SCSI] tcm_loop: Add multi-fabric Linux/SCSI LLD >> fabric module") > > From drivers/target/Kconfig on Linus' master branch: > > menuconfig TARGET_CORE > tristate "Generic Target Core Mod (TCM) and ConfigFS Infrastructure" > depends on SCSI && BLOCK > > if TARGET_CORE > [ ... ] > source "drivers/target/loopback/Kconfig" > endif > > In other words, the loopback driver already depends on SCSI. So I doubt that > this is a longstanding issue. Did you encounter this with Linus' master branch > or rather with linux-next? Darn. Thanks for the info. I encountered it in linux-next. I'll dig deeper.
On Mon, 2018-08-06 at 16:29 -0700, Randy Dunlap wrote: > On 08/06/2018 04:26 PM, Bart Van Assche wrote: > > On Mon, 2018-08-06 at 16:20 -0700, Randy Dunlap wrote: > > > Fixes: 3703b2c5d041 ("[SCSI] tcm_loop: Add multi-fabric Linux/SCSI LLD > > > fabric module") > > > > From drivers/target/Kconfig on Linus' master branch: > > > > menuconfig TARGET_CORE > > tristate "Generic Target Core Mod (TCM) and ConfigFS Infrastructure" > > depends on SCSI && BLOCK > > > > if TARGET_CORE > > [ ... ] > > source "drivers/target/loopback/Kconfig" > > endif > > > > In other words, the loopback driver already depends on SCSI. So I doubt that > > this is a longstanding issue. Did you encounter this with Linus' master branch > > or rather with linux-next? > > Darn. Thanks for the info. > > I encountered it in linux-next. I'll dig deeper. This patch series may be what you are looking for: "[PATCH v2 0/9] block: Consolidate scsi sense buffer usage" (https://lkml.org/lkml/2018/7/31/829). Bart.
On 08/06/2018 04:29 PM, Randy Dunlap wrote: > On 08/06/2018 04:26 PM, Bart Van Assche wrote: >> On Mon, 2018-08-06 at 16:20 -0700, Randy Dunlap wrote: >>> Fixes: 3703b2c5d041 ("[SCSI] tcm_loop: Add multi-fabric Linux/SCSI LLD >>> fabric module") >> >> From drivers/target/Kconfig on Linus' master branch: >> >> menuconfig TARGET_CORE >> tristate "Generic Target Core Mod (TCM) and ConfigFS Infrastructure" >> depends on SCSI && BLOCK >> >> if TARGET_CORE >> [ ... ] >> source "drivers/target/loopback/Kconfig" >> endif >> >> In other words, the loopback driver already depends on SCSI. So I doubt that >> this is a longstanding issue. Did you encounter this with Linus' master branch >> or rather with linux-next? > > Darn. Thanks for the info. > > I encountered it in linux-next. I'll dig deeper. For TARGET_CORE, the depends on SCSI has been removed in linux-next. That allows the kconfig to go sideways.
--- linux-next-20180806.orig/drivers/target/loopback/Kconfig +++ linux-next-20180806/drivers/target/loopback/Kconfig @@ -1,5 +1,6 @@ config LOOPBACK_TARGET tristate "TCM Virtual SAS target and Linux/SCSI LDD fabric loopback module" + depends on SCSI help Say Y here to enable the TCM Virtual SAS target and Linux/SCSI LLD fabric loopback module.