Mailinglist Archive: opensuse-bugs (5243 mails)

< Previous Next >
[Bug 809737] New: mount -oloop,sizelimit=nnnnnn ignores the sizelimit
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Fri, 15 Mar 2013 20:54:50 +0000
  • Message-id: <bug-809737-21960@http.bugzilla.novell.com/>

https://bugzilla.novell.com/show_bug.cgi?id=809737

https://bugzilla.novell.com/show_bug.cgi?id=809737#c0


Summary: mount -oloop,sizelimit=nnnnnn ignores the sizelimit
Classification: openSUSE
Product: openSUSE 12.3
Version: Final
Platform: Other
OS/Version: Other
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Basesystem
AssignedTo: puzel@xxxxxxxx
ReportedBy: jeffm@xxxxxxxx
QAContact: qa-bugs@xxxxxxx
Found By: ---
Blocker: ---


I recently tried to mount an hfsplus file system from an image file with
a partition table by using the loop offset and sizelimit options to specify
the location of the file system.

hfsplus stores some metadata at a set offset from the end of the partition,
so it's sensitive to the device size reported by the kernel.

It worked with this:
# losetup -r -o 32k --sizelimit=102400000 <loopdev> <imagefile>
# mount -r -t hfsplus <loopdev> <mountpoint>

But failed with this:
# mount -r -oloop,offset=32k,sizelimit=102400000 <imagefile> <mountpoint>

# losetup -a
/dev/loop0: [0089]:2 (<imagefile>), offset 32768, sizelimit 102400000
/dev/loop1: [0089]:2 (<imagefile>), offset 32768, sizelimit 102400000

/proc/partitions shows the correct number of blocks to match the sizelimit.

But if I set a breakpoint in mount before the mount syscall, I could see:
# blockdev --getsize64 /dev/loop[01]
102400000
102432768

Patch to follow.

--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

< Previous Next >