---
- branch: netbsd-8
  date: Thu Dec 21 21:37:03 UTC 2017
  files:
  - new: 1.125.2.1
    old: '1.125'
    path: src/sys/kern/kern_module.c
    pathrev: src/sys/kern/kern_module.c@1.125.2.1
    type: modified
  id: 20171221T213703Z.6b2b9aaf9d96319e5c0ad43deba87c4f455bb2ac
  log: "Pull up following revision(s) (requested by pgoyette in ticket #449):\n\tsys/kern/kern_module.c:
    1.126-1.130\nAdd additional duplicate-module-name check in case we have two modules\nwith
    the same internal name but no conflicting symbol definitions.\nWhen we load a
    module from the file system, the filename may have no\nrelationship to the internal
    module's name.  Furthermore, comparing\nthe module's filename is insufficient
    if the file is loaded from an\nabsolute path.\n--\nUse KASSERT to ensure that
    the newly-added module's name can be found.\n--\nChange a KASSERTMSG into a regular
    module_error - not nice for the\nkernel\nto panic when I try to modload the 'ntfs'
    module.\n--\nWhen looking for a duplicate module name, also check the pending
    list.\n--\nRemove the check for duplicate-module-name-on-pending-list since it
    really\ndoesn't help.  The check really cannot fail, and it only looks at the
    list\nbelonging to the current level of recursion.\nInstead, verify that the module's
    modcmd(MODULE_CMD_INIT, ...) does not\nintroduce a duplicate module name as a
    result of recursively calling\nmodule_do_load().\n"
  module: src
  subject: 'CVS commit: [netbsd-8] src/sys/kern'
  unixtime: '1513892223'
  user: snj