From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from out-186.mta0.migadu.com (out-186.mta0.migadu.com [91.218.175.186]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 26336D528 for ; Thu, 24 Apr 2025 09:19:42 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.218.175.186 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1745486385; cv=none; b=M1UqloI/9FzQYuVEqt3njfLCLPWxCeP+5IhSgwidBzXDYIg/0xSvpCLulFc2TtR9uFj9eSYi8PgVXCWPVbLoQB+VATcwSPUF82ac9j3CGTuxzXn1cGi4fmm4ecSgTPV5QzywgCFUdmExWSAWKzwDGFNSQP5xORkXDrWwChlLCCY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1745486385; c=relaxed/simple; bh=WD6Ff4on3gMXSvQb82UdayrkaTp2LKo8STmvaYTquPk=; h=MIME-Version:Date:Content-Type:From:Message-ID:Subject:To:Cc: In-Reply-To:References; b=Ynrd83FLKnwVcMuowsy18laamaqslGEbne96WXHGmTPfIpt82Cd9wXMzCti0yj4sp14aIryvy9cUPcV8VyVCECiHHgvKeSYyTmksi7bjJsFum0Ju9jZrFmKdqPg80N0gSrh9hBNg7dPxowX0YYPyuHJ7DdN90LZpevKtapKlpZU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev; spf=pass smtp.mailfrom=linux.dev; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b=dPU29toD; arc=none smtp.client-ip=91.218.175.186 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linux.dev Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linux.dev Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linux.dev header.i=@linux.dev header.b="dPU29toD" Precedence: bulk X-Mailing-List: bpf@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linux.dev; s=key1; t=1745486370; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Lsifh0qg1ETcVD6N2Oh5iR/tKrplPyYEmImPJnlsTSw=; b=dPU29toDEYXeQGvicYDT3fMKS6gTIShnuS14kkbKpGZcF1/X24kzMReG/Ft3/A/gsYB4hM 8EkmP9C0fTXl8GSRpJzMjTg5mpD+lHtzGykMVc3tQTzxoAKO3v18iPb12gI0QzdKb9RSsa ItMwoHumt3M/KA5b18V44bZlz9godwU= Date: Thu, 24 Apr 2025 09:19:28 +0000 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: "Jiayuan Chen" Message-ID: <978f0f1e4ab0c8f46820af305f5efb00cf94ffd2@linux.dev> TLS-Required: No Subject: Re: To: "Cong Wang" Cc: john.fastabend@gmail.com, jakub@cloudflare.com, netdev@vger.kernel.org, bpf@vger.kernel.org In-Reply-To: <90f887391cff690e883e40cbb67a9614e7757295@linux.dev> References: <90f887391cff690e883e40cbb67a9614e7757295@linux.dev> X-Migadu-Flow: FLOW_OUT April 24, 2025 at 08:59, "Jiayuan Chen" wrote: >=20 >=20April 24, 2025 at 08:40, "Cong Wang" wrote= : >=20 >=20>=20 >=20> netdev@vger.kernel.org, bpf@vger.kernel.org > >=20 >=20> Bcc:=20 >=20>=20 >=20>=20 >=20> Subject: test_sockmap failures on the latest bpf-next > >=20 >=20> Reply-To:=20 >=20>=20 >=20>=20=20 >=20>=20 >=20> Hi all, > >=20 >=20>=20=20 >=20>=20 >=20> The latest bpf-next failed on test_sockmap tests, I got the follow= ing > >=20 >=20> failures (including 1 kernel warning). It is 100% reproducible her= e. > >=20 >=20> I don't have time to look into them, a quick glance at the changel= og > >=20=20 >=20> shows quite some changes from Jiayuan. So please take a look, Jiay= uan. > >=20 >=20> Meanwhile, please let me know if you need more information from me= . > >=20 >=20> Thanks! > >=20 >=20>=20=20 >=20>=20 >=20> ---------------> > >=20 >=20 > Thanks, I'm working on it. >=20 After=20resetting my commit to 0bb2f7a1ad1f, which is before my changes, = the warning still exists. The warning originates from test_txmsg_redir_wait_sndmem(), which perform= s 'KTLS + sockmap with redir EGRESS and limited receive buffer'. The memory charge/uncharge logic is problematic, I need some time to inve= stigate and fix it. Thanks.