Linux-Next Archive on
 help / color / Atom feed
From: coverity-bot <>
To: Manasi Navare <>
Cc: Maarten Lankhorst <>,
	"Gustavo A. R. Silva" <>,
Subject: Coverity: intel_set_dp_tp_ctl_normal(): Memory - illegal accesses
Date: Mon, 28 Oct 2019 16:05:40 -0700
Message-ID: <201910281605.5595C8C@keescook> (raw)


This is an experimental automated report about issues detected by Coverity
from a scan of next-20191025 as part of the linux-next weekly scan project:

You're getting this email because you were associated with the identified
lines of code (noted below) that were touched by recent commits:

eadf6f9170d5 ("drm/i915/display/icl: Enable master-slaves in trans port sync")

Coverity reported the following:

*** CID 1487364:  Memory - illegal accesses  (UNINIT)
/drivers/gpu/drm/i915/display/intel_display.c: 14249 in intel_set_dp_tp_ctl_normal()
14243     	int i;
14245     	for_each_new_connector_in_state(&state->base, conn, conn_state, i) {
14246     		if (conn_state->crtc == &crtc->base)
14247     			break;
14248     	}
vvv     CID 1487364:  Memory - illegal accesses  (UNINIT)
vvv     Using uninitialized value "conn" when calling "intel_attached_encoder".
14249     	intel_dp = enc_to_intel_dp(&intel_attached_encoder(conn)->base);
14250     	intel_dp_stop_link_train(intel_dp);
14251     }
14253     static void intel_post_crtc_enable_updates(struct intel_crtc *crtc,
14254     					   struct intel_atomic_state *state)

If this is a false positive, please let us know so we can mark it as
such, or teach the Coverity rules to be smarter. If not, please make
sure fixes get into linux-next. :) For patches fixing this, please

Reported-by: coverity-bot <>
Addresses-Coverity-ID: 1487364 ("Memory - illegal accesses")
Fixes: eadf6f9170d5 ("drm/i915/display/icl: Enable master-slaves in trans port sync")

Thanks for your attention!


                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201910281605.5595C8C@keescook \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-Next Archive on

Archives are clonable:
	git clone --mirror linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ \
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone