From: kernel test robot <lkp@intel.com>
To: Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Alexander Potapenko <glider@google.com>,
Marco Elver <elver@google.com>,
Dmitry Vyukov <dvyukov@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
linux-kernel@vger.kernel.org, Hyeonggon Yoo <42.hyeyoo@gmail.com>
Subject: Re: [PATCH] mm/kfence: reset PG_slab and memcg_data before freeing __kfence_pool
Date: Thu, 5 May 2022 18:57:42 +0800 [thread overview]
Message-ID: <202205051852.M26PcwNj-lkp@intel.com> (raw)
In-Reply-To: <20220505070105.1835745-1-42.hyeyoo@gmail.com>
Hi Hyeonggon,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on hnaz-mm/master]
url: https://github.com/intel-lab-lkp/linux/commits/Hyeonggon-Yoo/mm-kfence-reset-PG_slab-and-memcg_data-before-freeing-__kfence_pool/20220505-150237
base: https://github.com/hnaz/linux-mm master
config: s390-randconfig-r044-20220505 (https://download.01.org/0day-ci/archive/20220505/202205051852.M26PcwNj-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 11.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/ad166fcbcd464ea0251165580e1ea0152531fe56
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review Hyeonggon-Yoo/mm-kfence-reset-PG_slab-and-memcg_data-before-freeing-__kfence_pool/20220505-150237
git checkout ad166fcbcd464ea0251165580e1ea0152531fe56
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.3.0 make.cross W=1 O=build_dir ARCH=s390 SHELL=/bin/bash mm/kfence/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
mm/kfence/core.c: In function 'kfence_init_pool_early':
>> mm/kfence/core.c:634:21: error: 'struct page' has no member named 'memcg_data'
634 | page->memcg_data = 0;
| ^~
vim +634 mm/kfence/core.c
610
611 static bool __init kfence_init_pool_early(void)
612 {
613 unsigned long addr;
614
615 if (!__kfence_pool)
616 return false;
617
618 addr = kfence_init_pool();
619
620 if (!addr)
621 return true;
622
623 /*
624 * Only release unprotected pages, and do not try to go back and change
625 * page attributes due to risk of failing to do so as well. If changing
626 * page attributes for some pages fails, it is very likely that it also
627 * fails for the first page, and therefore expect addr==__kfence_pool in
628 * most failure cases.
629 */
630 for (char *p = (char *)addr; p < __kfence_pool + KFENCE_POOL_SIZE; p += PAGE_SIZE) {
631 struct page *page;
632
633 page = virt_to_page(p);
> 634 page->memcg_data = 0;
635 __ClearPageSlab(page);
636 }
637 memblock_free_late(__pa(addr), KFENCE_POOL_SIZE - (addr - (unsigned long)__kfence_pool));
638 __kfence_pool = NULL;
639 return false;
640 }
641
--
0-DAY CI Kernel Test Service
https://01.org/lkp
prev parent reply other threads:[~2022-05-05 10:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-05 7:01 [PATCH] mm/kfence: reset PG_slab and memcg_data before freeing __kfence_pool Hyeonggon Yoo
2022-05-05 7:12 ` Marco Elver
2022-05-05 7:19 ` Marco Elver
2022-05-05 7:27 ` Hyeonggon Yoo
2022-05-05 7:39 ` [PATCH v2] " Hyeonggon Yoo
2022-05-05 8:25 ` Marco Elver
2022-05-05 9:07 ` Muchun Song
2022-05-05 10:13 ` [PATCH v3] " Hyeonggon Yoo
2022-05-05 10:54 ` Muchun Song
2022-05-05 11:33 ` Hyeonggon Yoo
2022-05-05 12:00 ` Muchun Song
2022-05-05 10:57 ` kernel test robot [this message]
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=202205051852.M26PcwNj-lkp@intel.com \
--to=lkp@intel.com \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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.