All of lore.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Geoff Levand <geoff@infradead.org>
Cc: panand@redhat.com, kexec@lists.infradead.org,
	Simon Horman <horms@verge.net.au>,
	Petitboot@lists.ozlabs.org, Dave Young <dyoung@redhat.com>,
	vgoyal@redhat.com
Subject: Re: [PATCH] kexec: Add --lite option
Date: Fri, 23 Oct 2015 14:02:34 -0500	[thread overview]
Message-ID: <87d1w52yt1.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <1445540240.30908.134.camel@infradead.org> (Geoff Levand's message of "Thu, 22 Oct 2015 11:57:20 -0700")

Geoff Levand <geoff@infradead.org> writes:

>> > It was reported that on some systems where purgatory is running
>> > without caches enabled the sha256 calculations would take several
>> > minutes.  For bootloaders that just load a new image and
>> > immediately jump into it the loss of the integrity check is worth
>> > the increase in boot speed.  Please consider.  
>> 
>> Pratyush reported the arm64 issue, he sent a patch to fix it with
>> enabling cache for purgatory. I think the patch can fix the problem.
>> Why not fix it? The fix is simple enough and it does not introduce
>> complicate logic.
>
> This patch also is simple, and is architecture independent.  I see this
> feature as an improvement to kexec, not necessarily as a fix for that
> problem.

Disabling image verification is not an improvement, all it does is
allow for a nasty form of heisenbug.


Eric

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

  parent reply	other threads:[~2015-10-23 19:11 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 23:12 [PATCH] kexec: Add --lite option Geoff Levand
2015-10-22  0:02 ` Jeremy Kerr
2015-10-22  0:37   ` Geoff Levand
2015-11-05  6:20     ` Scott Wood
2015-10-22  3:17 ` Dave Young
2015-10-22 12:50   ` Vivek Goyal
2015-10-22 19:08     ` Geoff Levand
2015-11-05  5:56       ` Scott Wood
2015-12-07 11:45         ` Pratyush Anand
2015-12-07 11:48           ` Pratyush Anand
2015-12-07 11:48             ` Pratyush Anand
2015-12-07 13:16             ` James Morse
2015-12-07 13:16               ` James Morse
2015-12-07 14:07               ` Pratyush Anand
2015-12-07 14:07                 ` Pratyush Anand
2015-12-08  1:03                 ` Scott Wood
2015-12-08  1:03                   ` Scott Wood
2015-12-08 16:00                 ` James Morse
2015-12-08 16:00                   ` James Morse
2015-12-09  9:28                   ` Pratyush Anand
2015-12-09  9:28                     ` Pratyush Anand
2016-01-11 12:46                     ` Pratyush Anand
2016-01-11 12:46                       ` Pratyush Anand
2016-01-12  1:06                       ` Simon Horman
2016-01-12  1:06                         ` Simon Horman
2015-10-22 18:57   ` Geoff Levand
2015-10-22 19:04     ` Vivek Goyal
2015-10-23  9:46     ` Dave Young
2015-10-23 18:49       ` Geoff Levand
2015-10-23 19:02     ` Eric W. Biederman [this message]
2018-04-11 18:30 ` [PATCH v2] kexec: Add --no-checks option Geoff Levand
2018-04-19  8:38   ` 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=87d1w52yt1.fsf@x220.int.ebiederm.org \
    --to=ebiederm@xmission.com \
    --cc=Petitboot@lists.ozlabs.org \
    --cc=dyoung@redhat.com \
    --cc=geoff@infradead.org \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=panand@redhat.com \
    --cc=vgoyal@redhat.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 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.