linux-kernel - Re: /dev/loop* devices not appearing in /dev (at least since 2.6.22-rc3*)

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, 14 Jun 2007 17:44:48 +0200
From:	markus reichelt <ml@...eichelt.de>
To:	linux-kernel@...r.kernel.org
Subject: Re: /dev/loop* devices not appearing in /dev (at least since
 2.6.22-rc3*)

* Paolo Ornati <ornati@...twebnet.it> wrote:

> So with this patch "max_loop=32" will create 32 loop devices... but
> then it doesn't allow more of them.

Well, that's what a max_ parameter implies ;p

A manually set limit of loop devices is ok with me. (32 was just an
example -- After all, I could have chosen 256 just to annoy some
people :-)

And with the recent hype of creating things when needed, or even
recycling already used ones (sdx), I worry that this impacts
stability or even usability as a whole. (yes, it's a -rc release ...)

I'll be staying with 2.6.20.x for a year or so. Get the newly
introduced bugs squashed before they have a chance to bug me, heh ;P

PS: Just wondering: Who came up with this "on-demand" hype?
-- 
left blank, right bald

Content of type "application/pgp-signature" skipped