Re: [PATCH 6.12 0/7] Backport object allocation APIs and two fscrypt fixes

[Greg KH <gregkh@linuxfoundation.org>]

On Thu, Jul 16, 2026 at 09:42:56PM -0700, Eric Biggers wrote:
> Like I did in an earlier series for 6.18
> (https://lore.kernel.org/linux-hardening/20260709043301.142931-1-ebiggers@kernel.org/),
> this series backports kmalloc_obj() et al to 6.12 so that more upstream
> commits will cherry-pick cleanly.  As in 6.18, the flex counter
> integration isn't included.
> 
> Patches 6-7 then backport two fscrypt fixes (which, like lots of other
> kernel code, happen to use kzalloc_obj()).  Patch 7 is a clean
> cherry-pick, while patch 6 required resolving some other conflicts.
> 
> Eric Biggers (2):
>   fscrypt: Fix key setup in edge case with multiple data unit sizes
>   fscrypt: Replace mk_users keyring with simple list
> 
> Kees Cook (2):
>   slab: Introduce kmalloc_obj() and family
>   slab: Introduce kmalloc_flex() and family
> 
> Linus Torvalds (2):
>   add default_gfp() helper macro and use it in the new *alloc_obj()
>     helpers
>   default_gfp(): avoid using the "newfangled" __VA_OPT__ trick
> 
> Randy Dunlap (1):
>   slab: recognize @GFP parameter as optional in kernel-doc

All now queued up, thanks!

greg k-h