linux-kernel - (1 loop device) Re: [1/3] 2.6.22-rc1: known regressions v2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 17 May 2007 01:11:46 +0400
From:	Alexey Dobriyan <adobriyan@...il.com>
To:	Michal Piotrowski <michal.k.k.piotrowski@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: (1 loop device) Re: [1/3] 2.6.22-rc1: known regressions v2

On Wed, May 16, 2007 at 10:31:30PM +0200, Michal Piotrowski wrote:
> Block devices
>
> Subject    : loop devices limited to one single device
> References : http://lkml.org/lkml/2007/5/16/229
> Submitter  : Uwe Bugla <uwe.bugla@....de>
> Status     : Unknown

>> The patch against loop.c is neither a fix, nor does it create
>> loop devices on demand:

It does. In kernel memory.

>> Facts are instead, at least on my machine:

>> The number of available loop devices is reduced from 8 (conventional
>> standard of preceding 2.6 kernels) to 1.

>> The consequence is: If you have to mount more than one single iso-image
>> with
>> the loop parameter you are receiving the following message during system
>> boot:

>> "mount: could not find any free loop device"

I suggest to read mknod(1) manpage.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/