This is the mail archive of the mailing list for the Insight project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

insight/132: losetup behaviour incorrect for large offsets

>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
>Release:        unknown-1.0
RH 7.2 2.4.7-10enterprise
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.
touch loopback
losetup -o 3000000000 /dev/loop6 loopback
losetup /dev/loop6
(returns 2^31-1 as offset, clearly wrong)
Hoping someone can tell me!

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]