From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 412F41FF13B for ; Wed, 20 May 2026 10:47:32 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 9BDA21D5C7; Wed, 20 May 2026 10:47:29 +0200 (CEST) From: =?UTF-8?q?Fabian=20Gr=C3=BCnbichler?= To: pve-devel@lists.proxmox.com, Christian Ebner Subject: applied: [PATCH zfsonlinux] debian/patches: backport vmalloc gfp flag fix Date: Wed, 20 May 2026 10:46:47 +0200 Message-ID: <177926680201.2795079.16237286169693741715.b4-ty@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260520083612.781892-1-c.ebner@proxmox.com> References: <20260520083612.781892-1-c.ebner@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1779266799078 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.054 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: RSGNMY4ZELRQDXTRHT6KHHLQYAYFPUDF X-Message-ID-Hash: RSGNMY4ZELRQDXTRHT6KHHLQYAYFPUDF X-MailFrom: f.gruenbichler@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Wed, 20 May 2026 10:36:12 +0200, Christian Ebner wrote: > Since commit 07003531e ("mm/vmalloc: warn on invalid vmalloc gfp > flags") [0] the Linux kernel explicitley warns and clears unsupported > gfp flags to vmalloc calls. ZFS already fixed some of these, in > particular __GFP_COMP flag in commit cb1833023 ("kmem: don't add > __GFP_COMP for KM_VMEM allocations"). This was however incomplete. > > Backport the upstream fix, the otherwise shown kernel trace is > potentially alarming but benign as also confirmed by upstream [1]. > > [...] Applied, thanks! [1/1] debian/patches: backport vmalloc gfp flag fix commit: 069198f9d5ca7876a4af06da2c42f848f0d0552e Best regards, -- Fabian Grünbichler