[Bug 234444] cc_htcp + TCP_RFC7413 panic

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234444

--- Comment #8 from Michael Tuexen <tuexen at freebsd.org> ---
(In reply to Sergey Samoyloff from comment #6)
Here is the config I'm using when trying to reproduce it:

tuexen at stable11:~ % uname -a
FreeBSD stable11 11.2-RELEASE-p8 FreeBSD 11.2-RELEASE-p8 #0 r342950: Fri Jan 11
23:37:10 CET 2019    
tuexen at stable11:/usr/home/tuexen/releng/11.2/sys/amd64/compile/TCP  amd64
tuexen at stable11:~ % sysctl net.inet.tcp.cc.algorithm
net.inet.tcp.cc.algorithm: htcp
tuexen at stable11:~ % sysctl net.inet.tcp.cc.htcp
net.inet.tcp.cc.htcp.rtt_scaling: 1
net.inet.tcp.cc.htcp.adaptive_backoff: 1
tuexen at stable11:~ % sysctl net.inet.tcp.fastopen.enabled
net.inet.tcp.fastopen.enabled: 1
tuexen at stable11:~ % cat stable/11/sys/amd64/conf/TCP
include         GENERIC
ident           TCP     

makeoptions     WITH_EXTRA_TCP_STACKS=1
options         TCP_RFC7413
options         IPFIREWALL
options         IPFIREWALL_VERBOSE
options         IPFIREWALL_VERBOSE_LIMIT=5
options         IPFIREWALL_DEFAULT_TO_ACCEPT
tuexen at stable11:~ % cat /etc/make.conf 
MODULES_OVERRIDE=tcp cc opensolaris dtrace

I have a HTTP server supporting TCP fast open running and an sshd not using TCP
fast open. I can log into the machine without problems, and access the HTTP
server actually using TCP fast open.

So the problem is not just using a combination of the CC module and using TCP
fast open.

Just to double check: When you compiled you custom kernel with TCP fast open
enabled, you also recompiled the kernel modules you are using, right?

-- 
You are receiving this mail because:
You are the assignee for the bug.