All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jiri Olsa <jolsa@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [jolsa-perf:bpf/optimized_usdt_13 12/18] arch/x86/kernel/uprobes.c:317:12: warning: 'is_call_insn' defined but not used
Date: Wed, 29 Jan 2025 21:21:18 +0800	[thread overview]
Message-ID: <202501292124.eb934HOp-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git bpf/optimized_usdt_13
head:   a264266ebd33899155a0cf37feac0ef4e300cec0
commit: 4f491bb5453694500c4681edd76e1843c8f4de4e [12/18] uprobes/x86: Add support to optimize uprobes
config: i386-randconfig-r063-20250129 (https://download.01.org/0day-ci/archive/20250129/202501292124.eb934HOp-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250129/202501292124.eb934HOp-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/202501292124.eb934HOp-lkp@intel.com/

All warnings (new ones prefixed by >>):

>> arch/x86/kernel/uprobes.c:317:12: warning: 'is_call_insn' defined but not used [-Wunused-function]
     317 | static int is_call_insn(uprobe_opcode_t *insn)
         |            ^~~~~~~~~~~~
   arch/x86/kernel/uprobes.c:312:12: warning: 'is_nop5_insn' defined but not used [-Wunused-function]
     312 | static int is_nop5_insn(uprobe_opcode_t *insn)
         |            ^~~~~~~~~~~~


vim +/is_call_insn +317 arch/x86/kernel/uprobes.c

   316	
 > 317	static int is_call_insn(uprobe_opcode_t *insn)
   318	{
   319		return *insn == CALL_INSN_OPCODE;
   320	}
   321	

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

                 reply	other threads:[~2025-01-29 13:22 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=202501292124.eb934HOp-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=jolsa@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.