Re: losetup -a only reporting a maximum of 256 loop devices

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Nov 01, 2007 at 09:50:36PM +0100, devzero@xxxxxx wrote:
> > Read the code. It doesn't check for all devices in range 0..256 -- it
> > breaks the for() loop when a /dev/loopN doesn't exist. For example on
> > my system it doesn't check for more than nine device. I don't see a
> > problem with a huge limit.
> 
> ah, ok - thanks for explaining.
> but, anyway - it`s a little bit weird that it stops checking if
> there is a "gap" in between.

 Yes, "gaps" are problem. I think we can try to use /sys/block/loop*
 for "losetup -a" and opendir("/dev") + readdir() for "losetup -f".

 That's probably better than blindly try to call stat(2) for all
 possible loop devices. I'll prepare a patch next week.

    Karel

-- 
 Karel Zak  <kzak@xxxxxxxxxx>
-
To unsubscribe from this list: send the line "unsubscribe util-linux-ng" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux