From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Release connector iterator on a digital port conflict.
Date: Thu, 15 Feb 2018 15:38:26 -0800 [thread overview]
Message-ID: <20180215233826.GA3621@intel.com> (raw)
In-Reply-To: <20180215091425.42364-1-maarten.lankhorst@linux.intel.com>
On Thu, Feb 15, 2018 at 10:14:25AM +0100, Maarten Lankhorst wrote:
> <4>[ 30.702366] ================================================
> <4>[ 30.702383] WARNING: lock held when returning to user space!
> <4>[ 30.702404] 4.16.0-rc1-CI-kasan_1+ #1 Tainted: G W
> <4>[ 30.702422] ------------------------------------------------
> <4>[ 30.702440] kms_3d/1439 is leaving the kernel with locks still held!
> <4>[ 30.702459] 1 lock held by kms_3d/1439:
> <4>[ 30.702472] #0: (drm_connector_list_iter){.+.+}, at: [<000000003745d183>] intel_atomic_check+0x1d9d/0x3ff0 [i915]
>
> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Reported-by: Chris Wilson <chris@chris-wilson.co.uk>
> ---
> drivers/gpu/drm/i915/intel_display.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index 3eb4c4b2e0e0..9f9656c9cfbe 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -10635,6 +10635,7 @@ static bool check_digital_port_conflicts(struct drm_atomic_state *state)
> struct drm_connector_list_iter conn_iter;
> unsigned int used_ports = 0;
> unsigned int used_mst_ports = 0;
> + bool ret = true;
>
> /*
> * Walk the connector list instead of the encoder
> @@ -10669,7 +10670,7 @@ static bool check_digital_port_conflicts(struct drm_atomic_state *state)
>
> /* the same port mustn't appear more than once */
2 eDPs?!
anyways seems that we do have to end the iteration.
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
> if (used_ports & port_mask)
> - return false;
> + ret = false;
>
> used_ports |= port_mask;
> break;
> @@ -10687,7 +10688,7 @@ static bool check_digital_port_conflicts(struct drm_atomic_state *state)
> if (used_ports & used_mst_ports)
> return false;
>
> - return true;
> + return ret;
> }
>
> static void
> --
> 2.16.1
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-02-15 23:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-15 9:14 [PATCH] drm/i915: Release connector iterator on a digital port conflict Maarten Lankhorst
2018-02-15 9:23 ` Chris Wilson
2018-02-15 9:23 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-02-15 9:39 ` ✗ Fi.CI.BAT: failure " Patchwork
2018-02-15 10:20 ` ✗ Fi.CI.CHECKPATCH: warning " Patchwork
2018-02-15 10:34 ` ✓ Fi.CI.BAT: success " Patchwork
2018-02-15 15:31 ` ✗ Fi.CI.IGT: warning " Patchwork
2018-02-15 16:50 ` ✓ Fi.CI.IGT: success " Patchwork
2018-02-15 23:38 ` Rodrigo Vivi [this message]
2018-02-19 10:00 ` [PATCH] " Maarten Lankhorst
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=20180215233826.GA3621@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.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