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

Subject: Re: [PATCH 5.10 1/1] drm/amdkfd: Check for null pointer after calling kmemdup
From: Christian König <christian.koenig@xxxxxxx>
Date: Thu, 19 Jan 2023 12:49:02 +0100
In-reply-to: <Y8ka2khSlK6E/XbF@phenom.ffwll.local>
References: <20230104175633.1420151-1-dragos.panait@windriver.com> <20230104175633.1420151-2-dragos.panait@windriver.com> <Y8ABeXQLzWdoaGAY@kroah.com> <CAKMK7uEgzJU8ukgR3sQtSUB5+wrD9VyMwCHOA-SReFWd0tKzzw@mail.gmail.com> <Y8A5NgtGLDJv4sON@kroah.com> <Y8ka2khSlK6E/XbF@phenom.ffwll.local>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2

Am 19.01.23 um 11:26 schrieb Daniel Vetter:

[SNIP]
I guess next step is that people will use chatgpt to write the patches for
these bugs.

To be honest I think that would result in quite some improvement in theaverage patch quality.

That guessing this AI does has at least a statistically proven chance tobe correct.


Cheers,
Christian.

References:
- [PATCH 5.10 0/1] drm/amdkfd: Check for null pointer after calling kmemdup
  - From: Dragos-Marian Panait
- [PATCH 5.10 1/1] drm/amdkfd: Check for null pointer after calling kmemdup
  - From: Dragos-Marian Panait
- Re: [PATCH 5.10 1/1] drm/amdkfd: Check for null pointer after calling kmemdup
  - From: Greg KH
- Re: [PATCH 5.10 1/1] drm/amdkfd: Check for null pointer after calling kmemdup
  - From: Daniel Vetter
- Re: [PATCH 5.10 1/1] drm/amdkfd: Check for null pointer after calling kmemdup
  - From: Greg KH
- Re: [PATCH 5.10 1/1] drm/amdkfd: Check for null pointer after calling kmemdup
  - From: Daniel Vetter