From: "Niccolò Belli" <darkbasic@linuxsystems.it>
To: Bagas Sanjaya <bagasdotme@gmail.com>
Cc: Linux Regressions <regressions@lists.linux.dev>,
Qingqing Zhuo <qingqing.zhuo@amd.com>,
Daniel Wheeler <daniel.wheeler@amd.com>,
Fangzhi Zuo <Jerry.Zuo@amd.com>, Hersen Wu <hersenxs.wu@amd.com>,
Linux AMDGPU <amd-gfx@lists.freedesktop.org>,
Alex Deucher <alexander.deucher@amd.com>,
Linux for PowerPC <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Fwd: Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0)
Date: Thu, 11 May 2023 19:25:26 +0200 [thread overview]
Message-ID: <a50537d1f1af34104793218acb954a61@linuxsystems.it> (raw)
In-Reply-To: <3e5548e4-5a3e-9346-ec58-3617e1947186@gmail.com>
Il 2023-05-12 10:32 Bagas Sanjaya ha scritto:
> #regzbot introduced: f4f3b7dedbe849
> #regzbot link: https://gitlab.freedesktop.org/drm/amd/-/issues/2553
It doesn't look like the aforementioned patch made its way into 6.3 yet:
niko@talos2 ~/devel/linux-stable $ git branch
* linux-6.3.y
master
niko@talos2 ~/devel/linux-stable $ git show f4f3b7dedbe8 | patch -p1
patching file
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.c
Hunk #1 succeeded at 227 (offset 15 lines).
Hunk #2 succeeded at 269 with fuzz 2 (offset 19 lines).
patching file
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_mst_types.h
Hunk #1 succeeded at 49 with fuzz 2 (offset 15 lines).
next prev parent reply other threads:[~2023-05-12 22:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 8:06 Fwd: Linux 6.3.1 + AMD RX 570 on ppc64le 4K: Kernel attempted to read user page (1128) - exploit attempt? (uid: 0) Bagas Sanjaya
2023-05-12 4:10 ` Michael Ellerman
2023-05-12 8:32 ` Bagas Sanjaya
2023-05-11 17:25 ` Niccolò Belli [this message]
2023-05-12 15:16 ` Christophe Leroy
2023-05-12 15:17 ` Alex Deucher
2023-05-12 15:25 ` Christophe Leroy
2023-05-12 22:34 ` Greg Kroah-Hartman
2023-05-13 16:15 ` Alex Deucher
2023-05-21 11:21 ` Linux regression tracking #update (Thorsten Leemhuis)
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=a50537d1f1af34104793218acb954a61@linuxsystems.it \
--to=darkbasic@linuxsystems.it \
--cc=Jerry.Zuo@amd.com \
--cc=alexander.deucher@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=bagasdotme@gmail.com \
--cc=daniel.wheeler@amd.com \
--cc=hersenxs.wu@amd.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=qingqing.zhuo@amd.com \
--cc=regressions@lists.linux.dev \
/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