[Bug 273890] accessing freed inpcb in udp6_bind

2023-12-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273890 Gleb Smirnoff changed: What|Removed |Added Assignee|b...@freebsd.org|gleb...@freebsd.org -- You are re

[Bug 273890] accessing freed inpcb in udp6_bind

2023-12-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273890 --- Comment #16 from Gleb Smirnoff --- Weldon, Dmitry, please test the patch from this review. Let me know if you have any problems with applying it. https://reviews.freebsd.org/D43122 -- You are receiving this mail because: You are the

[Bug 273890] accessing freed inpcb in udp6_bind

2023-12-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273890 --- Comment #15 from Gleb Smirnoff --- I see the problem. The inpcb destruction order has a flaw. We first clear inp_socket, then set INP_FREED flag, then call in_pcbremhash(). This isn't compatible with inpcb_lookup_local() which doesn't u

[Bug 273890] accessing freed inpcb in udp6_bind

2023-12-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273890 --- Comment #14 from Gleb Smirnoff --- Weldon gave me access to the core. Writing up summary for Mark and other interested parties. The panic happens at in6_pcb.c:257: (t->inp_socket->so_options & SO_REUSEPORT) || The temporary inpcb t ha

[Bug 273890] accessing freed inpcb in udp6_bind

2023-12-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273890 Gleb Smirnoff changed: What|Removed |Added Status|Open|In Progress -- You are receiving

[Bug 273890] accessing freed inpcb in udp6_bind

2023-12-19 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=273890 Gleb Smirnoff changed: What|Removed |Added Summary|Fatal trap 12: page fault |accessing freed inpcb in