From: kernel test robot <lkp@intel.com>
To: Aya Levin <ayal@nvidia.com>
Cc: oe-kbuild-all@lists.linux.dev, linux-kernel@vger.kernel.org,
Saeed Mahameed <saeedm@nvidia.com>,
Eran Ben Elisha <eranbe@nvidia.com>,
Tariq Toukan <tariqt@nvidia.com>
Subject: drivers/net/ethernet/mellanox/mlx5/core/en/reporter_rx.c:573:46: warning: '%s' directive output may be truncated writing up to 255 bytes into a region of size between 220 and 230
Date: Wed, 18 Oct 2023 21:16:23 +0800 [thread overview]
Message-ID: <202310182137.AlBjalaw-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
head: 06dc10eae55b5ceabfef287a7e5f16ceea204aa0
commit: 521f31af004ade74963d551a719a36ca7df0ba70 net/mlx5e: Allow RQ outside of channel context
date: 2 years, 10 months ago
config: x86_64-randconfig-001-20230913 (https://download.01.org/0day-ci/archive/20231018/202310182137.AlBjalaw-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/20231018/202310182137.AlBjalaw-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/202310182137.AlBjalaw-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/net/ethernet/mellanox/mlx5/core/en/reporter_rx.c: In function 'mlx5e_reporter_rx_timeout':
>> drivers/net/ethernet/mellanox/mlx5/core/en/reporter_rx.c:573:46: warning: '%s' directive output may be truncated writing up to 255 bytes into a region of size between 220 and 230 [-Wformat-truncation=]
573 | "RX timeout on channel: %d, %sRQ: 0x%x, CQ: 0x%x",
| ^~
574 | rq->ix, icosq_str, rq->rqn, rq->cq.mcq.cqn);
| ~~~~~~~~~
drivers/net/ethernet/mellanox/mlx5/core/en/reporter_rx.c:572:9: note: 'snprintf' output between 43 and 322 bytes into a destination of size 256
572 | snprintf(err_str, sizeof(err_str),
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
573 | "RX timeout on channel: %d, %sRQ: 0x%x, CQ: 0x%x",
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
574 | rq->ix, icosq_str, rq->rqn, rq->cq.mcq.cqn);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +573 drivers/net/ethernet/mellanox/mlx5/core/en/reporter_rx.c
557
558 void mlx5e_reporter_rx_timeout(struct mlx5e_rq *rq)
559 {
560 char icosq_str[MLX5E_REPORTER_PER_Q_MAX_LEN] = {};
561 char err_str[MLX5E_REPORTER_PER_Q_MAX_LEN];
562 struct mlx5e_icosq *icosq = rq->icosq;
563 struct mlx5e_priv *priv = rq->priv;
564 struct mlx5e_err_ctx err_ctx = {};
565
566 err_ctx.ctx = rq;
567 err_ctx.recover = mlx5e_rx_reporter_timeout_recover;
568 err_ctx.dump = mlx5e_rx_reporter_dump_rq;
569
570 if (icosq)
571 snprintf(icosq_str, sizeof(icosq_str), "ICOSQ: 0x%x, ", icosq->sqn);
572 snprintf(err_str, sizeof(err_str),
> 573 "RX timeout on channel: %d, %sRQ: 0x%x, CQ: 0x%x",
574 rq->ix, icosq_str, rq->rqn, rq->cq.mcq.cqn);
575
576 mlx5e_health_report(priv, priv->rx_reporter, err_str, &err_ctx);
577 }
578
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-18 13:16 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=202310182137.AlBjalaw-lkp@intel.com \
--to=lkp@intel.com \
--cc=ayal@nvidia.com \
--cc=eranbe@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®