[BusyBox 0000498]: mount loop device support broken

[bugs at busybox.net]

A NOTE has been added to this issue. 
====================================================================== 
http://busybox.net/bugs/view.php?id=498 
====================================================================== 
Reported By:                smiley73
Assigned To:                BusyBox
====================================================================== 
Project:                    BusyBox
Issue ID:                   498
Category:                   Other
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             10-21-2005 20:15 PDT
Last Modified:              10-24-2005 10:28 PDT
====================================================================== 
Summary:                    mount loop device support broken
Description: 
Starting from some release after 1.0rc1, mounting loop devices (in my case
an ISO image) doesn't work right anymore. Right now I use 1.01
Under Kernel 2.4.31 it seems the mount doesn't find a free loop device and
you have to specife "mount -o loop=/dev/loop ...."
Under Kernel 2.6.13.2 I couldn't get it to work at all. I tried the latest
code from SVN about 3 weeks ago, but it doesn't work either.
Unfortunately I can't give you more information.
====================================================================== 

---------------------------------------------------------------------- 
 smiley73 - 10-24-05 06:44  
---------------------------------------------------------------------- 
I did some further testing and it doesn't seem to be dependend on the
Kernel release.
Modifying the mount command to use "-o loop=/dev/loop0" returns the error
message, that it's not a valid block device.
Setting up the loopback device via losetup before the mount also doesn't
solve the problem.
One test used glibc 2.3.2 (kernel 2.4) and the other glibc 2.3.5 (kernel
2.6).
Both times busybox was statically compiled and used in the InitRD. 

---------------------------------------------------------------------- 
 smiley73 - 10-24-05 10:28  
---------------------------------------------------------------------- 
Some further testing showed, that busybox 1.00 seems to work fine.
So the error must have been introduced after that.

Heiko 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-21-05 20:15  smiley73       New Issue                                    
10-21-05 20:15  smiley73       Status                   new => assigned     
10-21-05 20:15  smiley73       Assigned To               => BusyBox         
10-24-05 06:44  smiley73       Note Added: 0000640                          
10-24-05 10:28  smiley73       Note Added: 0000641                          
======================================================================