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
| ||
|
Date: Mon, 21 May 2007 10:04:30 -0700 (PDT) From: Linus Torvalds <torvalds@...ux-foundation.org> To: Ken Chen <kenchen@...gle.com> cc: Kay Sievers <kay.sievers@...y.org>, Ray Lee <ray-lk@...rabbit.org>, Al Viro <viro@....linux.org.uk>, Andrey Borzenkov <arvidjaar@...l.ru>, Uwe Bugla <uwe.bugla@....de>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Andrew Morton <akpm@...ux-foundation.org>, Michal Piotrowski <michal.k.k.piotrowski@...il.com> Subject: Re: bug in 2.6.22-rc2: loop mount limited to one single iso image On Mon, 21 May 2007, Ken Chen wrote: > > So I propose we do the following: > > 1. have the module honor "max_loop" parameter and create that many > device upfront on module load (max_loop will also be a hard max) iff > user specify the parameter. > 2. if max_loop is not specified, default create 8 loop device. User > can extent more loop device by create device node themselves and have > kernel automatically instantiate loop device on-demand. > > Is this acceptable? Patch in a bit. That sounds perfect. Linus - 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