stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Mladek <pmladek@suse.com>
To: Matteo Croce <mcroce@linux.microsoft.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>,
	Fabian Frederick <fabf@skynet.be>,
	stable@vger.kernel.org
Subject: Re: [PATCH 1/2] reboot: fix overflow parsing reboot cpu number
Date: Mon, 19 Oct 2020 15:18:43 +0200	[thread overview]
Message-ID: <20201019131843.GB26718@alley> (raw)
In-Reply-To: <20201016180907.171957-2-mcroce@linux.microsoft.com>

On Fri 2020-10-16 20:09:06, Matteo Croce wrote:
> From: Matteo Croce <mcroce@microsoft.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@microsoft.com>

Reviewed-by: Petr Mladek <pmladek@suse.com>

Best Regards,
Petr

  parent reply	other threads:[~2020-10-19 13:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-16 18:09 [PATCH 0/2] fix parsing of reboot= cmdline Matteo Croce
2020-10-16 18:09 ` [PATCH 1/2] reboot: fix overflow parsing reboot cpu number Matteo Croce
2020-10-16 19:25   ` Kees Cook
2020-10-16 19:45   ` Pavel Tatashin
2020-10-19 13:18   ` Petr Mladek [this message]
2020-10-16 18:09 ` [PATCH 2/2] reboot: fix parsing of " Matteo Croce
2020-10-16 19:26   ` Kees Cook
2020-10-16 21:34     ` Matteo Croce
2020-10-16 19:46   ` Pavel Tatashin
2020-10-19 13:49   ` Petr Mladek

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=20201019131843.GB26718@alley \
    --to=pmladek@suse.com \
    --cc=arnd@arndb.de \
    --cc=fabf@skynet.be \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=mcroce@linux.microsoft.com \
    --cc=pasha.tatashin@soleen.com \
    --cc=robinmholt@gmail.com \
    --cc=rppt@kernel.org \
    --cc=stable@vger.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).