[lkp] [+82 bytes kernel size regression] [i386-tinyconfig] [5fab44501b] mm/oom_kill: trigger the oom killer if oom occurs without __GFP_FS

[kernel test robot <lkp@intel.com>]

FYI, we noticed a +82 bytes kernel size regression due to commit:

commit: 5fab44501b62e2132235cb0a88c5cb8e0481ff09 (mm/oom_kill: trigger the oom killer if oom occurs without __GFP_FS)
url: https://github.com/intel-lab-lkp/linux/commits/Hui-Wang/mm-oom_kill-trigger-the-oom-killer-if-oom-occurs-without-__GFP_FS/20230426-131239
base: https://git.kernel.org/cgit/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/all/20230426051030.112007-2-hui.wang@canonical.com/
patch subject: [PATCH 1/1] mm/oom_kill: trigger the oom killer if oom occurs without __GFP_FS


Details as below (size data is obtained by `nm --size-sort vmlinux`):

25aab2ea: Merge branch 'mm-nonmm-unstable' into mm-everything
5fab4450: mm/oom_kill: trigger the oom killer if oom occurs without __GFP_FS

+------------------------------+----------+----------+-------+
|            symbol            | 25aab2ea | 5fab4450 | delta |
+------------------------------+----------+----------+-------+
| bzImage                      | 502464   | 502560   | 96    |
| nm.T.out_of_memory           | 430      | 467      | 37    |
| nm.t.trigger_oom_killer_work | 0        | 29       | 29    |
| nm.d.oom_trigger_work        | 0        | 16       | 16    |
+------------------------------+----------+----------+-------+



Thanks