* [lkp] [+454 bytes kernel size regression] [i386-tinyconfig] [5b31ca6562] fs: allow to tuck mounts explicitly
@ 2023-03-26 10:32 kernel test robot
0 siblings, 0 replies; only message in thread
From: kernel test robot @ 2023-03-26 10:32 UTC (permalink / raw)
To: Christian Brauner, Christian Brauner; +Cc: Josh Triplett, lkp, oe-kbuild-all
FYI, we noticed a +454 bytes kernel size regression due to commit:
commit: 5b31ca65629e53f06bb0edf43d31fe5723d91ccd (fs: allow to tuck mounts explicitly)
https://git.kernel.org/cgit/linux/kernel/git/vfs/idmapping.git b4/fs-tucked-mounts
Details as below (size data is obtained by `nm --size-sort vmlinux`):
d13cc7e2: fs: use a for loop when locking a mount
5b31ca65: fs: allow to tuck mounts explicitly
+----------------------------+----------+----------+-------+
| symbol | d13cc7e2 | 5b31ca65 | delta |
+----------------------------+----------+----------+-------+
| bzImage | 501536 | 501824 | 288 |
| nm.t.do_move_mount | 464 | 647 | 183 |
| nm.t.lock_mount_mountpoint | 0 | 152 | 152 |
| nm.t.attach_recursive_mnt | 454 | 572 | 118 |
| nm.t.mnt_tuck_mountpoint | 0 | 69 | 69 |
| nm.t.can_umount | 0 | 44 | 44 |
| nm.T.__ia32_sys_move_mount | 180 | 219 | 39 |
| nm.T.path_mount | 1092 | 1094 | 2 |
| nm.T.path_umount | 83 | 59 | -24 |
| nm.t.lock_mount | 136 | 7 | -129 |
+----------------------------+----------+----------+-------+
Thanks
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-03-26 10:33 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-03-26 10:32 [lkp] [+454 bytes kernel size regression] [i386-tinyconfig] [5b31ca6562] fs: allow to tuck mounts explicitly kernel test robot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).