[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87pqagzcn8.fsf@skywalker.in.ibm.com>
Date: Mon, 07 May 2012 12:44:03 +0530
From: "Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>
To: Rusty Russell <rusty@...tcorp.com.au>,
Sasha Levin <levinsasha928@...il.com>, davem@...emloft.net,
ericvh@...il.com, jvrao@...ux.vnet.ibm.com
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
davej@...hat.com, Sasha Levin <levinsasha928@...il.com>
Subject: Re: [PATCH] 9p: disconnect channel when PCI device is removed
Rusty Russell <rusty@...tcorp.com.au> writes:
> On Fri, 13 Apr 2012 17:48:36 -0400, Sasha Levin <levinsasha928@...il.com> wrote:
>> When a virtio_9p pci device is being removed, we should close down any
>> active channels and free up resources, we're not supposed to BUG() if there's
>> still an open channel since it's a valid case when removing the PCI device.
>>
>> Otherwise, removing the PCI device with an open channel would cause the
>> following BUG():
>
> (Damn changed notmuch.el bindings! Previous reply went only to Sasha).
>
> Applied thanks,
> Rusty.
I am not sure whether the patch is sufficient, p9_virtio_remove does a
kfree(chan) and since we are not doing anything at the file system
level, we would still allow new 9p client request. That means
p9_virtio_request would be dereferencing a freed memory.
-aneesh
--
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