mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lukasz Luba <lukasz.luba@arm.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: [PATCH] powercap: Adjust printing the constraint name with new line
Date: Tue, 17 Nov 2020 12:57:10 +0000	[thread overview]
Message-ID: <f937c2b9-bfeb-7978-bf15-ef620c12a15d@arm.com> (raw)
In-Reply-To: <CAJZ5v0ihFzzmcN1c-Oo2ELkJZcLhfsrQTh+Yd5bgo3yrnjZPuA@mail.gmail.com>



On 11/17/20 12:51 PM, Rafael J. Wysocki wrote:
> On Tue, Nov 17, 2020 at 10:22 AM Lukasz Luba <lukasz.luba@arm.com> wrote:
>>
>> Hi Rafael,
>>
>> On 11/10/20 7:19 PM, Rafael J. Wysocki wrote:
>>> On Mon, Nov 9, 2020 at 6:25 PM Lukasz Luba <lukasz.luba@arm.com> wrote:
>>>>
>>>> The constraint name has limit of size 30, which sometimes might be hit.
>>>> When this happens the new line might be lost. Prevent this and set the
>>>> new line when the name string is too long."
>>>>
>>>> Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
>>>> ---
>>>>    drivers/powercap/powercap_sys.c | 4 ++++
>>>>    1 file changed, 4 insertions(+)
>>>>
>>>> diff --git a/drivers/powercap/powercap_sys.c b/drivers/powercap/powercap_sys.c
>>>> index f808c5fa9838..575f9fdb810e 100644
>>>> --- a/drivers/powercap/powercap_sys.c
>>>> +++ b/drivers/powercap/powercap_sys.c
>>>> @@ -174,6 +174,10 @@ static ssize_t show_constraint_name(struct device *dev,
>>>>                                                                   "%s\n", name);
>>>>                           buf[POWERCAP_CONSTRAINT_NAME_LEN] = '\0';
>>>>                           len = strlen(buf);
>>>> +
>>>> +                       /* When the 'name' is too long, don't lose new line */
>>>> +                       if (strlen(name) >= POWERCAP_CONSTRAINT_NAME_LEN)
>>>> +                               buf[POWERCAP_CONSTRAINT_NAME_LEN - 1] = '\n';
>>>
>>> Wouldn't it be better to pass POWERCAP_CONSTRAINT_NAME_LEN - 1 to
>>> snprintf() above?
>>
>> My apologies for delay, I was on holidays.
>>
>> The snprintf() overwrites the '\n' in that case also.
> 
> The snprintf() doesn't do that AFAICS, but the next assignment
> overwrites the newline with the zero character.
> 
> Anyway, it should have been POWERCAP_CONSTRAINT_NAME_LEN - 2, because
> it needs to leave space for 2 characters, the newline and the
> terminating zero.
> 
>> I've experimented with it a bit more and tried to come with a bit 'cleaner' solution.
>>
>> What we are looking is probably: "%.*s\n" semantic.
>> Another solution would be:
>> ------------------------------8<---------------------------
>>                   if (name) {
>> -                       snprintf(buf, POWERCAP_CONSTRAINT_NAME_LEN,
>> -                                                               "%s\n",
>> name);
>> -                       buf[POWERCAP_CONSTRAINT_NAME_LEN] = '\0';
>> +                       sprintf(buf, "%.*s\n",
>> POWERCAP_CONSTRAINT_NAME_LEN -1,
>> +                               name);
>>                           len = strlen(buf);
>>                   }
>>
>> ----------------------------->8----------------------------
>>
>> I've check this and it behaves very well.
>>
>> It looks cleaner and it is a used pattern in the kernel.
>> What do you think? Is it good for v2?
> 
> This works for me too.
> 
> Thanks!
> 

Thank you for the comments. I will send the v2 then.

Regards,
Lukasz

      reply	other threads:[~2020-11-17 12:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-09 17:24 Lukasz Luba
2020-11-10 19:19 ` Rafael J. Wysocki
2020-11-17  9:22   ` Lukasz Luba
2020-11-17 12:51     ` Rafael J. Wysocki
2020-11-17 12:57       ` Lukasz Luba [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=f937c2b9-bfeb-7978-bf15-ef620c12a15d@arm.com \
    --to=lukasz.luba@arm.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    /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®