Lines Matching full:modules

64  * DOC: dup_failed_modules - tracks duplicate failed modules
66  * Linked list of modules which failed to be loaded because an already existing
79  * All virtual memory allocated to these failed modules will be freed with
82  * To help with this the dup_failed_modules allows us to track modules which
116  *   * total_mod_size: total bytes ever used by all modules we've dealt with on
130  *     promote it to be processed to be added to our @modules linked list. These
136  *     add_unformed_module() will add a module to our &modules list and
137  *     subsequent loads of modules with the same name will error out at the
140  *     on layout_and_allocate() for modules already being processed. These
141  *     duplicate failed modules are non-fatal, however they typically are
175  *  * modcount: how many modules we've loaded in our kernel life time
176  *  * failed_kreads: how many modules failed due to failed kernel_read_file_from_fd()
180  *  * failed_becoming: how many modules failed after we kernel_read_file_from_fd()
184  *  * failed_load_modules: how many modules failed once we've allocated our
191  *    but it is perhaps not easy to fix them. A recent example are the modules
192  *    requests incurred for frequency modules, a separate module request was
379 	len += scnprintf(buf + len, size - len, "Duplicate failed modules:\n");  in read_file_mod_stats()