Date: Sat, 22 Feb 2025 00:24:11 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 283903] rtw88: possible skb leak Message-ID: <bug-283903-21060-NaTxaxsaTA@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-283903-21060@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283903 --- Comment #30 from Guillaume Outters <guillaume-freebsd@outters.eu> --- To reproduce: it seems that my manual traces + sysctl compat.linuxkpi.skb.debug=0x10 + visiting Ars Technica do a wonderful job stressing the c2h_queue and mess after 2 mn of uptime. Do all the printf add latency that increase the risks of concurrent modifications of the queue? As for the linked list, in degraded mode it seems that new entries get inserted before c2h_queue, and let the head be its own next; thus, as skb_queue_walk_safe anti-infinite-loop end condition is "when ->next is &c2h_queue itself", it will never go further than the 0th iteration. -- You are receiving this mail because: You are on the CC list for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-283903-21060-NaTxaxsaTA>
