[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1ba43657-2730-46eb-a6b9-8e316b35fa02@icloud.com>
Date: Fri, 23 Aug 2024 08:38:35 +0800
From: Zijun Hu <zijun_hu@...oud.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Dmitry Torokhov <dmitry.torokhov@...il.com>, linux-kernel@...r.kernel.org,
Zijun Hu <quic_zijuhu@...cinc.com>, stable@...r.kernel.org
Subject: Re: [PATCH] driver core: Fix an uninitialized variable is used by
__device_attach()
On 2024/8/23 08:14, Greg Kroah-Hartman wrote:
> On Fri, Aug 23, 2024 at 07:46:09AM +0800, Zijun Hu wrote:
>> From: Zijun Hu <quic_zijuhu@...cinc.com>
>>
>> An uninitialized variable @data.have_async may be used as analyzed
>> by the following inline comments:
>>
>> static int __device_attach(struct device *dev, bool allow_async)
>> {
>> // if @allow_async is true.
>>
>> ...
>> struct device_attach_data data = {
>> .dev = dev,
>> .check_async = allow_async,
>> .want_async = false,
>> };
>> // @data.have_async is not initialized.
>
> As Dmitry said, this is incorrect, please fix your broken code analysis
> tool, it is obviously not working properly :(
>
let us slow down firstly to confirm if what Dmitry said is right firstly.
it is not related to any analysis tool, i notice it by reading code.
> thanks,
>
> greg k-h
Powered by blists - more mailing lists