From: kernel test robot <lkp@intel.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: oe-kbuild-all@lists.linux.dev, lkp@intel.com
Subject: [lkp] [+84 bytes kernel size regression] [i386-tinyconfig] [538cb30493] random: add back async readiness notifier
Date: Sat, 19 Nov 2022 20:37:23 +0800 [thread overview]
Message-ID: <Y3jOA/oR3QPwv6ni@948c295b3299> (raw)
In-Reply-To: <20221116161642.1670235-2-Jason@zx2c4.com>
FYI, we noticed a +84 bytes kernel size regression due to commit:
commit: 538cb30493582ea76f363660fd4bf1c354916854 (random: add back async readiness notifier)
url: https://github.com/intel-lab-lkp/linux/commits/Jason-A-Donenfeld/Use-EFI-variables-for-random-seed/20221117-001923
base: git://git.kernel.org/cgit/linux/kernel/git/crng/random.git master
patch link: https://lore.kernel.org/all/20221116161642.1670235-2-Jason@zx2c4.com/
patch subject: [PATCH RFC v1 1/6] random: add back async readiness notifier
Details as below (size data is obtained by `nm --size-sort vmlinux`):
094226ad: Linux 6.1-rc5
538cb304: random: add back async readiness notifier
+--------------------------------+----------+----------+-------+
| symbol | 094226ad | 538cb304 | delta |
+--------------------------------+----------+----------+-------+
| bzImage | 491552 | 491616 | 64 |
| nm.T.notify_on_rng_initialized | 0 | 54 | 54 |
| nm.t._credit_init_bits | 198 | 222 | 24 |
| nm.b.random_ready_chain | 0 | 4 | 4 |
| nm.D.linux_banner | 152 | 154 | 2 |
+--------------------------------+----------+----------+-------+
Thanks
next prev parent reply other threads:[~2022-11-19 12:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 16:16 [PATCH RFC v1 0/6] Use EFI variables for random seed Jason A. Donenfeld
2022-11-16 16:16 ` [PATCH RFC v1 1/6] random: add back async readiness notifier Jason A. Donenfeld
2022-11-19 12:37 ` kernel test robot [this message]
2022-11-16 16:16 ` [PATCH RFC v1 2/6] vsprintf: initialize siphash key using notifier Jason A. Donenfeld
2022-11-18 14:16 ` Petr Mladek
2022-11-18 14:20 ` Jason A. Donenfeld
2022-11-16 16:16 ` [PATCH RFC v1 3/6] efi: random: combine bootloader provided RNG seed with RNG protocol output Jason A. Donenfeld
2022-11-16 16:16 ` [PATCH RFC v1 4/6] efi: stub: use random seed from EFI variable Jason A. Donenfeld
2022-11-16 16:16 ` [PATCH RFC v1 5/6] efi: efivarfs: prohibit reading random seed variables Jason A. Donenfeld
2022-11-16 17:04 ` Ard Biesheuvel
2022-11-16 18:56 ` Jason A. Donenfeld
2022-11-16 19:42 ` James Bottomley
2022-11-16 20:08 ` Jason A. Donenfeld
2022-11-27 21:36 ` James Bottomley
2022-11-16 16:16 ` [PATCH RFC v1 6/6] efi: refresh non-volatile random seed when RNG is initialized Jason A. Donenfeld
2022-11-16 17:59 ` [PATCH RFC v1 0/6] Use EFI variables for random seed Lennart Poettering
2022-11-16 18:57 ` Jason A. Donenfeld
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=Y3jOA/oR3QPwv6ni@948c295b3299 \
--to=lkp@intel.com \
--cc=Jason@zx2c4.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 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.