From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com, Christian Ebner <c.ebner@proxmox.com>
Subject: applied: [PATCH zfsonlinux] debian/patches: backport vmalloc gfp flag fix
Date: Wed, 20 May 2026 10:46:47 +0200 [thread overview]
Message-ID: <177926680201.2795079.16237286169693741715.b4-ty@proxmox.com> (raw)
In-Reply-To: <20260520083612.781892-1-c.ebner@proxmox.com>
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 <f.gruenbichler@proxmox.com>
prev parent reply other threads:[~2026-05-20 8:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 8:36 [PATCH zfsonlinux] debian/patches: backport vmalloc gfp flag fix Christian Ebner
2026-05-20 8:46 ` Fabian Grünbichler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=177926680201.2795079.16237286169693741715.b4-ty@proxmox.com \
--to=f.gruenbichler@proxmox.com \
--cc=c.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox