linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: kbuild-all@01.org, Mark Brown <broonie@kernel.org>,
	Mike Rapoport <rppt@linux.ibm.com>,
	Vincenzo Frascino <vincenzo.frascino@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Kees Cook <keescook@chromium.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [linux-next:master 13879/13946] fs/userfaultfd.c:1279:32: error: expected ')' before ';' token
Date: Fri, 27 Sep 2019 06:51:55 +0800	[thread overview]
Message-ID: <201909270651.REkimBOW%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   d47175169c28eedd2cc2ab8c01f38764cb0269cc
commit: c4da82d89ea3e689304f0ef783907dd23903b470 [13879/13946] userfaultfd: untag user pointers
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-gcc (GCC) 7.4.0
reproduce:
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        git checkout c4da82d89ea3e689304f0ef783907dd23903b470
        # save the attached .config to linux build tree
        GCC_VERSION=7.4.0 make.cross ARCH=sparc64 

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

All error/warnings (new ones prefixed by >>):

   fs/userfaultfd.c: In function 'validate_range':
>> fs/userfaultfd.c:1279:32: error: expected ')' before ';' token
     *start = untagged_addr(*start);
                                   ^
>> fs/userfaultfd.c:1294:1: error: expected ';' before '}' token
    }
    ^
   fs/userfaultfd.c:1277:8: warning: unused variable 'task_size' [-Wunused-variable]
     __u64 task_size = mm->task_size;
           ^~~~~~~~~
>> fs/userfaultfd.c:1294:1: warning: no return statement in function returning non-void [-Wreturn-type]
    }
    ^

vim +1279 fs/userfaultfd.c

  1273	
  1274	static __always_inline int validate_range(struct mm_struct *mm,
  1275						  __u64 *start, __u64 len)
  1276	{
  1277		__u64 task_size = mm->task_size;
  1278	
> 1279		*start = untagged_addr(*start);
  1280	
  1281		if (*start & ~PAGE_MASK)
  1282			return -EINVAL;
  1283		if (len & ~PAGE_MASK)
  1284			return -EINVAL;
  1285		if (!len)
  1286			return -EINVAL;
  1287		if (*start < mmap_min_addr)
  1288			return -EINVAL;
  1289		if (*start >= task_size)
  1290			return -EINVAL;
  1291		if (len > task_size - *start)
  1292			return -EINVAL;
  1293		return 0;
> 1294	}
  1295	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

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

                 reply	other threads:[~2019-09-26 22:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=201909270651.REkimBOW%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=andreyknvl@google.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=kbuild-all@01.org \
    --cc=keescook@chromium.org \
    --cc=linux-mm@kvack.org \
    --cc=rppt@linux.ibm.com \
    --cc=vincenzo.frascino@arm.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).