linux-kernel - Re: linux-next: build failure after merge of the pm tree

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 for Android: free password hash cracker in your pocket

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

Message-ID: <2023771.7SV6akbkpr@vostro.rjw.lan>
Date:	Mon, 09 Feb 2015 16:10:36 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Lorenzo Pieralisi <lorenzo.pieralisi@....com>,
	Jiang Liu <jiang.liu@...ux.intel.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the pm tree

On Monday, February 09, 2015 06:23:40 AM Lorenzo Pieralisi wrote:
> On Mon, Feb 09, 2015 at 05:36:07AM +0000, Jiang Liu wrote:
> > Hi Rafael and Lorenzo,
> > 	With more closer review, I suspect statement "kfree(bus_range)"
> > in commit d2be00c0fb5a ("of/pci: Free resources on failure in
> > of_pci_get_host_bridge_resources()") may cause double free of bus_range
> > because bus_range will also be freed by kfree(window->res);
> 
> Gah, my bad, you are right, sorry I missed that. Please let me know
> how you prefer fixing that, you could remove that line as part
> of the merge commit, or I can send you a patch to apply on top of it,
> it is a trivial one-line removal.

I re-did the merge.

Please have a look at my linux-next branch again and let me know if that's OK
with everybody.


-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
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/