[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f34abd0903091121g73d6cdeeqfa8353b55a3e9607@mail.gmail.com>
Date: Mon, 9 Mar 2009 19:21:00 +0100
From: Vegard Nossum <vegard.nossum@...il.com>
To: Alex Chiang <achiang@...com>, 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
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.
Hi,
Sorry for butting in, just wondering if I could have the patch to fix
the double free? :-)
Vegard
--
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
-- E. W. Dijkstra, EWD1036
--
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