The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>,
	catalin.marinas@arm.com, will@kernel.org, oleg@redhat.com,
	tglx@linutronix.de, peterz@infradead.org, luto@kernel.org,
	kees@kernel.org, wad@chromium.org, charlie@rivosinc.com,
	macro@orcam.me.uk, deller@gmx.de, akpm@linux-foundation.org,
	ldv@strace.io, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, ruanjinjie@huawei.com
Subject: Re: [PATCH -next v6 08/10] entry: Add arch_ptrace_report_syscall_entry/exit()
Date: Wed, 17 Sep 2025 16:27:47 +0800	[thread overview]
Message-ID: <202509171609.V2opqAfm-lkp@intel.com> (raw)
In-Reply-To: <20250916082611.2972008-9-ruanjinjie@huawei.com>

Hi Jinjie,

kernel test robot noticed the following build warnings:

[auto build test WARNING on next-20250915]

url:    https://github.com/intel-lab-lkp/linux/commits/Jinjie-Ruan/arm64-ptrace-Split-report_syscall-into-report_syscall_enter-exit/20250916-163202
base:   next-20250915
patch link:    https://lore.kernel.org/r/20250916082611.2972008-9-ruanjinjie%40huawei.com
patch subject: [PATCH -next v6 08/10] entry: Add arch_ptrace_report_syscall_entry/exit()
config: i386-buildonly-randconfig-001-20250917 (https://download.01.org/0day-ci/archive/20250917/202509171609.V2opqAfm-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250917/202509171609.V2opqAfm-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/202509171609.V2opqAfm-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> Warning: kernel/entry/syscall-common.c:29 function parameter 'regs' not described in 'arch_ptrace_report_syscall_entry'
>> Warning: kernel/entry/syscall-common.c:115 function parameter 'regs' not described in 'arch_ptrace_report_syscall_exit'
>> Warning: kernel/entry/syscall-common.c:115 function parameter 'step' not described in 'arch_ptrace_report_syscall_exit'

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

  reply	other threads:[~2025-09-17  8:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-16  8:26 [PATCH -next v6 00/10] arm64: entry: Convert to generic entry Jinjie Ruan
2025-09-16  8:26 ` [PATCH -next v6 01/10] arm64/ptrace: Split report_syscall() into report_syscall_enter/exit() Jinjie Ruan
2025-09-16  8:26 ` [PATCH -next v6 02/10] arm64/ptrace: Refactor syscall_trace_enter/exit() Jinjie Ruan
2025-09-16  8:26 ` [PATCH -next v6 03/10] arm64/ptrace: Refator el0_svc_common() Jinjie Ruan
2025-09-16  8:26 ` [PATCH -next v6 04/10] entry: Extract syscall_exit_to_user_mode_prepare() helper Jinjie Ruan
2025-09-16  8:26 ` [PATCH -next v6 05/10] arm64/ptrace: Handle ptrace_report_syscall_entry() error Jinjie Ruan
2025-09-16  8:26 ` [PATCH -next v6 06/10] arm64/ptrace: Rework secure_computing() in syscall_trace_enter() Jinjie Ruan
2025-09-16  8:26 ` [PATCH -next v6 07/10] arm64/ptrace: Use syscall_get_arguments() heleper Jinjie Ruan
2025-09-16  8:26 ` [PATCH -next v6 08/10] entry: Add arch_ptrace_report_syscall_entry/exit() Jinjie Ruan
2025-09-17  8:27   ` kernel test robot [this message]
2025-09-16  8:26 ` [PATCH -next v6 09/10] entry: Add has_syscall_work() helper Jinjie Ruan
2025-09-16  8:26 ` [PATCH -next v6 10/10] arm64: entry: Convert to generic entry Jinjie Ruan
2025-09-16 14:46   ` kemal
2025-09-17  1:55     ` Jinjie Ruan
2025-09-17 13:14       ` kemal
2025-09-18  9:52   ` kernel test robot
2025-10-10  0:59 ` [PATCH -next v6 00/10] " Jinjie Ruan

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=202509171609.V2opqAfm-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=catalin.marinas@arm.com \
    --cc=charlie@rivosinc.com \
    --cc=deller@gmx.de \
    --cc=kees@kernel.org \
    --cc=ldv@strace.io \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=macro@orcam.me.uk \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=ruanjinjie@huawei.com \
    --cc=tglx@linutronix.de \
    --cc=wad@chromium.org \
    --cc=will@kernel.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