mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: York Jasper Niebuhr <yjnworkstation@gmail.com>,
	akpm@linux-foundation.org
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
	York Jasper Niebuhr <yjnworkstation@gmail.com>
Subject: Re: [PATCH] mm: exitz syscall
Date: Sat, 11 Nov 2023 05:40:06 +0800	[thread overview]
Message-ID: <202311110549.g5gj4ZVU-lkp@intel.com> (raw)
In-Reply-To: <20231110184720.39780-1-yjnworkstation@gmail.com>

Hi York,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 8728c14129df7a6e29188a2e737b4774fb200953]

url:    https://github.com/intel-lab-lkp/linux/commits/York-Jasper-Niebuhr/mm-exitz-syscall/20231111-031729
base:   8728c14129df7a6e29188a2e737b4774fb200953
patch link:    https://lore.kernel.org/r/20231110184720.39780-1-yjnworkstation%40gmail.com
patch subject: [PATCH] mm: exitz syscall
config: loongarch-randconfig-001-20231111 (https://download.01.org/0day-ci/archive/20231111/202311110549.g5gj4ZVU-lkp@intel.com/config)
compiler: loongarch64-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231111/202311110549.g5gj4ZVU-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/202311110549.g5gj4ZVU-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> kernel/exitz.c:73:6: warning: no previous prototype for 'exit_memz' [-Wmissing-prototypes]
      73 | void exit_memz(void)
         |      ^~~~~~~~~


vim +/exit_memz +73 kernel/exitz.c

    69	
    70	/*
    71	 * Overwrite any memory associated to current process with zeros.
    72	 */
  > 73	void exit_memz(void)
    74	{
    75		if (!(current->ezflags & EZ_MEM))
    76			return;
    77	
    78		struct vm_area_struct *vma;
    79	
    80		VMA_ITERATOR(vmi, current->mm, 0);
    81	
    82		for_each_vma(vmi, vma) {
    83			memz_range(vma->vm_start, vma->vm_end);
    84		}
    85	}
    86	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  reply	other threads:[~2023-11-10 21:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-10 18:47 York Jasper Niebuhr
2023-11-10 21:40 ` kernel test robot [this message]
2023-11-10 22:35 ` 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=202311110549.g5gj4ZVU-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=yjnworkstation@gmail.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

all inboxes | Powered by JetHome®