archive mirror
 help / color / mirror / Atom feed
From: Lucas De Marchi <>
To: linux-modules <>
Cc: Jessica Yu <>,
	Rusty Russell <>,
	lkml <>
Subject: [ANNOUNCE] kmod 26
Date: Thu, 7 Feb 2019 13:57:23 -0800	[thread overview]
Message-ID: <> (raw)

kmod 26 is out:

Now we also have a new archive for the mailing list:

- Improvements
        - Add more error-checking in library functions and remove
warnings on newer

        - Depmod now handles parallel invocations better by protecting
the temporary
          files being used

        - Improvements to testsuite and added tests to check the behavior
          regardless of the features enabled in the kernel and
libraries we link to

        - Teach the --show-exports option to modprobe. This works similarly to
          --show-modversions, but it reports the exported symbols from
that module.
          Under the hood this reads the .symtab and .strtab sections rather than
          __versions so it shows useful data even if kernel is
configured without
          modversions (CONFIG_MODVERSIONS)

        - Teach pkcs7 parsing to modinfo by using openssl. This allows
modinfo to
          correctly parse the signature appended to a module by the kernel build
          system when configured with CONFIG_MODULE_SIG_ALL, or when externally
          signed by the distro. Traditionally modules were signed and a struct
          was appended together with the signature to the end of the module.
          This has changed on the kernel for pkcs#7 and now the structure isn't
          filled out with useful information.  So we have to parse the signature
          block in order to return useful data to the user.

          If kmod is linked with openssl we parse the signature and return the
          fields as we do for other signatures. An example of the relevant part
          on the output of modinfo is below:

                  sig_id:         PKCS#7
                  sig_hashalgo:   md4
                  sig_id:         PKCS#7
                  signer:         Fedora kernel signing key
                  sig_hashalgo:   sha256

          If kmod is not linked to openssl we just start printing
"unknown" in the
          sig_hashalgo field rather than the bogus value.

Shortlog is below:

Caio Marcelo de Oliveira Filho (1):
      testsuite: add Clear's mkosi configuration

Chris Stackpole (1):
      Phrasing correction in modprobe man page

Daniel Kahn Gillmor (1):
      man: Fix typo

Jakov Simunic (1):
      build: fix wrong quotes on bootstrap

Jan Engelhardt (1):
      kmod: build: cure compiler warnings showing up externally

Luca Bruno (1):
      libkmod-module: check for NULL before accessing pointers

Lucas De Marchi (17):
      testsuite: raise arch image to 3GB
      man: depmod: remove deprecated -m option
      mkosi: allow Clear to use test modules
      testsuite: add simple test for --show-exports
      README: Add link to mailing list archive
      Remove bootstrap* scripts
      testsuite: split out function to compare outputs exactly
      testsuite: add support for testing output against regex
      testsuite: move --show-exports test to use regex
      Add semaphoreci 2.0 configuration
      testsuite: fix modinfo test without openssl
      build: enable openssl by default
      build: add openssl to CI deps
      build: check openssl version
      testsuite: mkosi: update files
      build: fix make distcheck
      kmod 26

Michal Suchanek (3):
      depmod: prevent module dependency files missing during depmod invocation
      depmod: prevent module dependency files corruption due to
parallel invocation.
      depmod: shut up gcc insufficinet buffer warning

Yauheni Kaliuta (6):
      modprobe: add --show-exports
      signature: do not report wrong data for pkc#7 signature
      testsuite: track number of descriptors instead of their state
      testsuite: factor out fd related parameters to a structure
      testsuite: add modinfo pkcs7 signature test
      libkmod-signature: implement pkcs7 parsing with openssl

Lucas De Marchi

                 reply	other threads:[~2019-02-07 21:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \ \ \
    --subject='Re: [ANNOUNCE] kmod 26' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).