linux-kernel - Re: [PATCH v2 1/2] reboot: fix overflow parsing reboot cpu number

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAFnufp3sSb6_puAUpCdp9v2Kzw77-dtSAZrmzEwQpUeu6rRAUw@mail.gmail.com>
Date:   Fri, 30 Oct 2020 15:18:04 +0100
From:   Matteo Croce <mcroce@...ux.microsoft.com>
To:     Petr Mladek <pmladek@...e.com>
Cc:     Greg KH <gregkh@...uxfoundation.org>, linux-kernel@...r.kernel.org,
        Guenter Roeck <linux@...ck-us.net>,
        Arnd Bergmann <arnd@...db.de>, Mike Rapoport <rppt@...nel.org>,
        Kees Cook <keescook@...omium.org>,
        Pavel Tatashin <pasha.tatashin@...een.com>,
        Robin Holt <robinmholt@...il.com>,
        Fabian Frederick <fabf@...net.be>
Subject: Re: [PATCH v2 1/2] reboot: fix overflow parsing reboot cpu number

On Fri, Oct 30, 2020 at 3:13 PM Petr Mladek <pmladek@...e.com> wrote:
>
> On Tue 2020-10-27 14:42:43, Greg KH wrote:
> > On Tue, Oct 27, 2020 at 02:35:44PM +0100, Matteo Croce wrote:
> > > From: Matteo Croce <mcroce@...rosoft.com>
> > >
> > > Limit the CPU number to num_possible_cpus(), because setting it
> > > to a value lower than INT_MAX but higher than NR_CPUS produces the
> > > following error on reboot and shutdown:
> > >
> > > Fixes: 1b3a5d02ee07 ("reboot: move arch/x86 reboot= handling to generic kernel")
> > > Signed-off-by: Matteo Croce <mcroce@...rosoft.com>
>
> Reviewed-by: Petr Mladek <pmladek@...e.com>
>
> > <formletter>
> >
> > This is not the correct way to submit patches for inclusion in the
> > stable kernel tree.  Please read:
> >     https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
> > for how to do this properly.
> >
> > </formletter>
>
> The best way is to add the following line before Signed-off-by line:
>
> Cc: stable@...r.kernel.org
>

I see, sorry for the noise. Should I resend, or I eventually write to
stable@...r.kernel.org after the merge?


-- 
per aspera ad upstream