Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

client/fingerprint: detect unloaded dynamic bridge kernel module #9299

Merged
merged 2 commits into from
Nov 10, 2020
Merged

client/fingerprint: detect unloaded dynamic bridge kernel module #9299

merged 2 commits into from
Nov 10, 2020

Commits on Nov 9, 2020

  1. client/fingerprint: detect unloaded dynamic bridge kernel module 

    In Nomad v0.12.0, the client added additional fingerprinting around the
presense of the bridge kernel module. The fingerprinter only checked in
`/proc/modules` which is a list of loaded modules. In some cases, the
bridge kernel module is builtin rather than dynamically loaded. The fix
for that case is in #8721. However we were still missing the case where
the bridge module is dynamically loaded, but not yet loaded during the
startup of the Nomad agent. In this case the fingerprinter would believe
the bridge module was unavailable when really it gets loaded on demand.

This PR now has the fingerprinter scan the kernel module dependency file,
which will contain an entry for the bridge module even if it is not yet
loaded.

In summary, the client now looks for the bridge kernel module in
 - /proc/modules
 - /lib/modules/<kernel>/modules.builtin
 - /lib/modules/<kernel>/modules.dep

Closes #8423
    @shoenig
    shoenig committed Nov 9, 2020
    Configuration menu
    Copy the full SHA
    52cef27 View commit details
    Browse the repository at this point in the history

  2. docs: add changelog entry

    @shoenig
    shoenig committed Nov 9, 2020
    Configuration menu
    Copy the full SHA
    3ad75f0 View commit details
    Browse the repository at this point in the history