From: Christophe Varoqui <christophe.varoqui@gmail.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: dm-cvs@sourceware.org
Subject: Re: multipath-tools/kpartx gpt.c
Date: Wed, 02 Nov 2011 22:53:52 +0100 [thread overview]
Message-ID: <1320270832.16195.17.camel@lapoo.opensvc.com> (raw)
In-Reply-To: <20111024133718.30188.qmail@sourceware.org>
> --- multipath-tools/kpartx/gpt.c 2006/10/13 23:28:47 1.3
> +++ multipath-tools/kpartx/gpt.c 2011/10/24 13:37:18 1.3.2.1
> @@ -358,6 +358,15 @@
> return 0;
> }
>
> + /* Check that sizeof_partition_entry has the correct value */
> + if (__le32_to_cpu((*gpt)->sizeof_partition_entry) != sizeof(gpt_entry)) {
> + // printf("GUID partition entry size check failed.\n");
> + free(*gpt);
> + *gpt = NULL;
> + return 0;
> + }
> +
> +
> if (!(*ptes = alloc_read_gpt_entries(fd, *gpt))) {
> free(*gpt);
> *gpt = NULL;
>
Do you want this enhancement applied to upstream kpartx ? It seems the
hole is open there at the moment.
Regards,
--
Christophe Varoqui
OpenSVC - Tools to scale
http://www.opensvc.com/
prev parent reply other threads:[~2011-11-02 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 13:37 multipath-tools/kpartx gpt.c bmarzins
2011-11-02 21:53 ` Christophe Varoqui [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=1320270832.16195.17.camel@lapoo.opensvc.com \
--to=christophe.varoqui@gmail.com \
--cc=christophe.varoqui@opensvc.com \
--cc=dm-cvs@sourceware.org \
--cc=dm-devel@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.