From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Mariusz Dabrowski <mariusz.dabrowski@intel.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH] Always return last partition end address in 512B blocks
Date: Mon, 12 Dec 2016 14:30:28 -0500 [thread overview]
Message-ID: <wrfjshptrlm3.fsf@redhat.com> (raw)
In-Reply-To: <1481195606-13227-1-git-send-email-mariusz.dabrowski@intel.com> (Mariusz Dabrowski's message of "Thu, 8 Dec 2016 12:13:26 +0100")
Mariusz Dabrowski <mariusz.dabrowski@intel.com> writes:
> For 4K disks 'endofpart' is an index of the last 4K sector used by partition.
> mdadm is using number of 512-byte sectors, so value returned by
> get_last_partition_end must be multiplied by 8 for devices with 4K sectors.
> Also, unused 'ret' variable has been removed.
>
> Signed-off-by: Mariusz Dabrowski <mariusz.dabrowski@intel.com>
> ---
> util.c | 7 +++++--
> 1 file changed, 5 insertions(+), 2 deletions(-)
I am a little wary of this since I don't have any 4k sector drivers to
test with, so I will come yelling at you if this breaks something :)
> diff --git a/util.c b/util.c
> index 883eaa4..46c1280 100644
> --- a/util.c
> +++ b/util.c
> @@ -1430,6 +1430,7 @@ static int get_last_partition_end(int fd, unsigned long long *endofpart)
> struct MBR boot_sect;
> unsigned long long curr_part_end;
> unsigned part_nr;
> + unsigned int sector_size;
> int retval = 0;
>
> *endofpart = 0;
> @@ -1469,6 +1470,9 @@ static int get_last_partition_end(int fd, unsigned long long *endofpart)
> /* Unknown partition table */
> retval = -1;
> }
> + /* calculate number of 512-byte blocks */
> + if (get_dev_sector_size(fd, NULL, §or_size))
> + *endofpart *= sector_size/512;
I really would prefer to see a parenthesis around this here and use of
proper spacing.
Thanks,
Jes
prev parent reply other threads:[~2016-12-12 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 11:13 [PATCH] Always return last partition end address in 512B blocks Mariusz Dabrowski
2016-12-12 19:30 ` Jes Sorensen [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=wrfjshptrlm3.fsf@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.dabrowski@intel.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.