"Kirill A. Shutemov" <[email protected]> writes: > init_module(2) passes user-specified buffer length directly to > vmalloc(). It makes warn_alloc_failed() to print out a lot of info into > dmesg if user specified insane size, like -1. > > Let's silence the warning. It doesn't add much value to -ENOMEM return > code. Without the patch the syscall is prohibitive noisy for testing > with trinity.
Heh, we used to have an explicit length check because vmalloc would BUG(). So I guess this is progress... Applied thanks, Rusty. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
