Kernel module interface dependencies
View Patent ↗A method, and a corresponding mechanism, are used for resolving interface dependencies in kernel modules during an operating system (O/S) update. The method includes determining the O/S version for which each module is designed, determining a version of the updated O/S, comparing the O/S version for which each module is designed to the version of the updated O/S, and removing from the system those modules that are not compatible with the updated O/S.
1. A computer-implemented method for updating an operating system O/S by resolving interface dependencies in kernel modules, comprising:
determining an O/S version for which each module is designed;
determining a version of the updated O/S;
determining which modules are compatible with the updated O/S, comprising comparing the O/S version for which each module is designed to the version of the updated O/S; and
using the determination of compatible modules, retaining the compatible modules in the O/S and removing the non-compatible modules.
2. The method of claim 1 , wherein the updated O/S comprises an O/S interface, and wherein each module depends on the O/S interface.
3. The method of claim 2 , wherein each module includes a module description, and wherein the module description comprises an explicit indication of dependency on the O/S interface.
4. The method of claim 2 , wherein each module includes a module description, and wherein the module description comprises an implicit indication of dependency on the O/S interface.
5. The method of claim 2 , wherein the O/S interface is provided by a kconfig module.
6. The method of claim 1 , wherein determining the O/S version for which each module is designed comprises receiving a description of the module, the description including an indication of a requisite O/S version.
7. A computer-readable medium comprising a computer-implemented routine for updating a computer operating system (O/S) by managing dependencies between kernel modules and an O/S interface, the routine when executed comprising the steps of:
determining an O/S version for which each module is designed;
determining a version of the updated O/S;
determining which modules are compatible with the updated O/S, comprising comparing the O/S version for which each module is designed to the version of the updated O/S; and
using the determination of compatible modules, retaining the compatible module in the O/S and removing the non-compatible modules.
8. The computer-readable medium of claim 7 , wherein the updated O/S comprises an O/S interface, and wherein each module depends on the O/S interface.
9. The computer-readable medium of claim 8 , wherein the O/S interface is provided by a kconfig module.
10. The computer-readable medium of claim 7 , wherein each module includes a module description, and wherein the module description comprises an explicit indication of dependency on the O/S interface.
11. The computer-readable medium of claim 7 , wherein each module includes a module description, and wherein the module description comprises an implicit indication of dependency on the O/S interface.
12. The computer-readable medium of claim 7 , wherein determining the O/S version for which each module is designed comprises receiving a description of the module, the description including an indication of a requisite O/S version.