From: Eduardo Valentin <eduval@amazon.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
Juerg Haefliger <juerg.haefliger@canonical.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mingo@kernel.org, tglx@linutronix.de, peterz@infradead.org,
hughd@google.com, luto@kernel.org
Subject: Re: KAISER: kexec triggers a warning
Date: Fri, 1 Dec 2017 08:38:50 -0800 [thread overview]
Message-ID: <20171201163850.GC26327@u40b0340c692b58f6553c.ant.amazon.com> (raw)
In-Reply-To: <20171201153713.apdoi6em7c4iynlr@pd.tnic>
On Fri, Dec 01, 2017 at 04:37:13PM +0100, Borislav Petkov wrote:
> On Fri, Dec 01, 2017 at 07:31:36AM -0800, Dave Hansen wrote:
> > The only question is whether we want to preserve _some_ kind of warning
> > there, or just axe it entirely.
>
> Right, my fear would be if we keep it, then we'd have to go and
> whitelist or somehow track those users which are an exception...
>
> OTOH, it might be prudent to have a warning to catch such abnormal
> situations...
But a warn like that on the kexec/kdump path can be scary for regular / unware users,
specially considering that kexec is almost common place for regular reboot.
>
> --
> Regards/Gruss,
> Boris.
>
> Good mailing practices for 400: avoid top-posting and trim the reply.
>
--
All the best,
Eduardo Valentin
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-01 16:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-01 13:52 Juerg Haefliger
2017-12-01 15:18 ` Baoquan He
2017-12-01 15:27 ` Borislav Petkov
2017-12-04 1:52 ` Baoquan He
2017-12-01 15:31 ` Dave Hansen
2017-12-01 15:37 ` Borislav Petkov
2017-12-01 16:38 ` Eduardo Valentin [this message]
2017-12-01 17:03 ` Borislav Petkov
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=20171201163850.GC26327@u40b0340c692b58f6553c.ant.amazon.com \
--to=eduval@amazon.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hughd@google.com \
--cc=juerg.haefliger@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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