linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: xiujianfeng <xiujianfeng@huawei.com>
To: kernel test robot <lkp@intel.com>, <akpm@linux-foundation.org>,
	<muchun.song@linux.dev>
Cc: <oe-kbuild-all@lists.linux.dev>, <linux-mm@kvack.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next 2/3] mm/hugetlb_cgroup: prepare cftypes based on template
Date: Tue, 4 Jun 2024 09:16:27 +0800	[thread overview]
Message-ID: <3b030437-4571-7a87-55e0-5fc3f5711a6e@huawei.com> (raw)
In-Reply-To: <202406040437.z2Iel9db-lkp@intel.com>



On 2024/6/4 5:25, kernel test robot wrote:
> Hi Xiu,
> 
> kernel test robot noticed the following build warnings:
> 
> [auto build test WARNING on akpm-mm/mm-everything]
> 
> url:    https://github.com/intel-lab-lkp/linux/commits/Xiu-Jianfeng/mm-hugetlb_cgroup-identify-the-legacy-using-cgroup_subsys_on_dfl/20240603-201513
> base:   https://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-everything
> patch link:    https://lore.kernel.org/r/20240603120506.1837322-3-xiujianfeng%40huawei.com
> patch subject: [PATCH -next 2/3] mm/hugetlb_cgroup: prepare cftypes based on template
> config: arm64-defconfig (https://download.01.org/0day-ci/archive/20240604/202406040437.z2Iel9db-lkp@intel.com/config)
> compiler: aarch64-linux-gcc (GCC) 13.2.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240604/202406040437.z2Iel9db-lkp@intel.com/reproduce)
> 
> If you fix the issue in a separate patch/commit (i.e. not just a new version of
> the same patch/commit), kindly add following tags
> | Reported-by: kernel test robot <lkp@intel.com>
> | Closes: https://lore.kernel.org/oe-kbuild-all/202406040437.z2Iel9db-lkp@intel.com/
> 
> All warnings (new ones prefixed by >>):
> 
>    mm/hugetlb_cgroup.c: In function 'hugetlb_cgroup_cfttypes_init':
>>> mm/hugetlb_cgroup.c:828:21: warning: the comparison will always evaluate as 'true' for the address of 'name' will never be NULL [-Waddress]
>      828 |                 if (tmpl->name)
>          |                     ^~~~
>    In file included from include/linux/cgroup.h:27,
>                     from mm/hugetlb_cgroup.c:20:
>    include/linux/cgroup-defs.h:605:14: note: 'name' declared here
>      605 |         char name[MAX_CFTYPE_NAME];
>          |              ^~~~
> 

Thanks, will fix in the next version.

> 
> vim +828 mm/hugetlb_cgroup.c
> 
>    814	
>    815	static void __init
>    816	hugetlb_cgroup_cfttypes_init(struct hstate *h, struct cftype *cft,
>    817				     struct cftype *tmpl, int tmpl_size)
>    818	{
>    819		char buf[32];
>    820		int i, idx = hstate_index(h);
>    821	
>    822		/* format the size */
>    823		mem_fmt(buf, sizeof(buf), huge_page_size(h));
>    824	
>    825		for (i = 0; i < tmpl_size; cft++, tmpl++, i++) {
>    826			*cft = *tmpl;
>    827			/* rebuild the name */
>  > 828			if (tmpl->name)
>    829				snprintf(cft->name, MAX_CFTYPE_NAME, "%s.%s", buf, tmpl->name);
>    830			/* rebuild the private */
>    831			if (tmpl->private)
>    832				cft->private = MEMFILE_PRIVATE(idx, tmpl->private);
>    833			/* rebuild the file_offset */
>    834			if (tmpl->file_offset) {
>    835				unsigned int offset = tmpl->file_offset;
>    836	
>    837				cft->file_offset = MEMFILE_OFFSET0(offset) +
>    838						   MEMFILE_FIELD_SIZE(offset) * idx;
>    839			}
>    840		}
>    841	}
>    842	
> 


  reply	other threads:[~2024-06-04  1:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 12:05 [PATCH -next 0/3] mm/hugetlb_cgroup: rework on cftypes Xiu Jianfeng
2024-06-03 12:05 ` [PATCH -next 1/3] mm/hugetlb_cgroup: identify the legacy using cgroup_subsys_on_dfl() Xiu Jianfeng
2024-06-03 12:05 ` [PATCH -next 2/3] mm/hugetlb_cgroup: prepare cftypes based on template Xiu Jianfeng
2024-06-03 15:36   ` kernel test robot
2024-06-03 21:25   ` kernel test robot
2024-06-04  1:16     ` xiujianfeng [this message]
2024-06-05  5:24   ` Dan Carpenter
2024-06-05  6:15     ` xiujianfeng
2024-06-03 12:05 ` [PATCH -next 3/3] mm/hugetlb_cgroup: switch to the new cftypes Xiu Jianfeng

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=3b030437-4571-7a87-55e0-5fc3f5711a6e@huawei.com \
    --to=xiujianfeng@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=muchun.song@linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox