Re: port-arm/50764 - kernel tries to load already active modules

[Paul Goyette <paul%whooppee.com@localhost>]

The following reply was made to PR kern/50764; it has been noted by GNATS.

From: Paul Goyette <paul%whooppee.com@localhost>
To: gnats-bugs%NetBSD.org@localhost
Cc: Martin Husemann <martin%duskware.de@localhost>
Subject: Re: port-arm/50764 - kernel tries to load already active modules
Date: Fri, 5 Feb 2016 17:37:10 +0800 (PHT)

 This is almost certainly happening from routine exec_autoload() in file 
 sys/kern/kern_exec.c
 
 Whenever an attempt to execute something for which the correct 
 "interpreter" does not exist, we will load the entire list of possible 
 interpreters.  (See the end of routine execve_loadvm() in the same 
 source file.)  The module(s) might already be loaded - execve_loadvm() 
 doesn't really care.  If they're already loaded, nothing bad should 
 happen.
 
 The real question that should be answered is whether or not the 
 executable being loaded really needs an interpreter other than those 
 that are already available.  /usr/tests/lib/libc/gen/posix_spawn/t_spawn 
 is cited as an example of a trigger for this behavior - what does 
 file(1) say about t_spawn?
 
 Of course, the crash you noted in 50760 should not happen, whether or 
 not the module is already loaded.  (You might enable sysctl variable 
 kern.module.verbose to get some additional hints/clues.)