All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kumar Kartikeya Dwivedi <memxor@gmail.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: Re: [PATCH bpf-next v1 03/11] bpf: Add function to extract program source info
Date: Thu, 8 May 2025 18:30:35 +0800	[thread overview]
Message-ID: <202505081842.Tgphc4hq-lkp@intel.com> (raw)
In-Reply-To: <20250507171720.1958296-4-memxor@gmail.com>

Hi Kumar,

kernel test robot noticed the following build warnings:

[auto build test WARNING on 43745d11bfd9683abdf08ad7a5cc403d6a9ffd15]

url:    https://github.com/intel-lab-lkp/linux/commits/Kumar-Kartikeya-Dwivedi/bpf-Introduce-bpf_dynptr_from_mem_slice/20250508-012020
base:   43745d11bfd9683abdf08ad7a5cc403d6a9ffd15
patch link:    https://lore.kernel.org/r/20250507171720.1958296-4-memxor%40gmail.com
patch subject: [PATCH bpf-next v1 03/11] bpf: Add function to extract program source info
config: x86_64-defconfig (https://download.01.org/0day-ci/archive/20250508/202505081842.Tgphc4hq-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250508/202505081842.Tgphc4hq-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/202505081842.Tgphc4hq-lkp@intel.com/

All warnings (new ones prefixed by >>):

   In file included from include/linux/bitmap.h:13,
                    from include/linux/cpumask.h:12,
                    from arch/x86/include/asm/cpumask.h:5,
                    from arch/x86/include/asm/msr.h:11,
                    from arch/x86/include/asm/tsc.h:10,
                    from arch/x86/include/asm/timex.h:6,
                    from include/linux/timex.h:67,
                    from include/linux/time32.h:13,
                    from include/linux/time.h:60,
                    from include/linux/jiffies.h:10,
                    from include/linux/ktime.h:25,
                    from include/linux/timer.h:6,
                    from include/linux/workqueue.h:9,
                    from include/linux/bpf.h:10,
                    from include/linux/filter.h:9,
                    from kernel/bpf/core.c:21:
   In function 'kbasename',
       inlined from 'bpf_prog_get_file_line' at kernel/bpf/core.c:3240:11:
>> include/linux/string.h:387:28: warning: argument 1 null where non-null expected [-Wnonnull]
     387 |         const char *tail = strrchr(path, '/');
         |                            ^~~~~~~~~~~~~~~~~~
   kernel/bpf/core.c: In function 'bpf_prog_get_file_line':
   include/linux/string.h:183:15: note: in a call to function 'strrchr' declared 'nonnull'
     183 | extern char * strrchr(const char *,int);
         |               ^~~~~~~


vim +387 include/linux/string.h

639b9e34f15e4b Akinobu Mita    2012-07-30  379  
b18888ab256f05 Andy Shevchenko 2012-12-17  380  /**
b18888ab256f05 Andy Shevchenko 2012-12-17  381   * kbasename - return the last part of a pathname.
b18888ab256f05 Andy Shevchenko 2012-12-17  382   *
b18888ab256f05 Andy Shevchenko 2012-12-17  383   * @path: path to extract the filename from.
b18888ab256f05 Andy Shevchenko 2012-12-17  384   */
b18888ab256f05 Andy Shevchenko 2012-12-17  385  static inline const char *kbasename(const char *path)
b18888ab256f05 Andy Shevchenko 2012-12-17  386  {
b18888ab256f05 Andy Shevchenko 2012-12-17 @387  	const char *tail = strrchr(path, '/');
b18888ab256f05 Andy Shevchenko 2012-12-17  388  	return tail ? tail + 1 : path;
b18888ab256f05 Andy Shevchenko 2012-12-17  389  }
b18888ab256f05 Andy Shevchenko 2012-12-17  390  

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

  reply	other threads:[~2025-05-08 10:30 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07 17:17 [PATCH bpf-next v1 00/11] BPF Standard Streams Kumar Kartikeya Dwivedi
2025-05-07 17:17 ` [PATCH bpf-next v1 01/11] bpf: Introduce bpf_dynptr_from_mem_slice Kumar Kartikeya Dwivedi
2025-05-09 17:19   ` Eduard Zingerman
2025-05-09 21:11   ` Andrii Nakryiko
2025-05-07 17:17 ` [PATCH bpf-next v1 02/11] bpf: Introduce BPF standard streams Kumar Kartikeya Dwivedi
2025-05-08 23:54   ` Eduard Zingerman
2025-05-09  0:10     ` Kumar Kartikeya Dwivedi
2025-05-07 17:17 ` [PATCH bpf-next v1 03/11] bpf: Add function to extract program source info Kumar Kartikeya Dwivedi
2025-05-08 10:30   ` kernel test robot [this message]
2025-05-08 20:15   ` Eduard Zingerman
2025-05-08 23:32     ` Kumar Kartikeya Dwivedi
2025-05-09 21:17   ` Andrii Nakryiko
2025-05-07 17:17 ` [PATCH bpf-next v1 04/11] bpf: Add function to find program from stack trace Kumar Kartikeya Dwivedi
2025-05-08 23:07   ` Eduard Zingerman
2025-05-08 23:29     ` Kumar Kartikeya Dwivedi
2025-05-07 17:17 ` [PATCH bpf-next v1 05/11] bpf: Add dump_stack() analogue to print to BPF stderr Kumar Kartikeya Dwivedi
2025-05-08 22:38   ` Eduard Zingerman
2025-05-08 23:29     ` Kumar Kartikeya Dwivedi
2025-05-07 17:17 ` [PATCH bpf-next v1 06/11] bpf: Report may_goto timeout " Kumar Kartikeya Dwivedi
2025-05-08 12:53   ` kernel test robot
2025-05-09  6:22   ` Eduard Zingerman
2025-05-09  9:19   ` Alan Maguire
2025-05-07 17:17 ` [PATCH bpf-next v1 07/11] bpf: Report rqspinlock deadlocks/timeout " Kumar Kartikeya Dwivedi
2025-05-07 17:17 ` [PATCH bpf-next v1 08/11] bpf: Report arena faults " Kumar Kartikeya Dwivedi
2025-05-09 19:28   ` Eduard Zingerman
2025-05-09 20:01     ` Kumar Kartikeya Dwivedi
2025-05-09 20:07       ` Eduard Zingerman
2025-05-09 20:10         ` Kumar Kartikeya Dwivedi
2025-05-09 20:17           ` Eduard Zingerman
2025-05-07 17:17 ` [PATCH bpf-next v1 09/11] libbpf: Add bpf_stream_printk() macro Kumar Kartikeya Dwivedi
2025-05-08 23:31   ` Eduard Zingerman
2025-05-08 23:33     ` Kumar Kartikeya Dwivedi
2025-05-09  6:16       ` Eduard Zingerman
2025-05-09 21:28         ` Andrii Nakryiko
2025-05-08 23:41   ` Alexei Starovoitov
2025-05-08 23:48     ` Kumar Kartikeya Dwivedi
2025-05-08 23:50       ` Kumar Kartikeya Dwivedi
2025-05-09 21:26   ` Andrii Nakryiko
2025-05-07 17:17 ` [PATCH bpf-next v1 10/11] bpftool: Add support for dumping streams Kumar Kartikeya Dwivedi
2025-05-08 10:41   ` Quentin Monnet
2025-05-08 23:41     ` Kumar Kartikeya Dwivedi
2025-05-09  6:21   ` Eduard Zingerman
2025-05-09 17:31     ` Alexei Starovoitov
2025-05-09 18:31       ` Eduard Zingerman
2025-05-09 18:48         ` Alexei Starovoitov
2025-05-09 19:37           ` Eduard Zingerman
2025-05-09 19:50             ` Kumar Kartikeya Dwivedi
2025-05-09 21:33           ` Andrii Nakryiko
2025-05-12 20:51             ` Kumar Kartikeya Dwivedi
2025-05-12 21:35               ` Andrii Nakryiko
2025-05-12 21:50               ` Alexei Starovoitov
2025-05-12 21:56                 ` Kumar Kartikeya Dwivedi
2025-05-12 22:07                   ` Alexei Starovoitov
2025-05-07 17:17 ` [PATCH bpf-next v1 11/11] selftests/bpf: Add tests for prog streams Kumar Kartikeya Dwivedi
2025-05-09 17:18   ` Eduard Zingerman

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=202505081842.Tgphc4hq-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=memxor@gmail.com \
    --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.