Ville Juven 64d8249895 sched/addrenv, binfmt: Always allocate address environment from heap ... Instead of using a volatile storage for the address environment in the binfmt / loadinfo structures, always allocate the address environment from kheap. This serves two purposes: - If the task creation fails, any kernel thread that depends on the address environment created during task creation will not lose their mappings (because they hold a reference to it) - The current address environment variable (g_addrenv) will NEVER contain a stale / incorrect value - Releasing the address environment is simplified as any pointer given to addrenv_drop() can be assumed to be heap memory - Makes the kludge function addrenv_clear_current irrelevant, as the system will NEVER have invalid mappings any more		2023-04-22 00:43:30 +08:00
..
addrenv.c	sched/addrenv, binfmt: Always allocate address environment from heap	2023-04-22 00:43:30 +08:00
Make.defs