From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kunwu Chan <chentao@kylinos.cn>, tvrtko.ursulin@linux.intel.com
Cc: robdclark@chromium.org, andrzej.hajda@intel.com,
alan.previn.teres.alexis@intel.com, kunwu.chan@hotmail.com,
intel-gfx@lists.freedesktop.org, jonathan.cavitt@intel.com,
linux-kernel@vger.kernel.org, chris.p.wilson@intel.com,
rodrigo.vivi@intel.com, dri-devel@lists.freedesktop.org,
daniel@ffwll.ch, stable@vger.kernel.org, airlied@gmail.com
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Fix potential spectre vulnerability
Date: Fri, 3 Nov 2023 07:56:11 +0100 [thread overview]
Message-ID: <3d633ff6-e5e9-46bc-941a-258540ebbfc4@kernel.org> (raw)
In-Reply-To: <20231103023257.58199-1-chentao@kylinos.cn>
On 03/11/2023 03:32, Kunwu Chan wrote:
> Fix smatch warning:
> drivers/gpu/drm/i915/gem/i915_gem_context.c:847 set_proto_ctx_sseu()
> warn: potential spectre issue 'pc->user_engines' [r] (local cap)
>
> Fixes: d4433c7600f7 ("drm/i915/gem: Use the proto-context to handle create parameters (v5)")
> Cc: <stable@vger.kernel.org> # v5.15+
> Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
> Suggested-by: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Where did you receive this tag? There is nothing under link below.
> Link: https://lore.kernel.org/all/20231102101642.52988-1-chentao@kylinos.cn
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kunwu Chan <chentao@kylinos.cn>, tvrtko.ursulin@linux.intel.com
Cc: airlied@gmail.com, alan.previn.teres.alexis@intel.com,
andi.shyti@linux.intel.com, andrzej.hajda@intel.com,
chris.p.wilson@intel.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
jani.nikula@linux.intel.com, jonathan.cavitt@intel.com,
joonas.lahtinen@linux.intel.com, kunwu.chan@hotmail.com,
linux-kernel@vger.kernel.org, robdclark@chromium.org,
rodrigo.vivi@intel.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] drm/i915: Fix potential spectre vulnerability
Date: Fri, 3 Nov 2023 07:56:11 +0100 [thread overview]
Message-ID: <3d633ff6-e5e9-46bc-941a-258540ebbfc4@kernel.org> (raw)
In-Reply-To: <20231103023257.58199-1-chentao@kylinos.cn>
On 03/11/2023 03:32, Kunwu Chan wrote:
> Fix smatch warning:
> drivers/gpu/drm/i915/gem/i915_gem_context.c:847 set_proto_ctx_sseu()
> warn: potential spectre issue 'pc->user_engines' [r] (local cap)
>
> Fixes: d4433c7600f7 ("drm/i915/gem: Use the proto-context to handle create parameters (v5)")
> Cc: <stable@vger.kernel.org> # v5.15+
> Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
> Suggested-by: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Where did you receive this tag? There is nothing under link below.
> Link: https://lore.kernel.org/all/20231102101642.52988-1-chentao@kylinos.cn
Best regards,
Krzysztof
WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kunwu Chan <chentao@kylinos.cn>, tvrtko.ursulin@linux.intel.com
Cc: robdclark@chromium.org, andrzej.hajda@intel.com,
alan.previn.teres.alexis@intel.com, kunwu.chan@hotmail.com,
intel-gfx@lists.freedesktop.org, jonathan.cavitt@intel.com,
linux-kernel@vger.kernel.org, chris.p.wilson@intel.com,
rodrigo.vivi@intel.com, dri-devel@lists.freedesktop.org,
andi.shyti@linux.intel.com, stable@vger.kernel.org
Subject: Re: [PATCH v2] drm/i915: Fix potential spectre vulnerability
Date: Fri, 3 Nov 2023 07:56:11 +0100 [thread overview]
Message-ID: <3d633ff6-e5e9-46bc-941a-258540ebbfc4@kernel.org> (raw)
In-Reply-To: <20231103023257.58199-1-chentao@kylinos.cn>
On 03/11/2023 03:32, Kunwu Chan wrote:
> Fix smatch warning:
> drivers/gpu/drm/i915/gem/i915_gem_context.c:847 set_proto_ctx_sseu()
> warn: potential spectre issue 'pc->user_engines' [r] (local cap)
>
> Fixes: d4433c7600f7 ("drm/i915/gem: Use the proto-context to handle create parameters (v5)")
> Cc: <stable@vger.kernel.org> # v5.15+
> Signed-off-by: Kunwu Chan <chentao@kylinos.cn>
> Suggested-by: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Where did you receive this tag? There is nothing under link below.
> Link: https://lore.kernel.org/all/20231102101642.52988-1-chentao@kylinos.cn
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-11-03 6:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 10:16 [Intel-gfx] [PATCH] drm/i915: Fix potential spectre vulnerability chentao
2023-11-02 10:16 ` chentao
2023-11-02 10:16 ` chentao
2023-11-02 11:32 ` [Intel-gfx] " Tvrtko Ursulin
2023-11-02 11:32 ` Tvrtko Ursulin
2023-11-02 11:32 ` Tvrtko Ursulin
2023-11-03 0:07 ` [Intel-gfx] " Andi Shyti
2023-11-03 0:07 ` Andi Shyti
2023-11-03 0:07 ` Andi Shyti
2023-11-03 2:31 ` [Intel-gfx] " Kunwu Chan
2023-11-03 2:31 ` Kunwu Chan
2023-11-03 2:31 ` Kunwu Chan
2023-11-03 2:32 ` [Intel-gfx] [PATCH v2] " Kunwu Chan
2023-11-03 2:32 ` Kunwu Chan
2023-11-03 2:32 ` Kunwu Chan
2023-11-03 6:56 ` Krzysztof Kozlowski [this message]
2023-11-03 6:56 ` Krzysztof Kozlowski
2023-11-03 6:56 ` Krzysztof Kozlowski
2023-11-03 8:23 ` [Intel-gfx] " Tvrtko Ursulin
2023-11-03 8:23 ` Tvrtko Ursulin
2023-11-03 8:23 ` Tvrtko Ursulin
2023-11-06 9:57 ` [Intel-gfx] " Andi Shyti
2023-11-06 9:57 ` Andi Shyti
2023-11-06 9:57 ` Andi Shyti
2023-11-06 10:15 ` [Intel-gfx] " Tvrtko Ursulin
2023-11-06 10:15 ` Tvrtko Ursulin
2023-11-06 10:15 ` Tvrtko Ursulin
2023-11-06 21:59 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Fix potential spectre vulnerability (rev2) Patchwork
2023-11-06 22:13 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-11-07 6:56 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=3d633ff6-e5e9-46bc-941a-258540ebbfc4@kernel.org \
--to=krzk@kernel.org \
--cc=airlied@gmail.com \
--cc=alan.previn.teres.alexis@intel.com \
--cc=andrzej.hajda@intel.com \
--cc=chentao@kylinos.cn \
--cc=chris.p.wilson@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=kunwu.chan@hotmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=rodrigo.vivi@intel.com \
--cc=stable@vger.kernel.org \
--cc=tvrtko.ursulin@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 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.