summaryrefslogtreecommitdiff
path: root/libparted/labels/pt-limit.gperf
diff options
context:
space:
mode:
authorColin Watson <cjwatson@ubuntu.com>2010-08-19 11:07:20 +0100
committerJim Meyering <meyering@redhat.com>2010-08-20 16:34:59 -0400
commitfb1616546c56d5f78fce9076e6fa72e179d06ad6 (patch)
treecbb58472a7c152e0b77657203cb8d89573989f44 /libparted/labels/pt-limit.gperf
parentfeaa8f3fd279a5eb3adb16d8cfe863328a5e3222 (diff)
downloadparted-fb1616546c56d5f78fce9076e6fa72e179d06ad6.tar.gz
libparted: remove limits on loop labels
There's no reason to impose any particular limit on loop labels, since they just represent a single large partition. Sector counts over 2^32 are needed for large RAID arrays. Change the limit to 2^64 since that's the upper limit imposed by libparted and it saves us implementing the limit functions separately. This bug appears to have been introduced by commit 2dbc645c. * libparted/labels/pt-limit.gperf: Change limits on "loop" to 2^64. * tests/t9021-maxima.sh: Update for the new loop limit. * NEWS (Bug fixes): Mention it.
Diffstat (limited to 'libparted/labels/pt-limit.gperf')
-rw-r--r--libparted/labels/pt-limit.gperf3
1 files changed, 2 insertions, 1 deletions
diff --git a/libparted/labels/pt-limit.gperf b/libparted/labels/pt-limit.gperf
index f834647..3d764ae 100644
--- a/libparted/labels/pt-limit.gperf
+++ b/libparted/labels/pt-limit.gperf
@@ -19,7 +19,8 @@ sun,128ULL*UINT32_MAX,UINT32_MAX
#
bsd,UINT32_MAX,UINT32_MAX
# aix,UINT32_MAX,UINT32_MAX
-loop,UINT32_MAX,UINT32_MAX
+# In reality, loop labels have no particular limit.
+loop,UINT64_MAX,UINT64_MAX
pc98,UINT32_MAX,UINT32_MAX
#
# FIXME: not verified. looks like these are cylinder aligned, too