From: Karel Zak <kzak@redhat.com>
To: util-linux@vger.kernel.org, grawity@gmail.com
Subject: Re: [bug] incorrect GPT entry validation?
Date: Wed, 21 Nov 2012 15:53:50 +0100 [thread overview]
Message-ID: <20121121145350.GA2912@x2.net.home> (raw)
In-Reply-To: <20121103183511.GO482@rampage>
On Sat, Nov 03, 2012 at 02:35:11PM -0400, Dave Reisner wrote:
> blkid correctly reads the first 2 entries on the disk, but then starts
> reporting corrupted GPT entries (seen via LIBBLKID_DEBUG=0xffff):
We have two GPT headers... and the third pass have nothing
to parse :-)
This is the bug:
swap_efi_guid(&e->unique_partition_guid);
swap_efi_guid(&e->partition_type_guid);
the "e" is persistent buffer.
Fixed. Thanks!
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
prev parent reply other threads:[~2012-11-21 14:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-03 18:35 [bug] incorrect GPT entry validation? Dave Reisner
2012-11-05 9:45 ` Karel Zak
2012-11-05 14:05 ` Mantas Mikulėnas
2012-11-21 14:53 ` Karel Zak [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=20121121145350.GA2912@x2.net.home \
--to=kzak@redhat.com \
--cc=grawity@gmail.com \
--cc=util-linux@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).