[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090309184131.GI32589@ldl.fc.hp.com>
Date: Mon, 9 Mar 2009 12:41:31 -0600
From: Alex Chiang <achiang@...com>
To: Vegard Nossum <vegard.nossum@...il.com>
Cc: Matthew Wilcox <matthew@....cx>, Greg KH <greg@...ah.com>,
kay.sievers@...y.org, rjw@...k.pl, linux-kernel@...r.kernel.org,
linux-pci@...r.kernel.org
Subject: Re: kobj refcounting weirdness
* Vegard Nossum <vegard.nossum@...il.com>:
> 2009/3/9 Alex Chiang <achiang@...com>:
> > * Matthew Wilcox <matthew@....cx>:
> >> On Mon, Mar 09, 2009 at 10:50:10AM -0600, Alex Chiang wrote:
> >> > I thought about the allocators returning a pointer to the same
> >> > location that maybe has some valid looking data hanging around,
> >> > but it's not wise for someone like me to go pointing fingers at
> >> > the allocator before I've proven the bug isn't in my code. ;)
> >>
> >> Slab poisoning would be the logical next thing to try to decide whether
> >> the allocator is wrong or you're using it wrong ;-)
> >
> > We had a double free in the PCIe port driver. Removing the double
> > free seems to fix my issue.
> >
> > The double free is only in Jesse's linux-next branch, so no need
> > to worry about it in mainline/stable.
>
> Sorry for butting in, just wondering if I could have the patch to fix
> the double free? :-)
http://thread.gmane.org/gmane.linux.kernel.pci/3524
Remember, it only applies to Jesse's linux-next, since it has
Rafael's latest port driver cleanups.
If you apply it to mainline, you will leak memory.
Thanks.
/ac
--
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/
Powered by blists - more mailing lists