linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Sumit Semwal <sumit.semwal@linaro.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Jonathan Corbet <corbet@lwn.net>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org, Kees Cook <keescook@chromium.org>,
	Michal Hocko <mhocko@suse.com>, Colin Cross <ccross@google.com>
Subject: Re: [PATCH v6 3/3] mm: add a field to store names for private anonymous memory
Date: Tue, 1 Sep 2020 21:31:00 +0800	[thread overview]
Message-ID: <202009012106.erdERj7U%lkp@intel.com> (raw)
In-Reply-To: <20200901091901.19779-4-sumit.semwal@linaro.org>

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

Hi Sumit,

I love your patch! Yet something to improve:

[auto build test ERROR on linus/master]
[also build test ERROR on v5.9-rc3]
[cannot apply to hnaz-linux-mm/master linux/master next-20200828]
[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]

url:    https://github.com/0day-ci/linux/commits/Sumit-Semwal/Anonymous-VMA-naming-patches/20200901-172131
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git b51594df17d0ce80b9f9f35394a1f42d7ac94472
config: m68k-randconfig-s032-20200901 (attached as .config)
compiler: m68k-linux-gcc (GCC) 9.3.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # apt-get install sparse
        # sparse version: v0.6.2-191-g10164920-dirty
        # save the attached .config to linux build tree
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__' ARCH=m68k 

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 >>):

   m68k-linux-ld: kernel/sys.o: in function `prctl_set_vma':
>> kernel/sys.c:2294: undefined reference to `madvise_set_anon_name'

# https://github.com/0day-ci/linux/commit/aff01cd66b017fe09b1a449d66c8988bcc5960b9
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Sumit-Semwal/Anonymous-VMA-naming-patches/20200901-172131
git checkout aff01cd66b017fe09b1a449d66c8988bcc5960b9
vim +2294 kernel/sys.c

  2282	
  2283	#ifdef CONFIG_MMU
  2284	static int prctl_set_vma(unsigned long opt, unsigned long addr,
  2285				 unsigned long len, unsigned long arg)
  2286	{
  2287		struct mm_struct *mm = current->mm;
  2288		int error;
  2289	
  2290		mmap_write_lock(mm);
  2291	
  2292		switch (opt) {
  2293		case PR_SET_VMA_ANON_NAME:
> 2294			error = madvise_set_anon_name(addr, len, arg);
  2295			break;
  2296		default:
  2297			error = -EINVAL;
  2298		}
  2299	
  2300		mmap_write_unlock(mm);
  2301	
  2302		return error;
  2303	}
  2304	#else /* CONFIG_MMU */
  2305	static int prctl_set_vma(unsigned long opt, unsigned long start,
  2306				 unsigned long len_in, unsigned long arg)
  2307	{
  2308		return -EINVAL;
  2309	}
  2310	#endif
  2311	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 24492 bytes --]

  reply	other threads:[~2020-09-01 13:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01  9:18 [PATCH v6 0/3] Anonymous VMA naming patches Sumit Semwal
2020-09-01  9:18 ` [PATCH v6 1/3] mm: rearrange madvise code to allow for reuse Sumit Semwal
2020-09-01  9:19 ` [PATCH v6 2/3] mm: memory: Add access_remote_vm_locked variant Sumit Semwal
2020-09-01  9:19 ` [PATCH v6 3/3] mm: add a field to store names for private anonymous memory Sumit Semwal
2020-09-01 13:31   ` kernel test robot [this message]
2020-09-01 14:48   ` 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=202009012106.erdERj7U%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=ccross@google.com \
    --cc=corbet@lwn.net \
    --cc=kbuild-all@lists.01.org \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mchehab@kernel.org \
    --cc=mhocko@suse.com \
    --cc=sumit.semwal@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox