All of lore.kernel.org
 help / color / mirror / Atom feed
From: Suraj Kandpal <suraj.kandpal@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: chaitanya.kumar.borah@intel.com, Suraj Kandpal <suraj.kandpal@intel.com>
Subject: [PATCH 1/2] drm/i915/display: Initialize capability variables
Date: Mon,  1 Apr 2024 08:31:05 +0530	[thread overview]
Message-ID: <20240401030106.274787-2-suraj.kandpal@intel.com> (raw)
In-Reply-To: <20240401030106.274787-1-suraj.kandpal@intel.com>

Initialize HDCP capability variables to false to avoid UBSAN
warning in boolean value as some functions invoking this could
return without filling the two capability values.

--v2
-Fix Typo [Chaitanya]

Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
---
 drivers/gpu/drm/i915/display/intel_display_debugfs.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/gpu/drm/i915/display/intel_display_debugfs.c b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
index b99c024b0934..95d14dab089e 100644
--- a/drivers/gpu/drm/i915/display/intel_display_debugfs.c
+++ b/drivers/gpu/drm/i915/display/intel_display_debugfs.c
@@ -191,7 +191,7 @@ static void intel_hdcp_info(struct seq_file *m,
 			    struct intel_connector *intel_connector,
 			    bool remote_req)
 {
-	bool hdcp_cap, hdcp2_cap;
+	bool hdcp_cap = false, hdcp2_cap = false;
 
 	if (!intel_connector->hdcp.shim) {
 		seq_puts(m, "No Connector Support");
-- 
2.43.2


  reply	other threads:[~2024-04-01  3:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01  3:01 [PATCH 0/2] Fix UBSAN warning in hdcp_info Suraj Kandpal
2024-04-01  3:01 ` Suraj Kandpal [this message]
2024-04-01  3:01 ` [PATCH 2/2] drm/i915/hdcp: Fix get remote hdcp capability function Suraj Kandpal
2024-04-01  5:42   ` Borah, Chaitanya Kumar
2024-04-01  5:56   ` Suraj Kandpal
2024-04-01  9:50     ` Borah, Chaitanya Kumar
2024-04-01  9:25   ` kernel test robot
2024-04-01  3:29 ` ✗ Fi.CI.SPARSE: warning for Fix UBSAN warning in hdcp_info (rev2) Patchwork
2024-04-01  3:39 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-01  5:26 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-01  7:35 ` ✗ Fi.CI.SPARSE: warning for Fix UBSAN warning in hdcp_info (rev3) Patchwork
2024-04-01  7:55 ` ✓ Fi.CI.BAT: success " Patchwork
2024-04-01 13:39 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-04-02 21:18 ` ✓ Fi.CI.IGT: success " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2024-03-27  4:44 [PATCH 0/2] Fix UBSAN warning in hdcp_info Suraj Kandpal
2024-03-27  4:44 ` [PATCH 1/2] drm/i915/display: Initialize capability variables Suraj Kandpal
2024-03-28 10:22   ` Borah, Chaitanya Kumar

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=20240401030106.274787-2-suraj.kandpal@intel.com \
    --to=suraj.kandpal@intel.com \
    --cc=chaitanya.kumar.borah@intel.com \
    --cc=intel-gfx@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 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.