All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: Dave Young <dyoung@redhat.com>
Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>,
	Bhupesh Sharma <bhsharma@redhat.com>,
	Bhupesh SHARMA <bhupesh.linux@gmail.com>,
	kexec mailing list <kexec@lists.infradead.org>,
	Simon Horman <horms@verge.net.au>
Subject: Re: [PATCH] arm64: If 'getrandom' syscall fails, don't error out - just warn and proceed.
Date: Wed, 24 Oct 2018 15:13:10 +0800	[thread overview]
Message-ID: <20181024071310.GA2120@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20181024070439.GC3094@dhcp-128-65.nay.redhat.com>

On 10/24/18 at 03:04pm, Dave Young wrote:
> But if one specify "nokaslr" in 2nd kernel cmdlind eg. in some kdump
> config files, but kexec-tools still give a warning message, this is not
> good.

Yeah, message is an element of feature. If adding nokaslr still give a
warning or error message, that is obviously a bug we need fix. Otherwise
we can step back to not support kaslr in kdump.

Thanks
Baoquan

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2018-10-24  7:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-22 20:20 [PATCH] arm64: If 'getrandom' syscall fails, don't error out - just warn and proceed Bhupesh Sharma
2018-10-23  1:31 ` Dave Young
2018-10-23  5:08   ` Bhupesh Sharma
2018-10-24  7:04     ` Dave Young
2018-10-24  7:13       ` Baoquan He [this message]
2018-10-24  8:31       ` Bhupesh Sharma
2018-10-25  5:29         ` Dave Young
2018-10-29 10:15 ` Simon Horman

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=20181024071310.GA2120@MiWiFi-R3L-srv \
    --to=bhe@redhat.com \
    --cc=bhsharma@redhat.com \
    --cc=bhupesh.linux@gmail.com \
    --cc=dyoung@redhat.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=takahiro.akashi@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.