All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kees Cook <keescook@chromium.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC][PATCH] wifi: wil6210: Replace strlcat() usage with seq_buf
Date: Tue, 31 Oct 2023 11:50:45 +0800	[thread overview]
Message-ID: <202310311131.HryHNtzn-lkp@intel.com> (raw)
In-Reply-To: <20231026171349.work.928-kees@kernel.org>

Hi Kees,

[This is a private test report for your RFC patch.]
kernel test robot noticed the following build errors:

[auto build test ERROR on wireless-next/main]
[also build test ERROR on wireless/main kvalo-ath/ath-next linus/master v6.6 next-20231030]
[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#_base_tree_information]

url:    https://github.com/intel-lab-lkp/linux/commits/Kees-Cook/wifi-wil6210-Replace-strlcat-usage-with-seq_buf/20231027-011746
base:   https://git.kernel.org/pub/scm/linux/kernel/git/wireless/wireless-next.git main
patch link:    https://lore.kernel.org/r/20231026171349.work.928-kees%40kernel.org
patch subject: [RFC][PATCH] wifi: wil6210: Replace strlcat() usage with seq_buf
config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20231031/202310311131.HryHNtzn-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project.git 4a5ac14ee968ff0ad5d2cc1ffa0299048db4c88a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231031/202310311131.HryHNtzn-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/202310311131.HryHNtzn-lkp@intel.com/

All error/warnings (new ones prefixed by >>):

>> drivers/net/wireless/ath/wil6210/wmi.c:3162:57: warning: declaration of 'struct seq_buf' will not be visible outside of this function [-Wvisibility]
    3162 | static void resume_triggers2string(u32 triggers, struct seq_buf *s)
         |                                                         ^
>> drivers/net/wireless/ath/wil6210/wmi.c:3165:3: error: call to undeclared function 'seq_buf_puts'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    3165 |                 seq_buf_puts(s, " UNKNOWN");
         |                 ^
   drivers/net/wireless/ath/wil6210/wmi.c:3165:3: note: did you mean 'seq_puts'?
   include/linux/seq_file.h:121:6: note: 'seq_puts' declared here
     121 | void seq_puts(struct seq_file *m, const char *s);
         |      ^
   drivers/net/wireless/ath/wil6210/wmi.c:3170:3: error: call to undeclared function 'seq_buf_puts'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    3170 |                 seq_buf_puts(s, " HOST")
         |                 ^
>> drivers/net/wireless/ath/wil6210/wmi.c:3170:27: error: expected ';' after expression
    3170 |                 seq_buf_puts(s, " HOST")
         |                                         ^
         |                                         ;
>> drivers/net/wireless/ath/wil6210/wmi.c:3189:2: error: call to undeclared function 'DECLARE_SEQ_BUF'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    3189 |         DECLARE_SEQ_BUF(s, 100);
         |         ^
>> drivers/net/wireless/ath/wil6210/wmi.c:3189:18: error: use of undeclared identifier 's'
    3189 |         DECLARE_SEQ_BUF(s, 100);
         |                         ^
   drivers/net/wireless/ath/wil6210/wmi.c:3204:65: error: use of undeclared identifier 's'
    3204 |         resume_triggers2string(le32_to_cpu(reply.evt.resume_triggers), s);
         |                                                                        ^
>> drivers/net/wireless/ath/wil6210/wmi.c:3206:46: error: call to undeclared function 'seq_buf_cstr'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    3206 |                    reply.evt.status ? "failed" : "passed", seq_buf_cstr(s),
         |                                                            ^
   drivers/net/wireless/ath/wil6210/wmi.c:3206:59: error: use of undeclared identifier 's'
    3206 |                    reply.evt.status ? "failed" : "passed", seq_buf_cstr(s),
         |                                                                         ^
>> drivers/net/wireless/ath/wil6210/wmi.c:3206:46: error: call to undeclared function 'seq_buf_cstr'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
    3206 |                    reply.evt.status ? "failed" : "passed", seq_buf_cstr(s),
         |                                                            ^
   drivers/net/wireless/ath/wil6210/wmi.c:3206:59: error: use of undeclared identifier 's'
    3206 |                    reply.evt.status ? "failed" : "passed", seq_buf_cstr(s),
         |                                                                         ^
   1 warning and 10 errors generated.


vim +/seq_buf_puts +3165 drivers/net/wireless/ath/wil6210/wmi.c

  3161	
> 3162	static void resume_triggers2string(u32 triggers, struct seq_buf *s)
  3163	{
  3164		if (!triggers) {
> 3165			seq_buf_puts(s, " UNKNOWN");
  3166			return;
  3167		}
  3168	
  3169		if (triggers & WMI_RESUME_TRIGGER_HOST)
> 3170			seq_buf_puts(s, " HOST")
  3171	
  3172		if (triggers & WMI_RESUME_TRIGGER_UCAST_RX)
  3173			seq_buf_puts(s, " UCAST_RX");
  3174	
  3175		if (triggers & WMI_RESUME_TRIGGER_BCAST_RX)
  3176			seq_buf_puts(s, " BCAST_RX");
  3177	
  3178		if (triggers & WMI_RESUME_TRIGGER_WMI_EVT)
  3179			seq_buf_puts(s, " WMI_EVT");
  3180	
  3181		if (triggers & WMI_RESUME_TRIGGER_DISCONNECT)
  3182			seq_buf_puts(s, " DISCONNECT");
  3183	}
  3184	
  3185	int wmi_resume(struct wil6210_priv *wil)
  3186	{
  3187		struct wil6210_vif *vif = ndev_to_vif(wil->main_ndev);
  3188		int rc;
> 3189		DECLARE_SEQ_BUF(s, 100);
  3190		struct {
  3191			struct wmi_cmd_hdr wmi;
  3192			struct wmi_traffic_resume_event evt;
  3193		} __packed reply = {
  3194			.evt = {.status = WMI_TRAFFIC_RESUME_FAILED,
  3195				.resume_triggers =
  3196					cpu_to_le32(WMI_RESUME_TRIGGER_UNKNOWN)},
  3197		};
  3198	
  3199		rc = wmi_call(wil, WMI_TRAFFIC_RESUME_CMDID, vif->mid, NULL, 0,
  3200			      WMI_TRAFFIC_RESUME_EVENTID, &reply, sizeof(reply),
  3201			      WIL_WAIT_FOR_SUSPEND_RESUME_COMP);
  3202		if (rc)
  3203			return rc;
  3204		resume_triggers2string(le32_to_cpu(reply.evt.resume_triggers), s);
  3205		wil_dbg_pm(wil, "device resume %s, resume triggers:%s (0x%x)\n",
> 3206			   reply.evt.status ? "failed" : "passed", seq_buf_cstr(s),
  3207			   le32_to_cpu(reply.evt.resume_triggers));
  3208	
  3209		return reply.evt.status;
  3210	}
  3211	

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

      parent reply	other threads:[~2023-10-31  3:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26 17:13 [RFC][PATCH] wifi: wil6210: Replace strlcat() usage with seq_buf Kees Cook
2023-10-26 22:03 ` Justin Stitt
2023-10-31  3:50 ` kernel test robot [this message]

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=202310311131.HryHNtzn-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=keescook@chromium.org \
    --cc=llvm@lists.linux.dev \
    --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.