[BusyBox 0000931]: mount -o loop is broken again

[bugs at busybox.net]

The following issue has been CLOSED 
====================================================================== 
http://busybox.net/bugs/view.php?id=931 
====================================================================== 
Reported By:                STV
Assigned To:                BusyBox
====================================================================== 
Project:                    BusyBox
Issue ID:                   931
Category:                   Other
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
Resolution:                 no change required
Fixed in Version:           
====================================================================== 
Date Submitted:             07-02-2006 13:14 PDT
Last Modified:              09-30-2006 13:21 PDT
====================================================================== 
Summary:                    mount -o loop is broken again
Description: 
I see that this has been broken before and it has been fixed as well, but
im pretty darn sure the current code is b0rken.

im trying to mount an image produced by buildroot on a busybox based
system using -o loop.  It fails telling me

mount: Couldn't setup loop device.

I know its not a show-stopped, but its pretty annoying for me since i was
planning to use this as a way of providing a "firmware" update feature
(mounitng the file and reimaging the system using it as a source).  a
quick fix would be much appreciated - im about to stick gdb on it to see
what i can dig up.
====================================================================== 

---------------------------------------------------------------------- 
 vda - 09-29-06 14:40  
---------------------------------------------------------------------- 
if CONFIG_FEATURE_DEVFS=y, mount tries to use /dev/loop/N,
if not, it uses /dev/loopN.

This is trivially obvious if you will run strace. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
07-02-06 13:14  STV            New Issue                                    
07-02-06 13:14  STV            Status                   new => assigned     
07-02-06 13:14  STV            Assigned To               => BusyBox         
09-29-06 14:40  vda            Note Added: 0001655                          
09-29-06 14:42  vda            Status                   assigned => resolved
09-29-06 14:42  vda            Resolution               open => no change
required
09-30-06 13:21  vda            Status                   resolved => closed  
======================================================================