[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070418092903.GA16910@2ka.mipt.ru>
Date: Wed, 18 Apr 2007 13:29:03 +0400
From: Evgeniy Polyakov <johnpol@....mipt.ru>
To: Patrick McHardy <kaber@...sh.net>
Cc: Pavel Emelianov <xemul@...ru>, David Miller <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>,
Andrew Morton <akpm@...l.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
devel@...nvz.org, Kirill Korotaev <dev@...nvz.org>
Subject: Re: [NETLINK] Don't attach callback to a going-away netlink socket
On Wed, Apr 18, 2007 at 11:16:50AM +0200, Patrick McHardy (kaber@...sh.net) wrote:
> > That is what I referred to as error path. Btw, with positive return
> > value we end up in subsequent call to input which will free callback
> > under lock as expected.
>
>
> No, nothing is going to call netlink_dump after the initial call since
> the socket is gone.
Argh, userspace socket's sk_data_rady() if dump returned positive value.
So, callback is not freed to allow to put several pages before
NLMSG_DONE via single dump?
--
Evgeniy Polyakov
-
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