Lines Matching full:failures
29 * loading failures to enable improvements either for kernel module auto-loading
31 * provided to track all possible failures in the finit_module() path and memory
57 * failures.
114 * failures:
120 * * invalid_kread_bytes: bytes allocated and then freed on failures which
131 * failures can happen if we had a check in between a successful kernel_read_file_from_fd()
144 * to begin to process prior requests. Although duplicate failures can be
151 * failures. These failures can occur because:
164 * freed due to failures after we did all the sanity checks of the module
185 * private space for our module using layout_and_allocate(). These failures
189 * These failures are good signs the kernel or userspace is doing something
343 * The counters for imod_bytes does not increase for fkreads failures in read_file_mod_stats()