From: Davidlohr Bueso <davidlohr@hp.com>
To: Karel Zak <kzak@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Matt Domsch <Matt_Domsch@dell.com>,
Matt Fleming <matt.fleming@intel.com>,
"Chandramouleeswaran,Aswin" <aswin@hp.com>
Subject: Re: [PATCH] partitions/efi: complete gpt kernel param purpose
Date: Thu, 05 Dec 2013 06:52:11 -0800 [thread overview]
Message-ID: <1386255131.2802.3.camel@buesod1.americas.hpqcorp.net> (raw)
In-Reply-To: <20131205112158.GD8058@x2.net.home>
On Thu, 2013-12-05 at 12:21 +0100, Karel Zak wrote:
> On Wed, Dec 04, 2013 at 03:16:02PM -0800, Davidlohr Bueso wrote:
> > From: Davidlohr Bueso <davidlohr@hp.com>
> >
> > The usage of the 'gpt' kernel parameter is twofold:
> > (i) skip any mbr integrity checks and (ii) enable the
> > backup GPT header to be used in situations where the
> > primary one is corrupted. This last "feature" is not
> > obvious and needs to be properly documented in the
> > kernel-parameters document.
>
> The question is if we really have to force users to specify "gpt"
> kernel parameter to use the backup GPT header. Maybe it would be
> enough to report the problem (print warning) and use the valid backup
> header. IMHO the current behaviour is overkill.
Well yes, however, the rationale behind having to use 'gpt' is to
protect against devices which misreport their size, and forces the user
to decide to use the alternate GPT when they still have a valid primary
header. This has been the policy for years.
Thanks,
Davidlohr
prev parent reply other threads:[~2013-12-05 14:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-04 23:16 Davidlohr Bueso
2013-12-05 11:21 ` Karel Zak
2013-12-05 14:52 ` Davidlohr Bueso [this message]
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=1386255131.2802.3.camel@buesod1.americas.hpqcorp.net \
--to=davidlohr@hp.com \
--cc=Matt_Domsch@dell.com \
--cc=akpm@linux-foundation.org \
--cc=aswin@hp.com \
--cc=kzak@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.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®