linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Beau Belgrave <beaub@linux.microsoft.com>,
	rostedt@goodmis.org, mhiramat@kernel.org
Cc: kbuild-all@lists.01.org, linux-trace-devel@vger.kernel.org,
	linux-kernel@vger.kernel.org, beaub@linux.microsoft.com
Subject: Re: [PATCH v3] user_events: Enable user processes to create and write to trace events
Date: Tue, 26 Oct 2021 08:46:36 +0800	[thread overview]
Message-ID: <202110260812.wr9WmBwy-lkp@intel.com> (raw)
In-Reply-To: <20211018230957.3032-1-beaub@linux.microsoft.com>

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

Hi Beau,

Thank you for the patch! Yet something to improve:

[auto build test ERROR on tip/perf/core]
[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/Beau-Belgrave/user_events-Enable-user-processes-to-create-and-write-to-trace-events/20211019-071039
base:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git 79df45731da68772d2285265864a52c900b8c65f
config: mips-allyesconfig (attached as .config)
compiler: mips-linux-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
        wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
        chmod +x ~/bin/make.cross
        # https://github.com/0day-ci/linux/commit/c165bf4b91374ac0ffac76a9f93be466d37a5545
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Beau-Belgrave/user_events-Enable-user-processes-to-create-and-write-to-trace-events/20211019-071039
        git checkout c165bf4b91374ac0ffac76a9f93be466d37a5545
        # save the attached .config to linux build tree
        mkdir build_dir
        COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross O=build_dir ARCH=mips SHELL=/bin/bash

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

   kernel/trace/trace_events_user.c: In function 'user_status_mmap':
>> kernel/trace/trace_events_user.c:880:38: error: 'PAGE_READONLY' undeclared (first use in this function); did you mean 'MNT_READONLY'?
     880 |                                size, PAGE_READONLY);
         |                                      ^~~~~~~~~~~~~
         |                                      MNT_READONLY
   kernel/trace/trace_events_user.c:880:38: note: each undeclared identifier is reported only once for each function it appears in
   kernel/trace/trace_events_user.c:881:1: error: control reaches end of non-void function [-Werror=return-type]
     881 | }
         | ^
   cc1: some warnings being treated as errors


vim +880 kernel/trace/trace_events_user.c

   867	
   868	/*
   869	 * Maps the shared page into the user process for checking if event is enabled.
   870	 */
   871	static int user_status_mmap(struct file *file, struct vm_area_struct *vma)
   872	{
   873		unsigned long size = vma->vm_end - vma->vm_start;
   874	
   875		if (size != MAX_EVENTS)
   876			return -EINVAL;
   877	
   878		return remap_pfn_range(vma, vma->vm_start,
   879				       virt_to_phys(register_page_data) >> PAGE_SHIFT,
 > 880				       size, PAGE_READONLY);
   881	}
   882	

---
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: 70961 bytes --]

      parent reply	other threads:[~2021-10-26  0:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-18 23:09 [PATCH v3] user_events: Enable user processes to create and write to trace events Beau Belgrave
2021-10-22 13:38 ` Masami Hiramatsu
2021-10-22 22:42   ` Beau Belgrave
2021-10-25  1:40     ` Masami Hiramatsu
2021-10-25 17:26       ` Beau Belgrave
2021-10-26  8:26         ` Masami Hiramatsu
2021-10-27 19:14           ` Beau Belgrave
2021-10-26  0:46 ` kernel test robot [this message]

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=202110260812.wr9WmBwy-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=beaub@linux.microsoft.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=rostedt@goodmis.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;
as well as URLs for NNTP newsgroup(s).