From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from Chamillionaire.breakpoint.cc (Chamillionaire.breakpoint.cc [91.216.245.30]) (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 DE975139F for ; Tue, 9 Jul 2024 05:49:56 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=91.216.245.30 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720504200; cv=none; b=pxqF7dcHFlbyaHyWJrN42k1B6Vylb57eXOfDLcK4FB63tnGgCTHwK+iFuTibnwZoGj+Uxq5ROiUjIoMUmp7fsmciYUoIiUYgDa649YeUByDB4gq1vBL9KHdcu7xnaz4waxxz+nPFexTFAoGwWT6mOTfUwXflobhprDRzwVfSHOA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1720504200; c=relaxed/simple; bh=4qy/RFEouRJyMzA1Kt2+nxhwdHIrvaxqYXtV+rOROY0=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=IwxYaL+ac5X93d6X9iMkEfDlZ0yC5NwGoAjdDJtw1UjBBSCr+xuEfzHfbxBIHnPW3QHbudTmS7fAzEC4CuZRcHgYHryOWz6RBjzWeLvdtqkCLcBpn2EtrDRwHoAYd9OYn8GmDYD34OH5PnCWIbq7gSoGpSJBTb5Q/SouoMUaudc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=strlen.de; spf=pass smtp.mailfrom=strlen.de; arc=none smtp.client-ip=91.216.245.30 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=strlen.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=strlen.de Received: from fw by Chamillionaire.breakpoint.cc with local (Exim 4.92) (envelope-from ) id 1sR3ja-0007hx-32; Tue, 09 Jul 2024 07:49:50 +0200 Date: Tue, 9 Jul 2024 07:49:50 +0200 From: Florian Westphal To: Xin Long Cc: Florian Westphal , Ilya Maximets , network dev , dev@openvswitch.org, Marcelo Ricardo Leitner , Jiri Pirko , Davide Caratti , Jamal Hadi Salim , Eric Dumazet , Cong Wang , kuba@kernel.org, Paolo Abeni , davem@davemloft.net, Pablo Neira Ayuso , Aaron Conole Subject: Re: [PATCH net-next 3/3] openvswitch: set IPS_CONFIRMED in tmpl status only when commit is set in conntrack Message-ID: <20240709054950.GA29568@breakpoint.cc> References: <20240619201959.GA1513@breakpoint.cc> <20240619212030.GB1513@breakpoint.cc> <20240708223839.GA18283@breakpoint.cc> Precedence: bulk X-Mailing-List: netdev@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Xin Long wrote: > > Xin Long wrote: > > > I can avoid this warning by not allocating ext for commit ct in ovs: > > > > > > @@ -426,7 +426,7 @@ static int ovs_ct_set_labels(struct nf_conn *ct, > > > struct sw_flow_key *key, > > > struct nf_conn_labels *cl; > > > int err; > > > > > > - cl = ovs_ct_get_conn_labels(ct); > > > + cl = nf_ct_labels_find(ct); > > > if (!cl) > > > return -ENOSPC; > ovs_ct_get_conn_labels() must be replaced with nf_ct_labels_find() in here > anyway, thinking that the confirmed ct without labels was created in other > places (not by OVS conntrack), the warning may still be triggered when > trying to set labels in OVS after. Right. > > Then ovs_ct_limit_init() and nf_connlabels_get() need to be called > > once on the first conntrack operatation, regardless if labels are asked > > for or not. > > > > Not nice but still better than current state. > Right, not nice, it undermines the bits check against NF_CT_LABELS_MAX_SIZE. Yes, but OTOH this bit check isn't used anymore, it comes from days when label area was dynamically sized, today is hardcoded to 128 anyway.