linux-kernel - Re: [PATCH] partitions/efi: complete gpt kernel param purpose

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 5 Dec 2013 12:21:58 +0100
From:	Karel Zak <kzak@...hat.com>
To:	Davidlohr Bueso <davidlohr@...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 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.

    Karel

-- 
 Karel Zak  <kzak@...hat.com>
 http://karelzak.blogspot.com
--
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/