From: Bommu Krishnaiah <krishnaiah.bommu@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Bommu Krishnaiah <krishnaiah.bommu@intel.com>
Subject: [PATCH v3 0/2] drm/xe : avoid the risky function sprintf
Date: Thu, 7 Dec 2023 06:58:38 +0530 [thread overview]
Message-ID: <20231207012840.48432-1-krishnaiah.bommu@intel.com> (raw)
These errors were highlighted by Static analyzer. Used snprintf instead of sprint.
Static analyzer Reported "Calling risky function (DC.STRING_BUFFER)”
v2: Removed hard coded values abd used sizeof()
v3: for sysfs used sysfs_emit over sprint
Bommu Krishnaiah (2):
drm/xe: prefer snprintf over sprintf
drm/xe/xe_hw_engine_class_sysfs: prefer sysfs_emit over sprintf for
sysfs
drivers/gpu/drm/xe/xe_debugfs.c | 2 +-
drivers/gpu/drm/xe/xe_exec_queue.c | 12 +++----
drivers/gpu/drm/xe/xe_gt_debugfs.c | 2 +-
drivers/gpu/drm/xe/xe_gt_idle.c | 4 +--
drivers/gpu/drm/xe/xe_hw_engine_class_sysfs.c | 36 +++++++++----------
drivers/gpu/drm/xe/xe_hw_fence.c | 2 +-
6 files changed, 29 insertions(+), 29 deletions(-)
--
2.25.1
next reply other threads:[~2024-03-22 9:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 1:28 Bommu Krishnaiah [this message]
2023-12-07 1:28 ` [PATCH v3 1/2] drm/xe: prefer snprintf over sprintf Bommu Krishnaiah
2024-03-22 9:49 ` Ghimiray, Himal Prasad
2023-12-07 1:28 ` [PATCH v3 2/2] drm/xe/xe_hw_engine_class_sysfs: prefer sysfs_emit over sprintf for sysfs Bommu Krishnaiah
2024-03-22 9:56 ` [PATCH v3 0/2] drm/xe : avoid the risky function sprintf Jani Nikula
2024-03-22 10:10 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-22 10:10 ` ✓ CI.checkpatch: " Patchwork
2024-03-22 10:11 ` ✓ CI.KUnit: " Patchwork
2024-03-22 10:24 ` ✓ CI.Build: " Patchwork
2024-03-22 10:26 ` ✓ CI.Hooks: " Patchwork
2024-03-22 10:28 ` ✓ CI.checksparse: " Patchwork
2024-03-22 11:01 ` ✓ CI.BAT: " Patchwork
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=20231207012840.48432-1-krishnaiah.bommu@intel.com \
--to=krishnaiah.bommu@intel.com \
--cc=intel-xe@lists.freedesktop.org \
/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