From: kernel test robot <lkp@intel.com>
To: Bill Wendling <morbo@google.com>
Cc: oe-kbuild-all@lists.linux.dev,
"Martin K. Petersen (Oracle)" <mkp@kernel.org>,
Mariia Nikitash <nikitash.mariiaw@gmail.com>,
Bart Van Assche <bvanassche@acm.org>
Subject: [linux-next:master 13578/15025] drivers/scsi/bfa/bfa_fcs.c:826:4: warning: '%s' directive output may be truncated writing up to 63 bytes into a region of size between 44 and 122
Date: Wed, 07 Oct 2026 20:51:51 +0200 [thread overview]
Message-ID: <202610072037.kjdagNH7-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: b018686719706a781c45a874ed51374a2dc4b767
commit: 0a5b53c1e7276ffacf5153d06d442c4d7ab0c41d [13578/15025] scsi: bfa: Use snprintf() in bfa_fcs_fabric_nsymb_init()
config: s390-randconfig-2001-20261006 (https://download.01.org/0day-ci/archive/20261007/202610072037.kjdagNH7-lkp@intel.com/config)
compiler: s390-linux-gcc (GCC) 8.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20261007/202610072037.kjdagNH7-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/202610072037.kjdagNH7-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/scsi/bfa/bfa_fcs.c: In function 'bfa_fcs_fabric_nsymb_init':
>> drivers/scsi/bfa/bfa_fcs.c:826:4: warning: '%s' directive output may be truncated writing up to 63 bytes into a region of size between 44 and 122 [-Wformat-truncation=]
"%s" BFA_FCS_PORT_SYMBNAME_SEPARATOR
^~~~
drivers/scsi/bfa/bfa_fcs.c:828:5: note: format string is defined here
"%s" BFA_FCS_PORT_SYMBNAME_SEPARATOR,
^~
drivers/scsi/bfa/bfa_fcs.c:825:2: note: 'snprintf' output between 10 and 151 bytes into a destination of size 128
snprintf(port_cfg->node_sym_name.symname, BFA_SYMNAME_MAXLEN,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"%s" BFA_FCS_PORT_SYMBNAME_SEPARATOR
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"%s" BFA_FCS_PORT_SYMBNAME_SEPARATOR
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"%s" BFA_FCS_PORT_SYMBNAME_SEPARATOR,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
model, (char *)driver_info->version,
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
driver_info->host_machine_name);
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +826 drivers/scsi/bfa/bfa_fcs.c
811
812 /*
813 * Node Symbolic Name Creation for base port and all vports
814 */
815 void
816 bfa_fcs_fabric_nsymb_init(struct bfa_fcs_fabric_s *fabric)
817 {
818 struct bfa_lport_cfg_s *port_cfg = &fabric->bport.port_cfg;
819 char model[BFA_ADAPTER_MODEL_NAME_LEN] = {0};
820 struct bfa_fcs_driver_info_s *driver_info = &fabric->fcs->driver_info;
821
822 bfa_ioc_get_adapter_model(&fabric->fcs->bfa->ioc, model);
823
824 /* Model name/number, Driver Version, Host machine name */
825 snprintf(port_cfg->node_sym_name.symname, BFA_SYMNAME_MAXLEN,
> 826 "%s" BFA_FCS_PORT_SYMBNAME_SEPARATOR
827 "%s" BFA_FCS_PORT_SYMBNAME_SEPARATOR
828 "%s" BFA_FCS_PORT_SYMBNAME_SEPARATOR,
829 model, (char *)driver_info->version,
830 driver_info->host_machine_name);
831 }
832
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-10-07 18:52 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=202610072037.kjdagNH7-lkp@intel.com \
--to=lkp@intel.com \
--cc=bvanassche@acm.org \
--cc=mkp@kernel.org \
--cc=morbo@google.com \
--cc=nikitash.mariiaw@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.