| 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: Wed, 16 Jan 2013 08:22:42 -0800 From: Arjan van de Ven <arjan@...ux.intel.com> To: Linus Torvalds <torvalds@...ux-foundation.org> CC: Tejun Heo <tj@...nel.org>, Ming Lei <ming.lei@...onical.com>, Alex Riesen <raa.lkml@...il.com>, Alan Stern <stern@...land.harvard.edu>, Jens Axboe <axboe@...nel.dk>, USB list <linux-usb@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Rusty Russell <rusty@...tcorp.com.au> Subject: Re: [PATCH] module, async: async_synchronize_full() on module init iff async is used > But no, it's not just some trivial one-liner. Especially the question > about "when to try to load the module that is given on the kernel > command line" is not trivial. Do we require that the module is in the > initrd and loadable basically immediate at boot? Do we try again after > switching the root filesystem? Things like that.. to load it from the root fs you tend to need... an elevator ;-) I think it's pretty fair to users to say that if you want something by default at boot time, you need to build it in... but for us to try a modprobe from the initrd is not too bad I suppose. probably need to do this around the time we initialize the block layer -- 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