mirror of
https://github.com/torvalds/linux.git
synced 2024-11-23 04:31:50 +00:00
65e2a74c44
When the NVME target code is built-in but its TCP frontend is a loadable module, enabling keyring support causes a link failure: x86_64-linux-ld: vmlinux.o: in function `nvmet_ports_make': configfs.c:(.text+0x100a211): undefined reference to `nvme_keyring_id' The problem is that CONFIG_NVME_TARGET_TCP_TLS is a 'bool' symbol that depends on the tristate CONFIG_NVME_TARGET_TCP, so any 'select' from it inherits the state of the tristate symbol rather than the intended CONFIG_NVME_TARGET one that contains the actual call. The same thing is true for CONFIG_KEYS, which itself is required for NVME_KEYRING. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Link: https://lore.kernel.org/r/20231122224719.4042108-3-arnd@kernel.org Signed-off-by: Jens Axboe <axboe@kernel.dk> |
||
---|---|---|
.. | ||
admin-cmd.c | ||
auth.c | ||
configfs.c | ||
core.c | ||
discovery.c | ||
fabrics-cmd-auth.c | ||
fabrics-cmd.c | ||
fc.c | ||
fcloop.c | ||
io-cmd-bdev.c | ||
io-cmd-file.c | ||
Kconfig | ||
loop.c | ||
Makefile | ||
nvmet.h | ||
passthru.c | ||
rdma.c | ||
tcp.c | ||
trace.c | ||
trace.h | ||
zns.c |