| I was just looking at doing that.
Did you have any ideas for a better solution?
| I'd suggest including CONFIG_CRYPTO_TEST in the default size
| determination, and allowing both smaller sizes (for low ram
| applications, such as embedded systems) and larger ones.
and I'd agree with the latter half of this, but I think that if
one <quote> Quick & dirty crypto test module </quote> causes a
log buffer overrun, the general kernel config doesn't need to provide
a solution for it.
| With all of the crypto =y, the test wipes everything before ACPI out
| of the buffer before syslogd gets to start and log the buffer to disk.
| Even with a 64k buffer.
Use a larger buffer or reduce the output?
-- ~Randy- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/