From: Borislav Petkov <bp@alien8.de>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: tony.luck@intel.com, james.morse@arm.com, Dave.Martin@arm.com,
babu.moger@amd.com, tglx@linutronix.de,
dave.hansen@linux.intel.com, x86@kernel.org, hpa@zytor.com,
ben.horgan@arm.com, fustini@kernel.org, fenghuay@nvidia.com,
peternewman@google.com, linux-kernel@vger.kernel.org,
patches@lists.linux.dev
Subject: Re: [PATCH v3 03/13] fs/resctrl: Avoid "may be used uninitialized" warning
Date: Wed, 8 Apr 2026 00:19:08 +0200 [thread overview]
Message-ID: <20260407221908.GGadWC3BaUzStnu9Z5@fat_crate.local> (raw)
In-Reply-To: <e89edbdb-b6a4-453f-99da-41991ad25712@intel.com>
On Tue, Apr 07, 2026 at 01:50:50PM -0700, Reinette Chatre wrote:
> Indeed. This patch is for developer and maintenance convenience and not required for
> resctrl health. No problem from me if you find it not to be appropriate. I will just
> continue to parse the warning out of the logs.
Oh, your call. I just think it is unnecessary especially because those
warnings are not really worth to care for as they produce a bunch of false
positives and that's why they're not enabled by default.
IOW, I take them with a grain of salt.
In this particular case, I would care about the code not doing any unnecessary
work if it can be helped. And the warning can take a hike... :-)
But I can apply the patch if you prefer.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2026-04-07 22:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-07 16:01 [PATCH v3 00/13] x86,fs/resctrl: Improve resctrl quality and consistency Reinette Chatre
2026-04-07 16:01 ` [PATCH v3 01/13] MAINTAINERS: Update resctrl entry Reinette Chatre
2026-04-07 16:01 ` [PATCH v3 02/13] fs/resctrl: Add missing return value descriptions Reinette Chatre
2026-04-07 16:02 ` [PATCH v3 03/13] fs/resctrl: Avoid "may be used uninitialized" warning Reinette Chatre
2026-04-07 18:55 ` Borislav Petkov
2026-04-07 20:50 ` Reinette Chatre
2026-04-07 22:19 ` Borislav Petkov [this message]
2026-04-07 22:56 ` Reinette Chatre
2026-04-07 16:02 ` [PATCH v3 04/13] fs/resctrl: Use correct format specifier for printing error pointers Reinette Chatre
2026-04-07 16:02 ` [PATCH v3 05/13] x86/resctrl: Protect against bad shift Reinette Chatre
2026-04-08 16:37 ` Reinette Chatre
2026-04-07 16:02 ` [PATCH v3 06/13] fs/resctrl: Change pattern used to track number of entries in enum Reinette Chatre
2026-04-07 16:02 ` [PATCH v3 07/13] fs/resctrl: Use accurate type for rdt_resource::rid Reinette Chatre
2026-04-07 16:02 ` [PATCH v3 08/13] fs/resctrl: Pass error reading event through to user space Reinette Chatre
2026-04-07 16:02 ` [PATCH v3 09/13] fs/resctrl: Add last_cmd_status support for writes to max_threshold_occupancy Reinette Chatre
2026-04-07 16:02 ` [PATCH v3 10/13] fs/resctrl: Use accurate and symmetric exit flows Reinette Chatre
2026-04-07 16:02 ` [PATCH v3 11/13] fs/resctrl: Change last_cmd_status custom during input parsing Reinette Chatre
2026-04-07 16:02 ` [PATCH v3 12/13] fs/resctrl: Communicate resource group deleted error via last_cmd_status Reinette Chatre
2026-04-07 16:02 ` [PATCH v3 13/13] fs/resctrl: Inform user space when status buffer overflowed Reinette Chatre
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=20260407221908.GGadWC3BaUzStnu9Z5@fat_crate.local \
--to=bp@alien8.de \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=ben.horgan@arm.com \
--cc=dave.hansen@linux.intel.com \
--cc=fenghuay@nvidia.com \
--cc=fustini@kernel.org \
--cc=hpa@zytor.com \
--cc=james.morse@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@lists.linux.dev \
--cc=peternewman@google.com \
--cc=reinette.chatre@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®