[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1386255131.2802.3.camel@buesod1.americas.hpqcorp.net>
Date: Thu, 05 Dec 2013 06:52:11 -0800
From: Davidlohr Bueso <davidlohr@...com>
To: Karel Zak <kzak@...hat.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
linux-kernel@...r.kernel.org, Matt Domsch <Matt_Domsch@...l.com>,
Matt Fleming <matt.fleming@...el.com>,
"Chandramouleeswaran,Aswin" <aswin@...com>
Subject: Re: [PATCH] partitions/efi: complete gpt kernel param purpose
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@...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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists