From: Kees Cook <kees@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Kees Cook <kees@kernel.org>
Subject: [GIT PULL] kmalloc_obj prep for v7.0-rc1
Date: Thu, 19 Feb 2026 10:31:48 -0800 [thread overview]
Message-ID: <202602191029.2F0E7F01@keescook> (raw)
Hi Linus,
Please pull these kmalloc_obj preparation patches for v7.0-rc1. I'm
expecting to send the treewide conversion PR later today (or early
tomorrow).
Thanks!
-Kees
The following changes since commit 2b7a25df823dc7d8f56f8ce7c2d2dac391cea9c2:
Merge tag 'mm-nonmm-stable-2026-02-18-19-56' of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm (2026-02-18 21:40:16 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/kmalloc_obj-prep-v7.0-rc1
for you to fetch changes up to c732084c891d89a1a0824126b3075999a981bc88:
KVM: arm64: vgic: Handle const qualifier from gic_kvm_info allocation type (2026-02-19 10:14:02 -0800)
----------------------------------------------------------------
kmalloc_obj prep for v7.0-rc1
Fixes for return types to prepare for the kmalloc_obj treewide conversion,
that haven't yet appeared during the merge window: dm-crypt, dm-zoned,
drm/msm, and arm64 kvm.
----------------------------------------------------------------
Kees Cook (4):
dm-crypt: Adjust crypt_alloc_tfms_aead() allocation type
dm: dm-zoned: Adjust dmz_load_mapping() allocation type
drm/msm: Adjust msm_iommu_pagetable_prealloc_allocate() allocation type
KVM: arm64: vgic: Handle const qualifier from gic_kvm_info allocation type
arch/arm64/kvm/vgic/vgic-init.c | 2 +-
drivers/gpu/drm/msm/msm_iommu.c | 2 +-
drivers/md/dm-crypt.c | 2 +-
drivers/md/dm-zoned-metadata.c | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
--
Kees Cook
next reply other threads:[~2026-02-19 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 18:31 Kees Cook [this message]
2026-02-20 22:12 ` Kees Cook
2026-02-21 1:20 ` pr-tracker-bot
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=202602191029.2F0E7F01@keescook \
--to=kees@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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
Powered by JetHome