Module Name: src
Committed By: pgoyette
Date: Sun Sep 29 00:57:12 UTC 2019
Modified Files:
src/doc: TODO.modules
Log Message:
Another issue, as identified on IRC/ICB
To generate a diff of this commit:
cvs rdiff -u -r1.19 -r1.20 src/doc/TODO.modules
Please note that diffs are not public domain; they are subject to the
copyright notices on the relevant files.
Modified files:
Index: src/doc/TODO.modules
diff -u src/doc/TODO.modules:1.19 src/doc/TODO.modules:1.20
--- src/doc/TODO.modules:1.19 Wed Feb 20 04:32:51 2019
+++ src/doc/TODO.modules Sun Sep 29 00:57:11 2019
@@ -1,4 +1,4 @@
-/* $NetBSD: TODO.modules,v 1.19 2019/02/20 04:32:51 pgoyette Exp $ */
+/* $NetBSD: TODO.modules,v 1.20 2019/09/29 00:57:11 pgoyette Exp $ */
Some notes on the limitations of our current (as of 7.99.35) module
subsystem. This list was triggered by an Email exchange between
@@ -219,3 +219,12 @@ christos and pgoyette.
detail, but I have to wonder how code that compiles cleanly in a
normal kernel has these issues when compiled in a module, when both
are done with WARNS=5).
+
+23. The current process of "load all the emulation/exec modules in case
+ one of them might handle the image currently being exec'd" isn't
+ really cool. (See sys/kern/kern_exec.c?) It ends up auto-loading
+ a whole bunch of modules, involving file-system access, just to have
+ most of the modules getting unloaded a few seconds later. We don't
+ have any way to identify which module is needed for which image (ie,
+ we can't determine that an image needs compat_linux vs some other
+ module).
