Re: [PATCH 4.19 1/1] drm/amdkfd: Check for null pointer after calling kmemdup

2023-01-05 Thread Greg KH
On Wed, Jan 04, 2023 at 08:05:57PM +0200, Dragos-Marian Panait wrote: > > On 04.01.2023 16:48, Greg KH wrote: > > On Wed, Jan 04, 2023 at 09:35:03AM -0500, Alex Deucher wrote: > > > On Wed, Jan 4, 2023 at 8:23 AM Christian König > > > wrote: > > > > Am 04.01.23 um 13:41 schrieb Greg KH: > > > >

Re: [PATCH 4.19 1/1] drm/amdkfd: Check for null pointer after calling kmemdup

2023-01-04 Thread Dragos-Marian Panait
On 04.01.2023 16:48, Greg KH wrote: On Wed, Jan 04, 2023 at 09:35:03AM -0500, Alex Deucher wrote: On Wed, Jan 4, 2023 at 8:23 AM Christian König wrote: Am 04.01.23 um 13:41 schrieb Greg KH: On Tue, Jan 03, 2023 at 08:43:08PM +0200, Dragos-Marian Panait wrote: From: Jiasheng Jiang [

Re: [PATCH 4.19 1/1] drm/amdkfd: Check for null pointer after calling kmemdup

2023-01-04 Thread Greg KH
On Wed, Jan 04, 2023 at 09:35:03AM -0500, Alex Deucher wrote: > On Wed, Jan 4, 2023 at 8:23 AM Christian König > wrote: > > > > Am 04.01.23 um 13:41 schrieb Greg KH: > > > On Tue, Jan 03, 2023 at 08:43:08PM +0200, Dragos-Marian Panait wrote: > > >> From: Jiasheng Jiang > > >> > > >> [ Upstream

Re: [PATCH 4.19 1/1] drm/amdkfd: Check for null pointer after calling kmemdup

2023-01-04 Thread Alex Deucher
On Wed, Jan 4, 2023 at 8:23 AM Christian König wrote: > > Am 04.01.23 um 13:41 schrieb Greg KH: > > On Tue, Jan 03, 2023 at 08:43:08PM +0200, Dragos-Marian Panait wrote: > >> From: Jiasheng Jiang > >> > >> [ Upstream commit abfaf0eee97925905e742aa3b0b72e04a918fa9e ] > >> > >> As the possible

Re: [PATCH 4.19 1/1] drm/amdkfd: Check for null pointer after calling kmemdup

2023-01-04 Thread Christian König
Am 04.01.23 um 13:41 schrieb Greg KH: On Tue, Jan 03, 2023 at 08:43:08PM +0200, Dragos-Marian Panait wrote: From: Jiasheng Jiang [ Upstream commit abfaf0eee97925905e742aa3b0b72e04a918fa9e ] As the possible failure of the allocation, kmemdup() may return NULL pointer. Therefore, it should be

Re: [PATCH 4.19 1/1] drm/amdkfd: Check for null pointer after calling kmemdup

2023-01-04 Thread Greg KH
On Tue, Jan 03, 2023 at 08:43:08PM +0200, Dragos-Marian Panait wrote: > From: Jiasheng Jiang > > [ Upstream commit abfaf0eee97925905e742aa3b0b72e04a918fa9e ] > > As the possible failure of the allocation, kmemdup() may return NULL > pointer. > Therefore, it should be better to check the

[PATCH 4.19 1/1] drm/amdkfd: Check for null pointer after calling kmemdup

2023-01-04 Thread Dragos-Marian Panait
From: Jiasheng Jiang [ Upstream commit abfaf0eee97925905e742aa3b0b72e04a918fa9e ] As the possible failure of the allocation, kmemdup() may return NULL pointer. Therefore, it should be better to check the 'props2' in order to prevent the dereference of NULL pointer. Fixes: 3a87177eb141