From: Will Deacon <will@kernel.org>
To: Nicolin Chen <nicolinc@nvidia.com>
Cc: catalin.marinas@arm.com, kernel-team@android.com,
Will Deacon <will@kernel.org>,
thierry.reding@gmail.com, vdumpa@nvidia.com,
robin.murphy@arm.com, joro@8bytes.org, jonathanh@nvidia.com,
linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev,
linux-kernel@vger.kernel.org, Jason Gunthorpe <jgg@ziepe.ca>
Subject: Re: [PATCH] iommu/tegra241-cmdqv: Fix -Wformat-truncation warnings in lvcmdq_error_header
Date: Mon, 2 Sep 2024 16:17:34 +0100 [thread overview]
Message-ID: <172527350346.3175637.9296819868165905950.b4-ty@kernel.org> (raw)
In-Reply-To: <20240902055745.629456-1-nicolinc@nvidia.com>
On Sun, 01 Sep 2024 22:57:45 -0700, Nicolin Chen wrote:
> Kernel test robot reported a few trucation warnings at the snprintf:
> drivers/iommu/arm/arm-smmu-v3/tegra241-cmdqv.c:
> In function ‘tegra241_vintf_free_lvcmdq’:
> drivers/iommu/arm/arm-smmu-v3/tegra241-cmdqv.c:239:56:
> warning: ‘%u’ directive output may be truncated writing between 1 and
> 5 bytes into a region of size between 3 and 11 [-Wformat-truncation=]
> 239 | snprintf(header, hlen, "VINTF%u: VCMDQ%u/LVCMDQ%u: ",
> | ^~
> drivers/iommu/arm/arm-smmu-v3/tegra241-cmdqv.c:239:32: note: directive argument
> in the range [0, 65535]
> 239 | snprintf(header, hlen, "VINTF%u: VCMDQ%u/LVCMDQ%u: ",
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> drivers/iommu/arm/arm-smmu-v3/tegra241-cmdqv.c:239:9: note: ‘snprintf’ output
> between 25 and 37 bytes into a destination of size 32
> 239 | snprintf(header, hlen, "VINTF%u: VCMDQ%u/LVCMDQ%u: ",
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> 240 | vcmdq->vintf->idx, vcmdq->idx, vcmdq->lidx);
>
> [...]
Applied to will (for-joerg/arm-smmu/updates), thanks!
[1/1] iommu/tegra241-cmdqv: Fix -Wformat-truncation warnings in lvcmdq_error_header
https://git.kernel.org/will/c/db184a1ced56
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2024-09-02 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-02 5:57 Nicolin Chen
2024-09-02 15:17 ` Will Deacon [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=172527350346.3175637.9296819868165905950.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=jonathanh@nvidia.com \
--cc=joro@8bytes.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=nicolinc@nvidia.com \
--cc=robin.murphy@arm.com \
--cc=thierry.reding@gmail.com \
--cc=vdumpa@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®