| 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
| ||
|
Message-ID: <460396F5.5020509@slax.org> Date: Fri, 23 Mar 2007 09:59:33 +0100 From: Tomas M <tomas@...x.org> To: linux-kernel@...r.kernel.org Subject: Re: max_loop limit > wondering that here are 13 postings about loopdevice limitation, but > nobody giving any comment about dm-loop ( > http://sources.redhat.com/lvm2/wiki/DMLoop ), which is a solution for > this problem ...... If I understand it correctly, I would need 'dm' in kernel (or module) and moreover I would need some userspace utilities/binaries. > It can be used as a 1:1 replacement for classic loop and > should (?) probably be ready for mainline in the not too far future. So it is not in Kernel? With current loop, people would need kernel patch and *no* userspace utilities. With dm-loop, people would need kernel patch *and* userspace utilities. So, from my point of view, it would be better to fix/enhance Linux's loop. Tomas M slax.org - 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/
Powered by blists - more mailing lists