linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Julius Werner <jwerner@chromium.org>
To: Davidlohr Bueso <dave@stgolabs.net>
Cc: linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-block@vger.kernel.org,
	Gwendal Grignou <gwendal@chromium.org>,
	Doug Anderson <dianders@chromium.org>,
	Julius Werner <jwerner@chromium.org>
Subject: [PATCH] block: partitions: efi: Always check for alternative GPT at end of drive
Date: Mon, 25 Apr 2016 18:06:46 -0700	[thread overview]
Message-ID: <1461632806-5946-1-git-send-email-jwerner@chromium.org> (raw)

The GUID Partiton Table layout maintains two synonymous partition tables
on a block device, one starting in sector 1 and one in the very last
sectors of the block device. This is useful if one of the tables gets
accidentally corrupted (e.g. through a partial write because of an
unexpected power loss).

Linux normally only boots if the primary GPT is valid. It will not even
try to find the alternative GPT to an invalid primary one unless the
"gpt" command line option forces more aggressive detection. This doesn't
really make any sense... if the "gpt" option is not set, the code
validates the protective or hybrid MBR in sector 0 anyway before it even
starts looking for the actual GPTs. If we get to the point where a valid
proctective or hybrid MBR was found but the primary GPT was not found
(valid), checking the alternative GPT is our best bet: we know that this
block device is meant to use GPT (because any other partitioning system
would've presumably overwritten sector 0), and we know that if the
alternative GPT is valid it should contain more accurate information
than parsing the protective/hybrid MBR with msdos_partition() would
yield (which would otherwise be what happens next).

Signed-off-by: Julius Werner <jwerner@chromium.org>
---
 block/partitions/efi.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/block/partitions/efi.c b/block/partitions/efi.c
index 26cb624..0d4ca8e 100644
--- a/block/partitions/efi.c
+++ b/block/partitions/efi.c
@@ -625,7 +625,7 @@ static int find_valid_gpt(struct parsed_partitions *state, gpt_header **gpt,
 		good_agpt = is_gpt_valid(state,
 					 le64_to_cpu(pgpt->alternate_lba),
 					 &agpt, &aptes);
-        if (!good_agpt && force_gpt)
+        if (!good_agpt)
                 good_agpt = is_gpt_valid(state, lastlba, &agpt, &aptes);
 
         /* The obviously unsuccessful case */
-- 
2.1.2

             reply	other threads:[~2016-04-26  1:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26  1:06 Julius Werner [this message]
2016-04-26 10:20 ` [PATCH] block: partitions: efi: Always check for alternative GPT at end of drive Karel Zak
2016-04-26 18:33   ` Davidlohr Bueso
2016-04-26 20:13     ` Julius Werner
2016-04-26 20:34     ` Elliott, Robert (Persistent Memory)
2016-04-26 21:15       ` Davidlohr Bueso
2016-04-26 21:51         ` Gwendal Grignou
2016-04-27 15:09           ` Karel Zak
2016-04-27 15:45             ` Doug Anderson
2016-04-27 21:44             ` Julius Werner
2016-04-27  6:00       ` Ard Biesheuvel
2016-04-27 12:59         ` Austin S. Hemmelgarn
2016-04-26 14:38 ` Austin S. Hemmelgarn
2016-04-26 18:10   ` Davidlohr Bueso
2016-04-26 19:27     ` Austin S. Hemmelgarn

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=1461632806-5946-1-git-send-email-jwerner@chromium.org \
    --to=jwerner@chromium.org \
    --cc=dave@stgolabs.net \
    --cc=dianders@chromium.org \
    --cc=gwendal@chromium.org \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-efi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).