From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Reinette Chatre <reinette.chatre@intel.com>
Cc: tglx@linutronix.de, fenghua.yu@intel.com, bp@alien8.de,
tony.luck@intel.com, kuo-lang.tseng@intel.com,
ravi.v.shankar@intel.com, mingo@redhat.com, babu.moger@amd.com,
hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V6 4/4] x86/resctrl: Use appropriate API for strings terminated by newline
Date: Wed, 20 May 2020 00:47:49 +0300 [thread overview]
Message-ID: <20200519214749.GM1634618@smile.fi.intel.com> (raw)
In-Reply-To: <79faf008e6460a2bc8a3cc02313f7900552b1475.1589922949.git.reinette.chatre@intel.com>
On Tue, May 19, 2020 at 02:28:31PM -0700, Reinette Chatre wrote:
> The user input to files in the resctrl filesystem are expected to be
> terminated with a newline. Testing the user input includes a test for
> the presence of a newline and then replacing the newline with NUL
> byte followed by comparison using strcmp().
>
> sysfs_streq() exists to test if strings are equal, treating both NUL and
> newline-then-NUL as equivalent string terminations. Even more,
> sysfs_match_string() exists to match a given string in an array using
> sysfs_streq().
>
> Replace existing strcmp() comparisons of strings that are terminated
> with a newline with more appropriate sysfs_streq() via the
> sysfs_match_string() API that can perform the match across the different
> mode strings that are already maintained in an array.
FWIW,
Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
> ---
> Changes since V5:
> - Remove the early check of the sysfs_match_string() return code. (Andy)
>
> arch/x86/kernel/cpu/resctrl/rdtgroup.c | 28 ++++++++++----------------
> 1 file changed, 11 insertions(+), 17 deletions(-)
>
> diff --git a/arch/x86/kernel/cpu/resctrl/rdtgroup.c b/arch/x86/kernel/cpu/resctrl/rdtgroup.c
> index 088a1536bccc..07e0f150c56e 100644
> --- a/arch/x86/kernel/cpu/resctrl/rdtgroup.c
> +++ b/arch/x86/kernel/cpu/resctrl/rdtgroup.c
> @@ -1414,13 +1414,11 @@ static ssize_t rdtgroup_mode_write(struct kernfs_open_file *of,
> char *buf, size_t nbytes, loff_t off)
> {
> struct rdtgroup *rdtgrp;
> - enum rdtgrp_mode mode;
> int ret = 0;
> + int user_m;
>
> - /* Valid input requires a trailing newline */
> - if (nbytes == 0 || buf[nbytes - 1] != '\n')
> + if (nbytes == 0)
> return -EINVAL;
> - buf[nbytes - 1] = '\0';
>
> rdtgrp = rdtgroup_kn_lock_live(of->kn);
> if (!rdtgrp) {
> @@ -1430,29 +1428,25 @@ static ssize_t rdtgroup_mode_write(struct kernfs_open_file *of,
>
> rdt_last_cmd_clear();
>
> - mode = rdtgrp->mode;
> + user_m = sysfs_match_string(rdt_mode_str, buf);
>
> - if ((!strcmp(buf, "shareable") && mode == RDT_MODE_SHAREABLE) ||
> - (!strcmp(buf, "exclusive") && mode == RDT_MODE_EXCLUSIVE) ||
> - (!strcmp(buf, "pseudo-locksetup") &&
> - mode == RDT_MODE_PSEUDO_LOCKSETUP) ||
> - (!strcmp(buf, "pseudo-locked") && mode == RDT_MODE_PSEUDO_LOCKED))
> + /* Do nothing and return success if user asks for current mode */
> + if (user_m == rdtgrp->mode)
> goto out;
>
> - if (mode == RDT_MODE_PSEUDO_LOCKED) {
> + if (rdtgrp->mode == RDT_MODE_PSEUDO_LOCKED) {
> rdt_last_cmd_puts("Cannot change pseudo-locked group\n");
> ret = -EINVAL;
> goto out;
> }
>
> - if (!strcmp(buf, "shareable")) {
> + if (user_m == RDT_MODE_SHAREABLE) {
> if (rdtgrp->mode == RDT_MODE_PSEUDO_LOCKSETUP) {
> ret = rdtgroup_locksetup_exit(rdtgrp);
> if (ret)
> goto out;
> }
> - rdtgrp->mode = RDT_MODE_SHAREABLE;
> - } else if (!strcmp(buf, "exclusive")) {
> + } else if (user_m == RDT_MODE_EXCLUSIVE) {
> if (!rdtgroup_mode_test_exclusive(rdtgrp)) {
> ret = -EINVAL;
> goto out;
> @@ -1462,16 +1456,16 @@ static ssize_t rdtgroup_mode_write(struct kernfs_open_file *of,
> if (ret)
> goto out;
> }
> - rdtgrp->mode = RDT_MODE_EXCLUSIVE;
> - } else if (!strcmp(buf, "pseudo-locksetup")) {
> + } else if (user_m == RDT_MODE_PSEUDO_LOCKSETUP) {
> ret = rdtgroup_locksetup_enter(rdtgrp);
> if (ret)
> goto out;
> - rdtgrp->mode = RDT_MODE_PSEUDO_LOCKSETUP;
> } else {
> rdt_last_cmd_puts("Unknown or unsupported mode\n");
> ret = -EINVAL;
> + goto out;
> }
> + rdtgrp->mode = user_m;
>
> out:
> rdtgroup_kn_unlock(of->kn);
> --
> 2.21.0
>
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2020-05-19 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 21:28 [PATCH V6 0/4] x86/resctrl: Enable user to view and select thread throttling mode Reinette Chatre
2020-05-19 21:28 ` [PATCH V6 1/4] " Reinette Chatre
2020-05-19 21:28 ` [PATCH V6 2/4] x86/resctrl: Enumerate per-thread MBA Reinette Chatre
2020-05-19 21:28 ` [PATCH V6 3/4] x86/resctrl: Enable " Reinette Chatre
2020-05-19 21:28 ` [PATCH V6 4/4] x86/resctrl: Use appropriate API for strings terminated by newline Reinette Chatre
2020-05-19 21:47 ` Andy Shevchenko [this message]
2020-05-19 21:35 ` [PATCH V6 0/4] x86/resctrl: Enable user to view and select thread throttling mode Borislav Petkov
2020-05-19 22:13 ` Reinette Chatre
2020-05-20 7:11 ` Borislav Petkov
2020-05-20 17:32 ` Reinette Chatre
2020-05-20 18:35 ` Borislav Petkov
2020-05-20 20:24 ` 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=20200519214749.GM1634618@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=kuo-lang.tseng@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ravi.v.shankar@intel.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;
as well as URLs for NNTP newsgroup(s).