From: Ronan CHAUVIN <ronan.chauvin@parrot.com>
To: <util-linux@vger.kernel.org>
Cc: matthieu CASTET <matthieu.castet@parrot.com>,
Alexandre Dilly <alexandre.dilly@parrot.com>
Subject: [libfdisk]: gpt_write_disklabel function robustness to sudden power off
Date: Fri, 20 Mar 2015 11:17:13 +0100 [thread overview]
Message-ID: <550BF3A9.8080508@parrot.com> (raw)
Hello everyone,
I have a question regarding the fdisk library (libfdisk) provided in the
2.26 version of util-linux. I use it to create a MBR/GPT partition
scheme on a eMMC memory. I also use the partition renaming mechanism to
switch from a normal boot to an update boot (the bootloader compares
partitions names to choose the one to boot on).
I was wondering if the gpt_write_disklabel function was robust to sudden
power-off. In the source code, the writing procedure is as follow (UEFI
requires writing in this specific order):
1) backup partition tables
2) backup GPT header
3) primary partition tables
4) primary GPT header
5) protective MBR
and uses the standard linux write function with a file descriptor. Is
the writing order guaranty as operation is not synchronous ? I know that
the linux io scheduler can "optimize" writing operations order. This can
introduce an issue if only the primary and backup headers are written
but not the partition tables.
Thank you,
--
Ronan CHAUVIN
Embedded Software Engineer
ASIC team
--------------------------------
Parrot
174, quai de Jemmapes
75010 Paris France
--------------------------------
www.parrot.com
next reply other threads:[~2015-03-20 10:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 10:17 Ronan CHAUVIN [this message]
2015-03-20 11:18 ` [libfdisk]: gpt_write_disklabel function robustness to sudden power off Karel Zak
2015-03-23 18:31 ` Peter Cordes
2015-03-24 14:05 ` Ronan CHAUVIN
2015-03-24 14:25 ` Peter Cordes
2015-03-26 13:07 ` Ronan CHAUVIN
2015-03-24 3:24 ` Dale R. Worley
2015-03-24 13:54 ` Ronan CHAUVIN
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=550BF3A9.8080508@parrot.com \
--to=ronan.chauvin@parrot.com \
--cc=alexandre.dilly@parrot.com \
--cc=matthieu.castet@parrot.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 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.