linux-kernel - Re: BUG: key ffff8800192a6ad0 not in .data!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 15 Dec 2013 15:14:13 -0800
From:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Fengguang Wu <fengguang.wu@...el.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: BUG: key ffff8800192a6ad0 not in .data!

On Sun, Dec 15, 2013 at 03:12:03PM -0700, Bjorn Helgaas wrote:
> On Sun, Dec 15, 2013 at 10:04 AM, Greg Kroah-Hartman
> <gregkh@...uxfoundation.org> wrote:
> > On Sun, Dec 15, 2013 at 02:31:23PM +0800, Fengguang Wu wrote:
> >> Greetings,
> >>
> >> I got the below dmesg and the first bad commit is
> >
> > I thought this was already fixed in Bjorn's tree, but perhaps he hasn't
> > merged in the one-liner for it...
> 
> Yes, this is fixed.  I actually dropped that MSI change temporarily
> until we can fold in the memory leak fixes, so it is not currently in
> linux-next.

Do you want me to just resend a fixed patch up with the one-line fix,
and the memory-leak-on-error-path fix all as just one patch to make it
easier for you?

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/