From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 91E131FF16B for ; Fri, 26 Sep 2025 10:10:30 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E7CE7A180; Fri, 26 Sep 2025 10:10:58 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Gabriel Goller Date: Fri, 26 Sep 2025 10:08:59 +0200 Message-ID: <175887413661.3426394.13405794635246501139.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20250911100555.63174-1-g.goller@proxmox.com> References: <20250911100555.63174-1-g.goller@proxmox.com> MIME-Version: 1.0 X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1758874238869 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.153 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] applied: [PATCH kernel 0/5] backport nftables atomicity fix X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" On Thu, 11 Sep 2025 12:05:41 +0200, Gabriel Goller wrote: > Stefan Hanreich discovered this nftables bug which breaks the atomicity when > updating certain sets. This means that when updating a set, packets sometimes > slip through even though the existing and the incoming rules deny the packet. > A full reproducer is available here: [0]. > More information in following commit messages. > > The upstream series has not been applied yet, but is available here: > https://lore.kernel.org/netfilter-devel/20250910080227.11174-1-fw@strlen.de/ > > [...] Applied, thanks! As of now you can condese these backports that are patches of a single patch series also into a single patch for submission as it effectively is one semantic change to our kernel repo. [1/5] kernel: backport: netfilter: nft_set_pipapo: don't check genbit from packetpath lookups commit: 92933a19ce966faab12cdf8898ec360dcee2c378 [2/5] kernel: backport: netfilter: nft_set_rbtree: continue traversal if element is inactive commit: 7f29adff3aee976485b0ae01426e6347f44f304b [3/5] kernel: backport: netfilter: nf_tables: place base_seq in struct net commit: 40dd293b362702e92fb8768bbe19df0faf602df2 [4/5] kernel: backport: netfilter: nf_tables: make nft_set_do_lookup available unconditionally commit: 88da89ad66863668b2aaa2ba8464a7e2f0a5f1c6 [5/5] kernel: backport: netfilter: nf_tables: restart set lookup on base_seq change commit: 8167fffb36aad7bf4d8d54f618ea6b78e066f28c _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel