From: Reinette Chatre <reinette.chatre@intel.com>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: <james.morse@arm.com>, <Dave.Martin@arm.com>,
<babu.moger@amd.com>, <bp@alien8.de>, <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 v4 08/10] fs/resctrl: Change last_cmd_status custom during input parsing
Date: Thu, 28 May 2026 20:44:59 -0700 [thread overview]
Message-ID: <62975502-3d07-40ee-8ceb-c906a8c55c5c@intel.com> (raw)
In-Reply-To: <ahjR2CeEwosKXSE9@agluck-desk3>
Hi Tony,
On 5/28/26 4:38 PM, Luck, Tony wrote:
> On Wed, Apr 29, 2026 at 08:06:38AM -0700, Reinette Chatre wrote:
>> @@ -324,6 +319,15 @@ ssize_t rdtgroup_schemata_write(struct kernfs_open_file *of,
>> }
>> rdt_last_cmd_clear();
>>
>> + /* Valid input requires a trailing newline */
>> + if (nbytes == 0 || buf[nbytes - 1] != '\n') {
>> + rdt_last_cmd_puts("Invalid input\n");
>
> This is obviously a big improvement over existing failure to provide a
> message (or leaving previous stale message). Do you want to go the extra
> mile and disambiguate all these "Invalid input" messages? E.g. here:
>
> rdt_last_cmd_puts("schemata: Invalid input\n");
>
> It's good to have a grep-able pattern to diagnostics.
Good point. Will do.
>
> All the other patches in this series look great. You can add my
>
> Reviewed-by: Tony Luck <tony.luck@intel.com>
Thank you very much for taking a look.
Reinette
next prev parent reply other threads:[~2026-05-29 3:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 15:06 [PATCH v4 00/10] x86,fs/resctrl: Improve resctrl quality and consistency Reinette Chatre
2026-04-29 15:06 ` [PATCH v4 01/10] fs/resctrl: Use correct format specifier for printing error pointers Reinette Chatre
2026-04-29 15:06 ` [PATCH v4 02/10] x86/resctrl: Protect against bad shift Reinette Chatre
2026-04-29 15:06 ` [PATCH v4 03/10] fs/resctrl: Change pattern used to track number of entries in enum Reinette Chatre
2026-04-29 15:06 ` [PATCH v4 04/10] fs/resctrl: Use accurate type for rdt_resource::rid Reinette Chatre
2026-04-29 15:06 ` [PATCH v4 05/10] fs/resctrl: Pass error reading event through to user space Reinette Chatre
2026-04-29 15:06 ` [PATCH v4 06/10] fs/resctrl: Add last_cmd_status support for writes to max_threshold_occupancy Reinette Chatre
2026-04-29 15:06 ` [PATCH v4 07/10] fs/resctrl: Use accurate and symmetric exit flows Reinette Chatre
2026-04-29 15:06 ` [PATCH v4 08/10] fs/resctrl: Change last_cmd_status custom during input parsing Reinette Chatre
2026-05-28 23:38 ` Luck, Tony
2026-05-29 3:44 ` Reinette Chatre [this message]
2026-04-29 15:06 ` [PATCH v4 09/10] fs/resctrl: Communicate resource group deleted error via last_cmd_status Reinette Chatre
2026-04-29 15:06 ` [PATCH v4 10/10] 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=62975502-3d07-40ee-8ceb-c906a8c55c5c@intel.com \
--to=reinette.chatre@intel.com \
--cc=Dave.Martin@arm.com \
--cc=babu.moger@amd.com \
--cc=ben.horgan@arm.com \
--cc=bp@alien8.de \
--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=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®