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: [kkdwivedi:verifier/errors/v1 3/17] kernel/bpf/diagnostics.c:460:6: warning: stack frame size (1568) exceeds limit (1280) in 'bpf_diag_report_source'
Date: Tue, 09 Jun 2026 18:55:14 +0800	[thread overview]
Message-ID: <202606091810.k52hEnGe-lkp@intel.com> (raw)

tree:   https://github.com/kkdwivedi/linux verifier/errors/v1
head:   bd319f349f948035a4c5b93b96b109695d7eb130
commit: 8bd874a4c3f5883e1cb73c95ea735d2cfdf8f792 [3/17] bpf: Add source and instruction diagnostic context
config: hexagon-allmodconfig (https://download.01.org/0day-ci/archive/20260609/202606091810.k52hEnGe-lkp@intel.com/config)
compiler: clang version 23.0.0git (https://github.com/llvm/llvm-project 7917772d7d61384696c61102c08c2ea158e610fa)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260609/202606091810.k52hEnGe-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/202606091810.k52hEnGe-lkp@intel.com/

All warnings (new ones prefixed by >>):

   kernel/bpf/diagnostics.c:96:40: warning: diagnostic behavior may be improved by adding the 'format(printf, 2, 0)' attribute to the declaration of 'bpf_diag_vprint_indented' [-Wmissing-format-attribute]
      88 | static void bpf_diag_vprint_indented(struct bpf_verifier_env *env,
         | __attribute__((format(printf, 2, 0))) 
      89 |                                      const char *fmt, va_list args)
      90 | {
      91 |         char buf[1024];
      92 | 
      93 |         if (!bpf_verifier_log_needed(&env->log))
      94 |                 return;
      95 | 
      96 |         vscnprintf(buf, sizeof(buf), fmt, args);
         |                                               ^
   kernel/bpf/diagnostics.c:88:13: note: 'bpf_diag_vprint_indented' declared here
      88 | static void bpf_diag_vprint_indented(struct bpf_verifier_env *env,
         |             ^
   kernel/bpf/diagnostics.c:227:20: warning: diagnostic behavior may be improved by adding the 'format(printf, 2, 3)' attribute to the declaration of 'bpf_diag_insn_print' [-Wmissing-format-attribute]
     217 | static void bpf_diag_insn_print(void *private_data, const char *fmt, ...)
         | __attribute__((format(printf, 2, 3))) 
     218 | {
     219 |         struct bpf_diag_insn_buf *buf = private_data;
     220 |         va_list args;
     221 | 
     222 |         if (buf->len >= buf->size)
     223 |                 return;
     224 | 
     225 |         va_start(args, fmt);
     226 |         buf->len += vscnprintf(buf->buf + buf->len, buf->size - buf->len,
     227 |                                fmt, args);
         |                                         ^
   kernel/bpf/diagnostics.c:217:13: note: 'bpf_diag_insn_print' declared here
     217 | static void bpf_diag_insn_print(void *private_data, const char *fmt, ...)
         |             ^
>> kernel/bpf/diagnostics.c:460:6: warning: stack frame size (1568) exceeds limit (1280) in 'bpf_diag_report_source' [-Wframe-larger-than]
     460 | void bpf_diag_report_source(struct bpf_verifier_env *env, u32 insn_idx,
         |      ^
   3 warnings generated.


vim +/bpf_diag_report_source +460 kernel/bpf/diagnostics.c

   459	
 > 460	void bpf_diag_report_source(struct bpf_verifier_env *env, u32 insn_idx,

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

                 reply	other threads:[~2026-06-09 10:55 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=202606091810.k52hEnGe-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.