From: Luis Chamberlain <mcgrof@kernel.org>
To: Krister Johansen <kjlx@templeofstupid.com>
Cc: Kees Cook <keescook@chromium.org>,
Iurii Zaikin <yzaikin@google.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Douglas Anderson <dianders@chromium.org>,
Vlastimil Babka <vbabka@suse.cz>, Arnd Bergmann <arnd@arndb.de>,
Lecopzer Chen <lecopzer.chen@mediatek.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Thomas Gleixner <tglx@linutronix.de>,
David Hildenbrand <david@redhat.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Pingfan Liu <kernelfans@gmail.com>,
Michael Kelley <mikelley@microsoft.com>,
Petr Mladek <pmladek@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Josh Poimboeuf <jpoimboe@kernel.org>,
"Guilherme G. Piccoli" <kernel@gpiccoli.net>,
Mike Rapoport <rppt@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 0/2] Triggering a softlockup panic during SMP boot
Date: Fri, 27 Oct 2023 15:04:56 -0700 [thread overview]
Message-ID: <ZTw0CACF3jtT3/dX@bombadil.infradead.org> (raw)
In-Reply-To: <cover.1698441495.git.kjlx@templeofstupid.com>
On Fri, Oct 27, 2023 at 02:46:26PM -0700, Krister Johansen wrote:
> Hi,
> This pair of patches was the result of an unsuccessful attempt to set
> softlockup_panic before SMP boot. The rationale for wanting to set this
> parameter is that some of the VMs that my team runs will occasionally
> get stuck while onlining the non-boot processors as part of SMP boot.
>
> In the cases where this happens, we find out about it after the instance
> successfully boots; however, the machines can get stuck for tens of
> minutes at a time before finally completing onlining processors. Since
> we pay per minute for many of these VMs there were two goals for setting
> this value on boot: first, fail fast and hope that a subsequent boot
> attempt will be successful. Second, a panic is a little easier to keep
> track of, especially if we're scraping serial logs after the fact. In
> essence, the goal is to trigger the failure earlier and hopefully get
> more useful information for further debugging the problem as well.
>
> While testing to make sure that this value was getting correctly set on
> boot, I ran into a pair of surprises. First, when the softlockup_panic
> parameter was migrated to a sysctl alias, it had the side effect of
> setting the parameter value after SMP boot has occurred, when it used to
> be set before this. Second, testing revealed that even though the
> aliases were being correctly processed, the kernel was reporting the
> commandline arguments as unrecognized. This generated a message in the
> logs about an unrecognized parameter (even though it was) and the
> parameter was passed as an environment variable to init.
>
> The first patch ensures that aliased sysctl arguments are not reported
> as unrecognized boot arguments.
>
> The second patch moves the setting of softlockup_panic earlier in boot,
> where it can take effect before SMP boot beings.
Sounds all great but I only got the cover letter, so may be resend?
Luis
next prev parent reply other threads:[~2023-10-27 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-27 21:46 Krister Johansen
2023-10-27 21:46 ` [PATCH 1/2] proc: sysctl: prevent aliased sysctls from getting passed to init Krister Johansen
2023-10-27 21:46 ` [PATCH 2/2] watchdog: move softlockup_panic back to early_param Krister Johansen
2023-10-27 22:04 ` Luis Chamberlain [this message]
2023-10-27 23:06 ` [PATCH 0/2] Triggering a softlockup panic during SMP boot Krister Johansen
2023-11-01 19:10 ` Luis Chamberlain
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=ZTw0CACF3jtT3/dX@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=david@redhat.com \
--cc=dianders@chromium.org \
--cc=jpoimboe@kernel.org \
--cc=keescook@chromium.org \
--cc=kernel@gpiccoli.net \
--cc=kernelfans@gmail.com \
--cc=kjlx@templeofstupid.com \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mikelley@microsoft.com \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=pmladek@suse.com \
--cc=rppt@kernel.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--cc=yzaikin@google.com \
/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®