All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [RFC PATCH v2 1/2] rseq: x86: implement abort-at-ip extension
Date: Tue, 11 Jan 2022 13:31:08 +0800	[thread overview]
Message-ID: <202201111332.CweiXUcC-lkp@intel.com> (raw)
In-Reply-To: <20220110171611.8351-1-mathieu.desnoyers@efficios.com>

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

Hi Mathieu,

[FYI, it's a private test report for your RFC patch.]
[auto build test WARNING on shuah-kselftest/next]
[also build test WARNING on tip/x86/core tip/master linus/master v5.16 next-20220110]
[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/Mathieu-Desnoyers/rseq-x86-implement-abort-at-ip-extension/20220111-011941
base:   https://git.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest.git next
config: i386-randconfig-a011-20210930 (https://download.01.org/0day-ci/archive/20220111/202201111332.CweiXUcC-lkp(a)intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://github.com/0day-ci/linux/commit/8731a339925d9270b03a51b7c1b54e718dded248
        git remote add linux-review https://github.com/0day-ci/linux
        git fetch --no-tags linux-review Mathieu-Desnoyers/rseq-x86-implement-abort-at-ip-extension/20220111-011941
        git checkout 8731a339925d9270b03a51b7c1b54e718dded248
        # save the config file to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=i386 SHELL=/bin/bash arch/x86/kernel/

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

All warnings (new ones prefixed by >>):

>> arch/x86/kernel/ptrace.c:1372:5: warning: no previous prototype for 'rseq_abort_at_ip' [-Wmissing-prototypes]
    1372 | int rseq_abort_at_ip(struct pt_regs *regs, unsigned long ip)
         |     ^~~~~~~~~~~~~~~~


vim +/rseq_abort_at_ip +1372 arch/x86/kernel/ptrace.c

  1371	
> 1372	int rseq_abort_at_ip(struct pt_regs *regs, unsigned long ip)

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

  parent reply	other threads:[~2022-01-11  5:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-10 17:16 [RFC PATCH v2 1/2] rseq: x86: implement abort-at-ip extension Mathieu Desnoyers
2022-01-10 17:16 ` [RFC PATCH v2 2/2] selftests: rseq: test abort-at-ip extension on x86 Mathieu Desnoyers
2022-01-11  5:31 ` kernel test robot [this message]
2022-01-11 11:05 ` [RFC PATCH v2 1/2] rseq: x86: implement abort-at-ip extension Christian Brauner
2022-01-11 17:43   ` Mathieu Desnoyers
2022-01-12  8:46     ` Christian Brauner
2022-01-12 14:47       ` Mathieu Desnoyers
2022-01-12 14:55         ` Christian Brauner
2022-01-12 14:58         ` David Laight
2022-01-12 15:05           ` Mathieu Desnoyers
2022-01-12 15:15             ` David Laight
2022-01-12 15:24               ` Mathieu Desnoyers
2022-01-12 15:34               ` Peter Zijlstra
2022-01-12 15:53                 ` David Laight
2022-01-12 19:03 ` kernel test robot
2022-01-12 19:03   ` 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=202201111332.CweiXUcC-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.