All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Sedat Dilek <sedat.dilek@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Subject: Re: [PATCH 3.18 00/39] 3.18.7-stable review
Date: Mon, 9 Feb 2015 23:44:56 +0800	[thread overview]
Message-ID: <20150209154456.GA4539@kroah.com> (raw)
In-Reply-To: <CA+icZUUvfNy2ASvcnONk3-KQ74boZFc4xG7c=mcAQU4k42NeZQ@mail.gmail.com>

On Mon, Feb 09, 2015 at 04:35:53PM +0100, Sedat Dilek wrote:
> Hi Greg,
> 
> nice to see the kbuild and trace patches I was involved are in this series.
> 
> Unfortunately, I see the following in my logs...
> 
> [    2.117022] Request for unknown module key 'Magrathea: Glacier
> signing key: 009aa341bb673735a51dc34b238a0ca481d68098' err -11
> [    2.117114] mii: module verification failed: signature and/or
> required key missing - tainting kernel
> 
> Not sure whom to CC.
> I CCed Jeff as he worked on MII.
> Signing key ---> Dave Howells?
> 
> Attached are my kernel-config and dmesg output.
> 
> Hope this helps.
> 
> BTW, with v3.18.6 I haven't seen such output.

Any way you could take the patches at
https://git.kernel.org/cgit/linux/kernel/git/stable/stable-queue.git/
in the queue-3.18 directory and bisect them to see which patch causes
the problem?  I don't see any obvious patch in this series that would be
the issue.

thanks,

greg k-h

  reply	other threads:[~2015-02-09 15:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 15:35 [PATCH 3.18 00/39] 3.18.7-stable review Sedat Dilek
2015-02-09 15:44 ` Greg Kroah-Hartman [this message]
2015-02-09 15:58   ` Sedat Dilek
2015-02-09 16:02     ` Sedat Dilek
2015-02-10  7:24       ` Sedat Dilek
  -- strict thread matches above, loose matches on Subject: below --
2015-02-09  8:33 Greg Kroah-Hartman
2015-02-09 16:40 ` Guenter Roeck
2015-02-09 18:27 ` Shuah Khan
2015-02-09 21:37   ` Greg Kroah-Hartman
2015-02-09 22:03     ` Guenter Roeck
2015-02-09 22:24       ` Winkler, Tomas
2015-02-09 23:19         ` Shuah Khan

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=20150209154456.GA4539@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sedat.dilek@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.