This is the mail archive of the
insight-prs@sources.redhat.com
mailing list for the Insight project.
insight/132: losetup behaviour incorrect for large offsets
- From: jim dot bell at dsto dot defence dot gov dot au
- To: insight-gnats at sources dot redhat dot com
- Date: 12 Mar 2002 04:02:46 -0000
- Subject: insight/132: losetup behaviour incorrect for large offsets
- Reply-to: jim dot bell at dsto dot defence dot gov dot au
>Number: 132
>Category: insight
>Synopsis: losetup behaviour incorrect for large offsets
>Confidential: no
>Severity: serious
>Priority: high
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Mar 11 20:03:00 PST 2002
>Closed-Date:
>Last-Modified:
>Originator: jim.bell@dsto.defence.gov.au
>Release: unknown-1.0
>Organization:
>Environment:
RH 7.2 2.4.7-10enterprise
>Description:
losetup uses an offset value of 2^31 - 1 whenever an offset greater than or equal to this is specified. Worse, it changes the value silently, and the documentation does not mention a signed 32 bit limit on this value.
With loopback files growing in size with disk size, a 2GB limit is inappropriate.
>How-To-Repeat:
touch loopback
losetup -o 3000000000 /dev/loop6 loopback
losetup /dev/loop6
(returns 2^31-1 as offset, clearly wrong)
>Fix:
Hoping someone can tell me!
>Release-Note:
>Audit-Trail:
>Unformatted: