From nobody Thu Jan 9 08:38:51 2025 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4YTJ9767NVz5kMSv for ; Thu, 09 Jan 2025 08:38:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R11" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4YTJ972cJqz4WbH for ; Thu, 9 Jan 2025 08:38:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1736411931; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Em01aFC7/40h8msZSM6LLJT5my+IDn/L2kEI4wy8ABg=; b=T760aO4lTTqiobkfLxwukZf3ENWFf7td4UJVv8fQQ20OkYXit04sZhfROOv2W652CHFE2w jZBr7NGiFaGueAxFEdZ90MiwSgv1CDZ7G527xas7BpZ0Q2jVx/mja9XktyNXRkxctLn/NV C6npWTmUeWGtElwshRacGcR/DkRk6M3gfL92S1tEf8oqkI4FQM5BzhGfZG5FouNbeq03lG 7to6B26XsZjBItkbpJmls9/KW2e60YJX+kGUXBZNykxJuLhZFUENZU+HvV4OPGUQSoi+Gb WdnfIts0WW0ukXIMGkeZiIGwQHtal1phCDPFH/Sp97ySXkicfGNHZ9uAuVAQmg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1736411931; a=rsa-sha256; cv=none; b=mU0hjl3FphplHbS+MG3jF8d/mCmKQFhZZExQapxBNbGlYxqTaf3faacCR6h6RL6AFYB9HM HpJ1SjVDZ01jluHZRzIHoHSAoIbVkDSvssHNmrlnNUrioNFfNvGFvppeUdQl8sSx9yQg2u /wHo9RRA7S4kAp47W8tcaCQDs4aDSwE3MX/E3ERwfxkrYLVmGnHkm1kATQD5PZbBk2AQ9h 374MZst31CDfSGdqTxRtjewcpqY7PYCLdjNZsJoNvZLqrkUNw94oCvK7Y0t4gwI7CZg7ib Y/NRzxobhcBwpR0Jwv0QDCuR7RCM7yu/Il1h4ItUWTlVjPTUtdxzwCuXpjODRg== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4YTJ971wYzz3mq for ; Thu, 09 Jan 2025 08:38:51 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 5098cpgk099908 for ; Thu, 9 Jan 2025 08:38:51 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 5098cpL8099907 for wireless@FreeBSD.org; Thu, 9 Jan 2025 08:38:51 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 283903] rtw88: possible skb leak Date: Thu, 09 Jan 2025 08:38:51 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: oleg.nauman@gmail.com X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bz@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D283903 --- Comment #4 from oleg.nauman@gmail.com --- (In reply to Guillaume Outters from comment #3) Hello, I can not confirm that "skb allocation failure" happens only when virtual memory is exhausted Could you please directly confirm that you also observing "skb allocation failure" messages? Unfortunately Bjoern can not reproduce it so I was under assumptions so it is somehow triggered by my load pattern ( laptop which I = am using as my desktop ) Thank you --=20 You are receiving this mail because: You are on the CC list for the bug.=