oe-kbuild-all.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Zi Yan <ziy@nvidia.com>
To: kernel test robot <lkp@intel.com>
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	"Yang Shi" <shy828301@gmail.com>, "Yu Zhao" <yuzhao@google.com>,
	linux-mm@kvack.org, oe-kbuild-all@lists.linux.dev,
	"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
	"Ryan Roberts" <ryan.roberts@arm.com>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Roman Gushchin" <roman.gushchin@linux.dev>,
	"Zach O'Keefe" <zokeefe@google.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v2 4/7] mm: page_owner: add support for splitting to any order in split page_owner.
Date: Wed, 29 Mar 2023 09:16:32 -0400	[thread overview]
Message-ID: <657AFA72-1604-4FFF-8F40-1B6CFB0B5061@nvidia.com> (raw)
In-Reply-To: <202303291732.7OqWI96E-lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 3998 bytes --]

On 29 Mar 2023, at 5:58, kernel test robot wrote:

> Hi Zi,
>
> Thank you for the patch! Yet something to improve:
>
> [auto build test ERROR on akpm-mm/mm-everything]
> [also build test ERROR on linus/master v6.3-rc4 next-20230329]
> [If your patch is applied to the wrong git tree, kindly drop us a note.
> And when submitting patch, we suggest to use '--base' as documented in
> https://git-scm.com/docs/git-format-patch#_base_tree_information]
>
> url:    https://github.com/intel-lab-lkp/linux/commits/Zi-Yan/mm-memcg-use-order-instead-of-nr-in-split_page_memcg/20230329-091809
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
> patch link:    https://lore.kernel.org/r/20230329011712.3242298-5-zi.yan%40sent.com
> patch subject: [PATCH v2 4/7] mm: page_owner: add support for splitting to any order in split page_owner.
> config: i386-randconfig-m021 (https://download.01.org/0day-ci/archive/20230329/202303291732.7OqWI96E-lkp@intel.com/config)
> compiler: gcc-11 (Debian 11.3.0-8) 11.3.0
> reproduce (this is a W=1 build):
>         # https://github.com/intel-lab-lkp/linux/commit/6d1831c0e01a1a742e026454fe6e5643e08c5985
>         git remote add linux-review https://github.com/intel-lab-lkp/linux
>         git fetch --no-tags linux-review Zi-Yan/mm-memcg-use-order-instead-of-nr-in-split_page_memcg/20230329-091809
>         git checkout 6d1831c0e01a1a742e026454fe6e5643e08c5985
>         # save the config file
>         mkdir build_dir && cp config build_dir/.config
>         make W=1 O=build_dir ARCH=i386 olddefconfig
>         make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash
>
> If you fix the issue, kindly add following tag where applicable
> | Reported-by: kernel test robot <lkp@intel.com>
> | Link: https://lore.kernel.org/oe-kbuild-all/202303291732.7OqWI96E-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>    mm/page_owner.c: In function '__split_page_owner':
>>> mm/page_owner.c:226:28: error: implicit declaration of function 'lookup_page_ext' [-Werror=implicit-function-declaration]
>      226 |                 page_ext = lookup_page_ext(page + i);
>          |                            ^~~~~~~~~~~~~~~
>    mm/page_owner.c:226:26: warning: assignment to 'struct page_ext *' from 'int' makes pointer from integer without a cast [-Wint-conversion]
>      226 |                 page_ext = lookup_page_ext(page + i);
>          |                          ^
>    cc1: some warnings being treated as errors
>
>
> vim +/lookup_page_ext +226 mm/page_owner.c
>
>    213	
>    214	void __split_page_owner(struct page *page, int old_order, int new_order)
>    215	{
>    216		int i;
>    217		struct page_ext *page_ext = page_ext_get(page);
>    218		struct page_owner *page_owner;
>    219		unsigned int old_nr = 1 << old_order;
>    220		unsigned int new_nr = 1 << new_order;
>    221	
>    222		if (unlikely(!page_ext))
>    223			return;
>    224	
>    225		for (i = 0; i < old_nr; i += new_nr) {
>> 226			page_ext = lookup_page_ext(page + i);
>    227			page_owner = get_page_owner(page_ext);
>    228			page_owner->order = new_order;
>    229		}
>    230		page_ext_put(page_ext);
>    231	}
>    232	
>
> -- 
> 0-DAY CI Kernel Test Service
> https://github.com/intel/lkp-tests

It can be fixed by the patch below. I will fix it in the next version. Thanks.

diff --git a/mm/page_owner.c b/mm/page_owner.c
index 347861fe9c50..72244a4f1a31 100644
--- a/mm/page_owner.c
+++ b/mm/page_owner.c
@@ -223,9 +223,9 @@ void __split_page_owner(struct page *page, int old_order, int new_order)
                return;

        for (i = 0; i < old_nr; i += new_nr) {
-               page_ext = lookup_page_ext(page + i);
                page_owner = get_page_owner(page_ext);
                page_owner->order = new_order;
+               page_ext = page_ext_next(page_ext);
        }
        page_ext_put(page_ext);
 }


--
Best Regards,
Yan, Zi

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]

  reply	other threads:[~2023-03-29 13:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230329011712.3242298-5-zi.yan@sent.com>
2023-03-29  9:58 ` [PATCH v2 4/7] mm: page_owner: add support for splitting to any order in split page_owner kernel test robot
2023-03-29 13:16   ` Zi Yan [this message]
2023-03-29 14:48 ` kernel test robot
2023-03-29 16:11 ` kernel test robot

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=657AFA72-1604-4FFF-8F40-1B6CFB0B5061@nvidia.com \
    --to=ziy@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=cgroups@vger.kernel.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=mkoutny@suse.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=roman.gushchin@linux.dev \
    --cc=ryan.roberts@arm.com \
    --cc=shy828301@gmail.com \
    --cc=willy@infradead.org \
    --cc=yuzhao@google.com \
    --cc=zokeefe@google.com \
    /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).