User Details
- User Since
- Feb 4 2016, 4:45 PM (562 w, 5 d)
Yesterday
Mon, Nov 16
Sun, Nov 15
Provide patch with context.
Sat, Nov 14
Fri, Nov 13
Thu, Nov 12
@nprice ping again. I would really like to have this in tree. If you don't want to commit this, let me know and I can do it.
Sat, Nov 7
Fri, Nov 6
Wed, Nov 4
@nprice Can you commit this?
I agree. There was a problem on my side. I added packetdrill reproducers to the PRs.
I attached kyua tests for both cases generated with Claude Code.
Maxim
Tue, Nov 3
I tested this patch on a Framework AMD laptop and it resolves the problem for me. No more messages observed.
Mon, Nov 2
This fixes PR 296474.
It would be great if this fix can go in soon, such we can get it into 15.2. Please refer to the PR.
Fri, Oct 30
Thu, Oct 29
Thu, Oct 22
Wed, Oct 21
Oct 16 2026
Oct 15 2026
Oct 14 2026
Oct 11 2026
I am trying to trigger a "sent too much" KASSERT but was not successful up to now. Can you provide a BBLog file of such a situation?
Oct 9 2026
Let me write a packetdrill-test to make sure we catch an KASSERT-issue.
Oct 8 2026
D60444 solves the problem in a better way.
Oct 7 2026
Improve comment.
As suggested by Gleb: lie about error in sysctl_setsockopt() to avoid a loop in userland_sysctl().
Oct 6 2026
Let tfb_tcp_handoff_ok() return bool. That is simpler and out of tree stacks a caught by the compiler.
Oct 5 2026
An alternative approach would be to change int (*tfb_tcp_handoff_ok)(struct tcpcb *) to bool (*tfb_tcp_handoff_ok)(struct tcpcb *) and let the caller map false to EINVAL. Would that be clearer? That would also allow the compiler to catch the change in TCP stacks other than BBR and RACK.
