Hi,

On Busybox 1.31.1, modprobing any module for the 5.10 kernel prints a
nasty message:
Module has invalid ELF header

but the module loads successfully after that. So looks like bb tries
two paths, the first fails, second succeeds. It's rather unsightly to
get a high priority kernel error though.

The message seems to have been introduced in v5.9 rc4, before that it
was a silent failure. It's a pr_err, so it gets printed to console on
the "quiet" log level too.

CCing the authors and reviewers of the kernel patch, in case it's not
intentional to print such a high error for that path.

- Lauri

Attachment: busybox-1.31.1_config.nosuid.gz
Description: Binary data

_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox

Reply via email to