Starting targetcli-fb breaks with unknown parameter in target_core_mod.
Kernel configuration like in https://wiki.gentoo.org/wiki/ISCSI/Target
Asking for crc_t10dif.
Trying to resolve especially a logic behind
SCSI_LPFC [=m] && SCSI_LOWLEVEL [=y] && PCI [=y] && SCSI [=y] && CPU_FREQ [=y] && SCSI_FC_ATTRS [=m] && (NVME_TARGET_FC [=n] || NVME_TARGET_FC [=n]=n) && ( NVME_FC [=m] || NVME_FC [=m]=n)
in kernel config
Steps to Reproduce:
1. emerge targetcli-fb
2. select kernel modules from https://wiki.gentoo.org/wiki/ISCSI/Target
3. run targetcli
4. get dmesg
abenakit /usr/src/linux # targetcli
b"modprobe: ERROR: could not insert 'target_core_mod': Unknown symbol in module, or unknown parameter (see dmesg)\n"
abenakit /usr/src/linux # dmesg | tail -n 2
[ 9383.623134] target_core_mod: Unknown symbol crc_t10dif (err -2)
[ 9383.623273] target_core_mod: Unknown symbol crc_t10dif_update (err -2)
targetcli runs (&& / ||) modprobe target_core_mod loads (&& / ||) kernel parameter CONFIG_CRC_T10DIF
(NVME_TARGET_FC [=n] || NVME_TARGET_FC [=n]=n) && ( NVME_FC [=m] || NVME_FC [=m]=n)
can be configured to make CONFIG_CRC_T10DIF: a known symbol in the target_core_mod
I am not sure where to post this if this is a kernel topic or a targetcli-fb.
I dont need the FibreChannel Drivers neither the nvme but somehow the module seems to depend on them.
Or maybe I am just missing out on an easy way to configure this set of the kernel sources.
Created attachment 727569 [details]
annex kernel config
It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis.
I have had very good experience on the gentoo IRC  with questions like this. Of course there are also forums and mailing lists [2,3].
I asssigned the ticket, please try to find out more details on one of the mentioned channels  and report the important findings here.
Thanks I will try there.
I gave genkernel a run and it is definetly a problem on my understanding of the kernel config. With genkernel the modules are compiled and I am able to start targetcli as the target_core modules loads also the t10_dif.
So it is _not_ a bug.
Sorry for bringing it up here.
If you want to close this issue feel free.
Anyhow as soon as I know which param is blocking the selection of the t10_dif module I will post it here if anybody else runs into this and/or confusion.
Hi Stefan, could you find out more so that we can fix/close this one?