linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.demarchi@profusion.mobi>
To: linux-modules <linux-modules@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	linux-hotplug <linux-hotplug@vger.kernel.org>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: [ANNOUNCE] kmod 12
Date: Wed, 05 Dec 2012 03:52:57 +0000	[thread overview]
Message-ID: <CAMOw1v6gc-NV8M8cHX9novwDv57zWMtoLHn6P22GGJ0QW2wFww@mail.gmail.com> (raw)

kmod 12 is out:

ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-12.tar.xz
ftp://ftp.kernel.org/pub/linux/utils/kernel/kmod/kmod-12.tar.sign


Bug fix release only. Copying the NEWS section here for brevity:

       - Fix removing vermagic from module when told to force load a module
       - Fix removing __versions section when told to force load a module: we
         need to mangle the section header, not the section.
       - modinfo no longer fails while loading a module from file when path
         contains ".ko" substring

Interesting that there was no previous bug report of "modprobe -f"
failing, yet before this release it was not working properly. Maybe
people are not tainting their kernel as frequently as I imagined.

Shortlog is below.


Cheers
Lucas De Marchi

---

Aleksey Makarov (1):
      fix is_module_filename()

Lucas De Marchi (7):
      depmod: fix hash lookup by relpath instead of uncrelpath
      depmod: fix asserting mod->kmod = NULL
      libkmod-module: Remove key+value vermagic from .modinfo section
      libkmod-module: mangle the section header, not the section
      Use bool instead of int
      depmod: fix checking file extension
      kmod 12

                 reply	other threads:[~2012-12-05  3:52 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=CAMOw1v6gc-NV8M8cHX9novwDv57zWMtoLHn6P22GGJ0QW2wFww@mail.gmail.com \
    --to=lucas.demarchi@profusion.mobi \
    --cc=linux-hotplug@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=rusty@rustcorp.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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 read-only IMAP folder(s) and NNTP newsgroup(s).