Good evening, all.

I'm running slackware x64 current in a hyper-v vm, and I encountered an oddity when the kernel was first upgraded to the 4.9 branch, and I'm hoping someone can help me either dig to the bottom of the hole or confirm that I've found an actual problem.

In the new branch, the hv_storvsc module now depends on scsi_transport_fc. However, attempting to load scsi_transport_fc results in an error due to a same-name symbol already being present (I don't have the name in front of me, I can recreate if relevant). The symbol in question appears to be the one that hv_storvsc depends on, so I hacked around by manually adding scsi_transport_fc to /lib/modules/{}/modules.builtin and running depmod prior to mkinitrd. This boots and appears to work, but I'm not deep enough in kernel modules to know if this band-aid will hold. Does anyone have insights?

TalonRed --

Interesting ... I am going to run into something like this out in the field someday ...

A quick google search resulted in:

this: https://tracker.debian.org/media/pac...og-4.11-1~exp2 ( look for scsi_transport_fc )

and

this: http://lkml.iu.edu/hypermail/linux/k...2/subject.html ( look for scsi_transport_fc )

Maybe one of the three Kernel Devs or the Debian Packager has a hint ?

HTH

-- kjh