Bug 217401
Summary: | TCP_ULP option is not working for tls | ||
---|---|---|---|
Product: | Linux | Reporter: | Sumit (sumit.200744) |
Component: | Kernel | Assignee: | Virtual assignee for kernel bugs (linux-kernel) |
Status: | RESOLVED DISTRO_KERNEL | ||
Severity: | normal | CC: | kubakici |
Priority: | P3 | Flags: | mricon:
bugbot+
|
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 5.15 | Subsystem: | NETWORKING [TLS] |
Regression: | No | Bisected commit-id: |
Description
Sumit
2023-05-04 11:55:36 UTC
What kernel version is this? I tried it on 5.15.78 where I'm getting the above failure - "No such file or directory for setsockopt. Not sure on which linux kernel this TLS option is introduced. Jakub Kicinski <kuba@kernel.org> replies to comment #2: On Thu, 4 May 2023 16:19:29 +0000 (UTC) Kernel.org Bugbot wrote: > I tried it on 5.15.78 where I'm getting the above failure - "No such > file or directory for setsockopt. Not sure on which linux kernel this > TLS option is introduced. Can you show the output of: modprobe tls cat /proc/sys/net/ipv4/tcp_available_ulp grep CONFIG_TLS /boot/config-* ? (via https://msgid.link/20230504095114.6656e611@kernel.org) Trying it on android platform. Seems TLS is not enabled in kernel # modprobe tls modprobe: No module configuration directories given. # insmod tls insmod: tls: No such file or directory # cat /proc/sys/net/ipv4/tcp_available_ulp # grep CONFIG_TLS /boot/config-* grep: /boot/config-*: No such file or directory Sounds like it. I'm not familiar with the Android kernel but the tls code either needs to be loaded as a module or compiled in, and since /proc/sys/net/ipv4/tcp_available_ulp is empty - neither seems to be the case on your system. |