All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "Sasha Levin" <sashal@kernel.org>,
	"Linux Regressions" <regressions@lists.linux.dev>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Qingqing Zhuo" <qingqing.zhuo@amd.com>,
	"Fangzhi Zuo" <Jerry.Zuo@amd.com>,
	"Linux AMDGPU" <amd-gfx@lists.freedesktop.org>,
	"Daniel Wheeler" <daniel.wheeler@amd.com>,
	"Niccolò Belli" <darkbasic@linuxsystems.it>,
	"Hersen Wu" <hersenxs.wu@amd.com>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>,
	"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: Sat, 13 May 2023 07:34:33 +0900	[thread overview]
Message-ID: <2023051353-epiphany-retorted-4ad1@gregkh> (raw)
In-Reply-To: <57100be6-d379-0bc7-6d45-228cd46f9c81@csgroup.eu>

On Fri, May 12, 2023 at 03:25:47PM +0000, Christophe Leroy wrote:
> 
> 
> Le 12/05/2023 à 17:16, Christophe Leroy a écrit :
> > 
> > 
> > Le 11/05/2023 à 19:25, Niccolò Belli a écrit :
> >> [Vous ne recevez pas souvent de courriers de 
> >> darkbasic@linuxsystems.it. D?couvrez pourquoi ceci est important ? 
> >> https://aka.ms/LearnAboutSenderIdentification ]
> >>
> >> 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).
> > 
> > As far as I can see that patch has no Fixes: tag, so it will unlikely be 
> > automatically merged into stable.
> > 
> > Has anybody requested greg/sasha to get it into 6.3 ?
> > 
> 
> In fact, it seems that patch is already part of 6.3:
> 
> $ git tag --contains f4f3b7dedbe8
> v6.3
> v6.3-rc5
> v6.3-rc6
> v6.3-rc7
> v6.3.1
> v6.3.2
> v6.4-rc1

And that commit is already in the following releases:
	5.10.177 5.15.106 6.1.23 6.2.10 6.3

So what needs to be done here?

confused,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "Sasha Levin" <sashal@kernel.org>,
	"Linux Regressions" <regressions@lists.linux.dev>,
	"Qingqing Zhuo" <qingqing.zhuo@amd.com>,
	"Fangzhi Zuo" <Jerry.Zuo@amd.com>,
	"Linux AMDGPU" <amd-gfx@lists.freedesktop.org>,
	"Daniel Wheeler" <daniel.wheeler@amd.com>,
	"Niccolò Belli" <darkbasic@linuxsystems.it>,
	"Hersen Wu" <hersenxs.wu@amd.com>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>,
	"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: Sat, 13 May 2023 07:34:33 +0900	[thread overview]
Message-ID: <2023051353-epiphany-retorted-4ad1@gregkh> (raw)
In-Reply-To: <57100be6-d379-0bc7-6d45-228cd46f9c81@csgroup.eu>

On Fri, May 12, 2023 at 03:25:47PM +0000, Christophe Leroy wrote:
> 
> 
> Le 12/05/2023 à 17:16, Christophe Leroy a écrit :
> > 
> > 
> > Le 11/05/2023 à 19:25, Niccolò Belli a écrit :
> >> [Vous ne recevez pas souvent de courriers de 
> >> darkbasic@linuxsystems.it. D?couvrez pourquoi ceci est important ? 
> >> https://aka.ms/LearnAboutSenderIdentification ]
> >>
> >> 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).
> > 
> > As far as I can see that patch has no Fixes: tag, so it will unlikely be 
> > automatically merged into stable.
> > 
> > Has anybody requested greg/sasha to get it into 6.3 ?
> > 
> 
> In fact, it seems that patch is already part of 6.3:
> 
> $ git tag --contains f4f3b7dedbe8
> v6.3
> v6.3-rc5
> v6.3-rc6
> v6.3-rc7
> v6.3.1
> v6.3.2
> v6.4-rc1

And that commit is already in the following releases:
	5.10.177 5.15.106 6.1.23 6.2.10 6.3

So what needs to be done here?

