FYI, we noticed a +1158 bytes kernel size regression due to commit: commit: 22dd199a7221932b194badb999181ca3fa2e62e2 (mm: introduce secretmemfd system call to create "secret" memory areas) https://git.kernel.org/pub/scm/linux/kernel/git/rppt/linux.git secretmemfd/v0 Details as below (size data is obtained by `nm --size-sort vmlinux`): f56cf703: mmap: make mlock_future_check() global 22dd199a: mm: introduce secretmemfd system call to create "secret" memory areas +--------------------------------+----------+----------+-------+ | symbol | f56cf703 | 22dd199a | delta | +--------------------------------+----------+----------+-------+ | bzImage | 442560 | 443008 | 448 | | nm.T.__ia32_sys_secretmemfd | 0 | 285 | 285 | | nm.t.secretmem_fault | 0 | 254 | 254 | | nm.R.secretmem_fops | 0 | 128 | 128 | | nm.t.secretmem_mmap | 0 | 110 | 110 | | nm.r.secretmem_super_ops | 0 | 92 | 92 | | nm.r.secretmem_aops | 0 | 88 | 88 | | nm.r.secretmem_vm_ops | 0 | 52 | 52 | | nm.t.secretmem_evict_inode | 0 | 37 | 37 | | nm.d.secretmem_fs | 0 | 36 | 36 | | nm.t.secretmem_init | 0 | 29 | 29 | | nm.t.secretmem_init_fs_context | 0 | 29 | 29 | | nm.t.secretmem_migratepage | 0 | 6 | 6 | | nm.t.secretmem_freepage | 0 | 5 | 5 | | nm.b.secretmem_mnt | 0 | 4 | 4 | | nm.t.secretmem_isolate_page | 0 | 3 | 3 | +--------------------------------+----------+----------+-------+ Thanks