| 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: <20070322143314.GX4095@ftp.linux.org.uk> Date: Thu, 22 Mar 2007 14:33:14 +0000 From: Al Viro <viro@....linux.org.uk> To: Jens Axboe <jens.axboe@...cle.com> Cc: Eric Dumazet <dada1@...mosbay.com>, Tomas M <tomas@...x.org>, linux-kernel@...r.kernel.org Subject: Re: max_loop limit On Thu, Mar 22, 2007 at 02:42:31PM +0100, Jens Axboe wrote: > But this still wastes memory, why not just allocate each loop device > dynamically when it is set up? The current approach is crap, it is just > wasting memory for loop devices, queues, etc. Correction: current ABI is crap. To set the thing up you need to open it and issue an ioctl. Which is a bloody bad idea, for obvious reasons... - 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