From: kernel test robot <lkp@intel.com>
To: Amir Goldstein <amir73il@gmail.com>
Cc: lkp@intel.com, oe-kbuild-all@lists.linux.dev
Subject: [lkp] [+77 bytes kernel size regression] [i386-tinyconfig] [5a7c77eebb] fsnotify: prepare for directory entry pre-modify permission events
Date: Thu, 08 Dec 2022 06:22:21 +0800 [thread overview]
Message-ID: <6391121d.WolFGJw5FjD6RKcH%lkp@intel.com> (raw)
FYI, we noticed a +77 bytes kernel size regression due to commit:
commit: 5a7c77eebbac19d62a5f25c78e66c487cd7f8366 (fsnotify: prepare for directory entry pre-modify permission events)
https://github.com/amir73il/linux fan_pre_modify
Details as below (size data is obtained by `nm --size-sort vmlinux`):
79db767d: fanotify: introduce FAN_PRE_ATTRIB permission event
5a7c77ee: fsnotify: prepare for directory entry pre-modify permission events
+-------------------------+----------+----------+-------+
| symbol | 79db767d | 5a7c77ee | delta |
+-------------------------+----------+----------+-------+
| nm.T.filename_lookupat | 0 | 183 | 183 |
| nm.T.user_path_lookupat | 0 | 69 | 69 |
| bzImage | 492256 | 492320 | 64 |
| nm.t.filename_parentat | 165 | 174 | 9 |
| nm.t.do_readlinkat | 191 | 196 | 5 |
| nm.T.do_renameat2 | 814 | 817 | 3 |
| nm.T.do_rmdir | 257 | 251 | -6 |
| nm.T.do_unlinkat | 366 | 360 | -6 |
| nm.T.kern_path_locked | 139 | 132 | -7 |
| nm.t.filename_create | 222 | 215 | -7 |
| nm.T.user_path_at_empty | 56 | 0 | -56 |
| nm.T.filename_lookup | 129 | 19 | -110 |
+-------------------------+----------+----------+-------+
Thanks
reply other threads:[~2022-12-07 22:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6391121d.WolFGJw5FjD6RKcH%lkp@intel.com \
--to=lkp@intel.com \
--cc=amir73il@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).