From: kernel test robot <lkp@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: oe-kbuild-all@lists.linux.dev, lkp@intel.com
Subject: [lkp] [+118 bytes kernel size regression] [i386-tinyconfig] [6e6937ac88] fs: introduce lock_rename_child() helper
Date: Thu, 16 Mar 2023 08:46:53 +0800 [thread overview]
Message-ID: <ZBJm/VySI5NOYpji@7948dbfe554b> (raw)
In-Reply-To: <20230315223435.5139-3-linkinjeon@kernel.org>
FYI, we noticed a +118 bytes kernel size regression due to commit:
commit: 6e6937ac882828b632bbcecf35ce35d280a2b4fb (fs: introduce lock_rename_child() helper)
url: https://github.com/intel-lab-lkp/linux/commits/Namjae-Jeon/ksmbd-remove-internal-h-include/20230316-063731
base: https://git.kernel.org/cgit/linux/kernel/git/vfs/idmapping.git for-next
patch link: https://lore.kernel.org/all/20230315223435.5139-3-linkinjeon@kernel.org/
patch subject: [PATCH v8 2/3] fs: introduce lock_rename_child() helper
Details as below (size data is obtained by `nm --size-sort vmlinux`):
2d2e9d60: ksmbd: remove internal.h include
6e6937ac: fs: introduce lock_rename_child() helper
+---------------------------+----------+----------+-------+
| symbol | 2d2e9d60 | 6e6937ac | delta |
+---------------------------+----------+----------+-------+
| nm.T.lock_rename_child | 0 | 98 | 98 |
| nm.t.lock_two_directories | 0 | 77 | 77 |
| bzImage | 501536 | 501600 | 64 |
| nm.T.lock_rename | 109 | 52 | -57 |
+---------------------------+----------+----------+-------+
Thanks
next prev parent reply other threads:[~2023-03-16 0:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 22:34 [PATCH v8 0/3] ksmbd patches included vfs changes Namjae Jeon
2023-03-15 22:34 ` [PATCH v8 1/3] ksmbd: remove internal.h include Namjae Jeon
2023-03-17 8:55 ` Christian Brauner
2023-03-15 22:34 ` [PATCH v8 2/3] fs: introduce lock_rename_child() helper Namjae Jeon
2023-03-16 0:46 ` kernel test robot [this message]
2023-03-15 22:34 ` [PATCH v8 3/3] ksmbd: fix racy issue from using ->d_parent and ->d_name Namjae Jeon
2023-03-16 0:30 ` kernel test robot
2023-03-16 0:56 ` Namjae Jeon
2023-03-16 7:30 ` kernel test robot
2023-04-21 2:35 ` [PATCH v8 0/3] ksmbd patches included vfs changes Al Viro
2023-04-21 2:38 ` Al Viro
2023-04-21 7:26 ` Namjae Jeon
2023-06-13 10:57 ` Amir Goldstein
2023-06-13 12:24 ` Namjae Jeon
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=ZBJm/VySI5NOYpji@7948dbfe554b \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.