From: Jocelyn Falempe <jfalempe@redhat.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: llvm@lists.linux.dev, Kees Cook <keescook@chromium.org>,
Tom Rix <trix@redhat.com>,
intel-gfx@lists.freedesktop.org,
Nick Desaulniers <ndesaulniers@google.com>,
patches@lists.linux.dev, Sami Tolvanen <samitolvanen@google.com>,
dri-devel@lists.freedesktop.org,
Andrzej Hajda <andrzej.hajda@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Fix CFI violations in gt_sysfs
Date: Fri, 13 Jan 2023 09:03:05 +0100 [thread overview]
Message-ID: <e54977a6-d767-7ea4-5259-d9735e5a68e9@redhat.com> (raw)
In-Reply-To: <Y8Atycuni0bl8std@dev-arch.thelio-3990X>
On 12/01/2023 16:56, Nathan Chancellor wrote:
> Hi Jocelyn,
>
> On Thu, Jan 12, 2023 at 11:08:17AM +0100, Jocelyn Falempe wrote:
>> This patch does also solve a kernel crash when reading
>> /sys/class/drm/card1/gt/gt0/* on a skylake machine:
>> https://bugzilla.redhat.com/show_bug.cgi?id=2154880
>
> Interesting, I wonder what aspect of this patch fixes this because I am
> not sure that is an intended consequence of this change but that is
> still good to hear!
I wasn't able to find the root cause, but basically the kobj pointer
given in the sysfs callback, is not the good one on this machine, so it
either return garbage or crash.
By chance I found this patch, tried it, and it solves the issue.
>
> For the record, this is commit a8a4f0467d70 ("drm/i915: Fix CFI
> violations in gt_sysfs") in mainline.
>
>> Do you think it can be backported to stable releases ?
>> Conflicts are trivial on top of v6.0 at least.
>
> I had a report from another user of this crash affecting them with kCFI
> so it is on my TODO to backport it to 6.1 (6.0 just went EOL) but I am
> currently out of the office until next Wednesday so I won't be able to
> get to it until then (as I would like to test the backport on affected
> hardware). If someone wants to beat me to it, I won't complain ;)
Thanks for taking care of it, I will wait next week then.
>
> Cheers,
> Nathan
>
--
Jocelyn
prev parent reply other threads:[~2023-01-13 8:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-13 20:59 [Intel-gfx] [PATCH v2] drm/i915: Fix CFI violations in gt_sysfs Nathan Chancellor
2022-10-13 22:13 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Fix CFI violations in gt_sysfs (rev3) Patchwork
2022-10-13 22:33 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-14 3:39 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-18 18:14 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Fix CFI violations in gt_sysfs (rev4) Patchwork
2022-10-18 18:32 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-10-27 17:17 ` [Intel-gfx] [PATCH v2] drm/i915: Fix CFI violations in gt_sysfs Andi Shyti
2023-01-12 10:08 ` Jocelyn Falempe
2023-01-12 15:56 ` Nathan Chancellor
2023-01-13 8:03 ` Jocelyn Falempe [this message]
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=e54977a6-d767-7ea4-5259-d9735e5a68e9@redhat.com \
--to=jfalempe@redhat.com \
--cc=andrzej.hajda@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=keescook@chromium.org \
--cc=llvm@lists.linux.dev \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=patches@lists.linux.dev \
--cc=rodrigo.vivi@intel.com \
--cc=samitolvanen@google.com \
--cc=trix@redhat.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