linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matteo Croce <mcroce@linux.microsoft.com>
To: Petr Mladek <pmladek@suse.com>
Cc: linux-kernel@vger.kernel.org, Guenter Roeck <linux@roeck-us.net>,
	Arnd Bergmann <arnd@arndb.de>, Mike Rapoport <rppt@kernel.org>,
	Kees Cook <keescook@chromium.org>,
	Pavel Tatashin <pasha.tatashin@soleen.com>,
	Robin Holt <robinmholt@gmail.com>
Subject: Re: [PATCH v2 2/2] reboot: fix parsing of reboot cpu number
Date: Sun, 1 Nov 2020 02:57:40 +0100	[thread overview]
Message-ID: <CAFnufp2zSsESBK-ZfCJD5dFzMGc9pU4R-VT1j8eu1f4xPde19w@mail.gmail.com> (raw)
In-Reply-To: <20201030143049.GE1602@alley>

On Fri, Oct 30, 2020 at 3:30 PM Petr Mladek <pmladek@suse.com> wrote:
>
> On Tue 2020-10-27 14:35:45, Matteo Croce wrote:
> > From: Matteo Croce <mcroce@microsoft.com>
> >
> > The kernel cmdline reboot= argument allows to specify the CPU used
> > for rebooting, with the syntax `s####` among the other flags, e.g.
> >
> >   reboot=soft,s4
> >   reboot=warm,s31,force
> >
> > In the early days the parsing was done with simple_strtoul(), later
> > deprecated in favor of the safer kstrtoint() which handles overflow.
> >
> > But kstrtoint() returns -EINVAL if there are non-digit characters
> > in a string, so if this flag is not the last given, it's silently
> > ignored as well as the subsequent ones.
> >
> > To fix it, revert the usage of simple_strtoul(), which is no longer
> > deprecated, and restore the old behaviour.
> >
> > While at it, merge two identical code blocks into one.
>
> > --- a/kernel/reboot.c
> > +++ b/kernel/reboot.c
> > @@ -552,25 +552,19 @@ static int __init reboot_setup(char *str)
> >
> >               case 's':
> >               {
> > -                     int rc;
> > -
> > -                     if (isdigit(*(str+1))) {
> > -                             rc = kstrtoint(str+1, 0, &reboot_cpu);
> > -                             if (rc)
> > -                                     return rc;
> > -                             if (reboot_cpu >= num_possible_cpus()) {
> > -                                     reboot_cpu = 0;
> > -                                     return -ERANGE;
> > -                             }
> > -                     } else if (str[1] == 'm' && str[2] == 'p' &&
> > -                                isdigit(*(str+3))) {
> > -                             rc = kstrtoint(str+3, 0, &reboot_cpu);
> > -                             if (rc)
> > -                                     return rc;
> > -                             if (reboot_cpu >= num_possible_cpus()) {
> > -                                     reboot_cpu = 0;
>
>                                                      ^^^^^^
>
> > +                     int cpu;
> > +
> > +                     /*
> > +                      * reboot_cpu is s[mp]#### with #### being the processor
> > +                      * to be used for rebooting. Skip 's' or 'smp' prefix.
> > +                      */
> > +                     str += str[1] == 'm' && str[2] == 'p' ? 3 : 1;
> > +
> > +                     if (isdigit(str[0])) {
> > +                             cpu = simple_strtoul(str, NULL, 0);
> > +                             if (cpu >= num_possible_cpus())
> >                                       return -ERANGE;
> > -                             }
> > +                             reboot_cpu = cpu;
>
> The original value stays when the new one is out of range. It is
> small functional change that should get mentioned in the commit
> message or better fixed separately.
>

Hi,

I didn't understand, the original value is 0 since reboot_cpu is global.
reboot_setup() is only called once at boot to parse the cmdline,
indeed it's __init.
I don't know any way to call it more than once (exept passing multiple
reboot= arguments)

> Hmm, I suggest to split this into 3 patches and switch the order:
>
>   + 1st patch should simply revert the commit 616feab75397
>    ("kernel/reboot.c: convert simple_strtoul to kstrtoint").
>
>   + 2nd patch should merge the two branches without any
>     functional change.
>
>   + 3rd patch should add the check for num_possible_cpus()
>     and update the value only when it is valid.
>
> I am sorry that I did not suggested this when reviewed v1.
> I have missed this functional change at that time.
>

Np :)

Bye,

--
per aspera ad upstream

  reply	other threads:[~2020-11-01  2:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27 13:35 [PATCH v2 0/2] fix parsing of reboot= cmdline Matteo Croce
2020-10-27 13:35 ` [PATCH v2 1/2] reboot: fix overflow parsing reboot cpu number Matteo Croce
2020-10-27 13:42   ` Greg KH
2020-10-30 14:13     ` Petr Mladek
2020-10-30 14:18       ` Matteo Croce
2020-10-27 13:35 ` [PATCH v2 2/2] reboot: fix parsing of " Matteo Croce
2020-10-27 13:42   ` Greg KH
2020-10-30 14:30   ` Petr Mladek
2020-11-01  1:57     ` Matteo Croce [this message]
2020-11-02 11:01       ` Petr Mladek
2020-11-03 11:43         ` Matteo Croce
2020-11-03 14:25           ` Petr Mladek
2020-11-03 15:43             ` Matteo Croce
2020-11-03 16:22               ` Petr Mladek
2020-10-27 13:42 ` [PATCH v2 0/2] fix parsing of reboot= cmdline Greg KH

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=CAFnufp2zSsESBK-ZfCJD5dFzMGc9pU4R-VT1j8eu1f4xPde19w@mail.gmail.com \
    --to=mcroce@linux.microsoft.com \
    --cc=arnd@arndb.de \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=pasha.tatashin@soleen.com \
    --cc=pmladek@suse.com \
    --cc=robinmholt@gmail.com \
    --cc=rppt@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).