mirror of
https://github.com/AuxXxilium/kmod.git
synced 2024-12-19 21:16:11 +07:00
kmod - Linux kernel module handling
c48b269d64
Since the beginning depmod just warned about dependency loops and upon
creation of modules.dep{,.bin} it skipped the modules that were part of
a loop. However just skipping the modules may come as a surprise to
kernel module developers: they will need to try to load the module (or
to pay attention to the log messages) to notice thavt the module has not
been put in the index. Also, differently from module-init-tools we were
not skipping modules that depend on modules with dependency loops,
leading to a segfault in depmod.
So this is a summary of the change in behavior with this patch:
Loop 1)
A -> B -> C -
^ |
'------------
Before:
depmod: WARNING: found 3 modules in dependency cycles!
depmod: WARNING: /tmp/test-kmod/lib/modules/3.14.2-1-ARCH/kernel/moduleB.ko in dependency cycle!
depmod: WARNING: /tmp/test-kmod/lib/modules/3.14.2-1-ARCH/kernel/moduleC.ko in dependency cycle!
depmod: WARNING: /tmp/test-kmod/lib/modules/3.14.2-1-ARCH/kernel/moduleA.ko in dependency cycle!
return code: 0
After:
depmod: ERROR: Found 3 modules in dependency cycles!
depmod: ERROR: /tmp/test-kmod/lib/modules/3.14.2-1-ARCH/kernel/moduleB.ko in dependency cycle!
depmod: ERROR: /tmp/test-kmod/lib/modules/3.14.2-1-ARCH/kernel/moduleC.ko in dependency cycle!
depmod: ERROR: /tmp/test-kmod/lib/modules/3.14.2-1-ARCH/kernel/moduleA.ko in dependency cycle!
return code: 2
Loop 2)
A -> B -> C -
^ |
'-------
Before:
depmod: WARNING: found 2 modules in dependency cycles!
depmod: WARNING: /tmp/test-kmod//lib/modules/3.14.2-1-ARCH/kernel/moduleB.ko in dependency cycle!
depmod: WARNING: /tmp/test-kmod//lib/modules/3.14.2-1-ARCH/kernel/moduleC.ko in dependency cycle!
Segmentation fault (core dumped)
After:
depmod: ERROR: Found 2 modules in dependency cycles!
depmod: ERROR: /tmp/test-kmod/lib/modules/3.14.2-1-ARCH/kernel/moduleB.ko in dependency cycle!
depmod: ERROR: /tmp/test-kmod/lib/modules/3.14.2-1-ARCH/kernel/moduleC.ko in dependency cycle!
return code: 2
The segfault above could be fixed, but let's just fail everything
because dependency cycles should be fixed in the modules rather than
just be skipped in the index.
|
||
|---|---|---|
| libkmod | ||
| m4 | ||
| man | ||
| shell-completion/bash | ||
| testsuite | ||
| tools | ||
| .gitignore | ||
| .travis.yml | ||
| autogen.sh | ||
| bootstrap | ||
| bootstrap-configure | ||
| CODING-STYLE | ||
| configure.ac | ||
| COPYING | ||
| Makefile.am | ||
| NEWS | ||
| README | ||
| TODO | ||
kmod - Linux kernel module handling
OVERVIEW
========
kmod is a set of tools to handle common tasks with Linux kernel modules like
insert, remove, list, check properties, resolve dependencies and aliases.
These tools are designed on top of libkmod, a library that is shipped with
kmod. See libkmod/README for more details on this library and how to use it.
The aim is to be compatible with tools, configurations and indexes from
module-init-tools project.
Compilation and installation
============================
In order to compiler the source code you need following software packages:
- GCC compiler
- GNU C library
Optional dependencies:
- ZLIB library
- LZMA library
Typical configuration:
./configure CFLAGS="-g -O2" --prefix=/usr \
--sysconfdir=/etc --libdir=/usr/lib
Configure automatically searches for all required components and packages.
To compile and install run:
make && make install
Hacking
=======
Run 'bootstrap' script before configure. If you want to accept the recommended
flags, you just need to run 'bootstrap-configure'.
Make sure to read the CODING-STYLE file and the other READMEs: libkmod/README
and testsuite/README.
Information
===========
Signed packages:
http://www.kernel.org/pub/linux/utils/kernel/kmod/
Mailing list:
linux-modules@vger.kernel.org (no subscription needed)
Git:
git://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git
http://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git
https://git.kernel.org/pub/scm/utils/kernel/kmod/kmod.git
Gitweb:
http://git.kernel.org/?p=utils/kernel/kmod/kmod.git
Irc:
#kmod on irc.freenode.org
Compatibility with module-init-tools
====================================
kmod replaces module-init-tools, which is end-of-life. Most of its tools are
rewritten on top of libkmod so it can be used as a drop in replacements.
Somethings however were changed. Reasons vary from "the feature was already
long deprecated on module-init-tools" to "it would be too much trouble to
support it".
There are several features that are being added in kmod, but we don't
keep track of them here.
modprobe
--------
* 'modprobe -l' was marked as deprecated and does not exist anymore
* 'modprobe -t' is gone, together with 'modprobe -l'
* modprobe doesn't parse configuration files with names not ending in
'.alias' or '.conf'. modprobe used to warn about these files.
* modprobe doesn't parse 'config' and 'include' commands in configuration
files.
* modprobe from m-i-t does not honour softdeps for install commands. E.g.:
config:
install bli "echo bli"
install bla "echo bla"
softdep bla pre: bli
With m-i-t, the output of 'modprobe --show-depends bla' will be:
install "echo bla"
While with kmod:
install "echo bli"
install "echo bla"
* kmod doesn't dump the configuration as is in the config files. Instead it
dumps the configuration as it was parsed. Therefore, comments and file names
are not dumped, but on the good side we know what the exact configuration
kmod is using. We did this because if we only want to know the entire content
of configuration files, it's enough to use find(1) in modprobe.d directories
depmod
------
* there's no 'depmod -m' option: legacy modules.*map files are gone
lsmod
-----
* module-init-tools used /proc/modules to parse module info. kmod uses
/sys/module/*, but there's a fallback to /proc/modules if the latter isn't
available