Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
IronPort-SDR: Q43gCF6nAzm+KczJ8J8u3FB2Z1E14Btw9dTRv3+LSIsfrF0Ppw4XdNGCyHP2vyKmW2Xywhe0uX
 SzHX4OB1djvA==
IronPort-SDR: hpPnUjjcjcPumfqHPKVthzvzlEuENKNnPVgsTW0wCgzE3FsftI1zpMToUV9TUSRC9AinDR/6dS
 tFZ1ILxHWeow==
Subject: Re: [PATCH V5 4/4] x86/resctrl: Use appropriate API for strings
 terminated by newline
To:     Andy Shevchenko <andy.shevchenko@gmail.com>
Cc:     Thomas Gleixner <tglx@linutronix.de>,
        Fenghua Yu <fenghua.yu@intel.com>,
        Borislav Petkov <bp@alien8.de>,
        Tony Luck <tony.luck@intel.com>, kuo-lang.tseng@intel.com,
        ravi.v.shankar@intel.com, Ingo Molnar <mingo@redhat.com>,
        Babu Moger <babu.moger@amd.com>,
        "H. Peter Anvin" <hpa@zytor.com>,
        "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" <x86@kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
References: <cover.1589844108.git.reinette.chatre@intel.com>
 <a953992d99a1930703cba1362a3005d517c4cb33.1589844108.git.reinette.chatre@intel.com>
 <CAHp75Vc_VA-2UNJh7epe+oQEiU3WBedomLbAVTD_L4_ocvt8Dw@mail.gmail.com>
 <4a9603b8-32fb-024a-e2f5-14e95b4e3763@intel.com>
 <20200519160710.GK1634618@smile.fi.intel.com>
From:   Reinette Chatre <reinette.chatre@intel.com>
Message-ID: <87d00e95-7944-2fa4-fd02-1662ec4382fe@intel.com>
Date:   Tue, 19 May 2020 10:54:52 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:68.0) Gecko/20100101
 Thunderbird/68.8.0
MIME-Version: 1.0
In-Reply-To: <20200519160710.GK1634618@smile.fi.intel.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

Hi Andy,

On 5/19/2020 9:07 AM, Andy Shevchenko wrote:
> On Tue, May 19, 2020 at 08:50:22AM -0700, Reinette Chatre wrote:
>> On 5/19/2020 1:28 AM, Andy Shevchenko wrote:
>>> On Tue, May 19, 2020 at 2:50 AM Reinette Chatre
>>> <reinette.chatre@intel.com> wrote:
> 
> ...
> 
>>>> +       ret = sysfs_match_string(rdt_mode_str, buf);
>>>> +       if (ret < 0) {
>>>> +               rdt_last_cmd_puts("Unknown or unsupported mode\n");
>>>> +               ret = -EINVAL;
>>>> +               goto out;
>>>> +       }
>>
>> From your previous email ...
>>
>>>> +       ret = sysfs_match_string(rdt_mode_str, buf);
>>>> +       if (ret < 0) {
>>>> +               rdt_last_cmd_puts("Unknown or unsupported mode\n");
>>>
>>>> +               ret = -EINVAL;
>>>
>>> This is redundant.
>>
>> I understand that shadowing an error code is generally of concern. In
>> this case the error code is set to -EINVAL to ensure that it is the same
>> error code that was returned to user space originally and will continue
>> to be so no matter what changes may come to sysfs_match_string().
> 
> It returns -EINVAL and if that will be ever changed this driver would be one of
> hundreds who suffers.

Not if we keep this change ... but that is no longer of concern with the
removal of the check as you propose later.

> 
> ...
> 
>>> Can't we unify latter with a former like ...
> 
>> This would have been ideal if done from the start but currently "0" is
>> returned if the current mode is pseudo-locked and user attempts to
>> change the mode to pseudo-locked. Thus, to maintain the current user
>> interface the check if user wants to set pseudo-locked mode is moved
>> after the check if new mode is same as existing mode and thus not
>> unified because that will result in an error returned always when user
>> requests pseudo-locked mode.
> 
> Ah, I see now.
> 
> But we can then drop the check from sysfs_match_string() returned value, like
> 
> 	user_m = sysfs_match_string();
> 	if (...) {
> 		...
> 	} else { // w/o even checking for the PSEUDO_LOCKED
> 		...
> 		goto out;
> 	}
> 
> Can we?
> 

Yes, we can. Will do.

Reinette