From: Pierre Gondois <pierre.gondois@arm.com>
To: Dan Carpenter <error27@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [bug report] arch_topology: Build cacheinfo from primary CPU
Date: Mon, 23 Jan 2023 17:20:11 +0100 [thread overview]
Message-ID: <32be7ef3-61d7-3f25-7e98-1e8bfc557737@arm.com> (raw)
In-Reply-To: <Y86rRxRCbel5xUE0@kadam>
On 1/23/23 16:44, Dan Carpenter wrote:
> On Mon, Jan 23, 2023 at 04:14:56PM +0100, Pierre Gondois wrote:
>> Hello Dan,
>> The 'levels' and 'split_levels' variables are initialized through their
>> addresses when necessary, so I believe the warning can be ignored.
>
> I don't understand what "initialized through their addresses when
> necessary" means. If you have CONFIG_ACPI_PPTT turned off as I do then
> acpi_get_cache_info() is a no-op so it's not initializing anything.
Ok yes indeed. I will send a fix shortly.
Sorry for the trouble,
Pierre
>
>>
>> If you still want to have the variables initialized, please let me know and I
>> will send a patch,
>
> I feel like I have this kind of discussion a lot. I don't know why
> people don't want to initialize their variables to zero.
>
> 1) It doesn't affect runtime on modern distros because they use the
> CONFIG_ option to zero stack variables.
>
> 2) If they don't then syzbot will detect it at runtime. It will probably
> take a year or two. That will set off a bunch of emails. Meanwhile
> you will have joined an exciting new start up and won't be around.
> No one else will remember how this code works.
>
> regards,
> dan carpenter
>
>
prev parent reply other threads:[~2023-01-23 16:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 15:07 [bug report] arch_topology: Build cacheinfo from primary CPU Dan Carpenter
2023-01-23 15:14 ` Pierre Gondois
2023-01-23 15:44 ` Dan Carpenter
2023-01-23 16:20 ` Pierre Gondois [this message]
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=32be7ef3-61d7-3f25-7e98-1e8bfc557737@arm.com \
--to=pierre.gondois@arm.com \
--cc=error27@gmail.com \
--cc=linux-acpi@vger.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.