confused,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: "Niccolò Belli" <darkbasic@linuxsystems.it>,
	"Bagas Sanjaya" <bagasdotme@gmail.com>,
	"Sasha Levin" <sashal@kernel.org>,
	"Linux Regressions" <regressions@lists.linux.dev>,
	"Linux for PowerPC" <linuxppc-dev@lists.ozlabs.org>,
	"Linux AMDGPU" <amd-gfx@lists.freedesktop.org>,
	"Michael Ellerman" <mpe@ellerman.id.au>,
	"Alex Deucher" <alexander.deucher@amd.com>,
	"Hersen Wu" <hersenxs.wu@amd.com>,
	"Qingqing Zhuo" <qingqing.zhuo@amd.com>,
	"Fangzhi Zuo" <Jerry.Zuo@amd.com>,
	"Daniel Wheeler" <daniel.wheeler@amd.com>
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: Sat, 13 May 2023 07:34:33 +0900	[thread overview]
Message-ID: <2023051353-epiphany-retorted-4ad1@gregkh> (raw)
In-Reply-To: <57100be6-d379-0bc7-6d45-228cd46f9c81@csgroup.eu>

On Fri, May 12, 2023 at 03:25:47PM +0000, Christophe Leroy wrote:
> 
> 
> Le 12/05/2023 à 17:16, Christophe Leroy a écrit :
> > 
> > 
> > Le 11/05/2023 à 19:25, Niccolò Belli a écrit :
> >> [Vous ne recevez pas souvent de courriers de 
> >> darkbasic@linuxsystems.it. D?couvrez pourquoi ceci est important ? 
> >> https://aka.ms/LearnAboutSenderIdentification ]
> >>
> >> 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).
> > 
> > As far as I can see that patch has no Fixes: tag, so it will unlikely be 
> > automatically merged into stable.
> > 
> > Has anybody requested greg/sasha to get it into 6.3 ?
> > 
> 
> In fact, it seems that patch is already part of 6.3:
> 
> $ git tag --contains f4f3b7dedbe8
> v6.3
> v6.3-rc5
> v6.3-rc6
> v6.3-rc7
> v6.3.1
> v6.3.2
> v6.4-rc1

And that commit is already in the following releases:
	5.10.177 5.15.106 6.1.23 6.2.10 6.3

So what needs to be done here?

confused,

greg k-h

  reply	other threads:[~2023-05-13 16:11 UTC|newest]

Thread overview: 28+ 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-11  8:06 ` Bagas Sanjaya
2023-05-11  8:06 ` Bagas Sanjaya
2023-05-12  4:10 ` Michael Ellerman
2023-05-12  4:10   ` Michael Ellerman
2023-05-12  4:10   ` Michael Ellerman
2023-05-12  8:32 ` Bagas Sanjaya
2023-05-12  8:32   ` Bagas Sanjaya
2023-05-12  8:32   ` Bagas Sanjaya
2023-05-11 17:25   ` Niccolò Belli
2023-05-11 17:25     ` Niccolò Belli
2023-05-11 17:25     ` Niccolò Belli
2023-05-12 15:16     ` Christophe Leroy
2023-05-12 15:16       ` Christophe Leroy
2023-05-12 15:16       ` Christophe Leroy
2023-05-12 15:17       ` Alex Deucher
2023-05-12 15:17         ` Alex Deucher
2023-05-12 15:17         ` Alex Deucher
2023-05-12 15:25       ` Christophe Leroy
2023-05-12 15:25         ` Christophe Leroy
2023-05-12 15:25         ` Christophe Leroy
2023-05-12 22:34         ` Greg Kroah-Hartman [this message]
2023-05-12 22:34           ` Greg Kroah-Hartman
2023-05-12 22:34           ` Greg Kroah-Hartman
2023-05-13 16:15           ` Alex Deucher
2023-05-13 16:15             ` Alex Deucher
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=2023051353-epiphany-retorted-4ad1@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=Jerry.Zuo@amd.com \
    --cc=alexander.deucher@amd.com \
    --cc=amd-gfx@lists.freedesktop.org \
    --cc=bagasdotme@gmail.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=daniel.wheeler@amd.com \
    --cc=darkbasic@linuxsystems.it \
    --cc=hersenxs.wu@amd.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=qingqing.zhuo@amd.com \
    --cc=regressions@lists.linux.dev \
    --cc=sashal@kernel.org \
    /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.