[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20140923.113738.2189831519873566622.davem@davemloft.net>
Date: Tue, 23 Sep 2014 11:37:38 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: richard.alpe@...csson.com
Cc: netdev@...r.kernel.org, tipc-discussion@...ts.sourceforge.net
Subject: Re: [PATCH net-next 04/14] tipc: add sock dump to new netlink api
From: Richard Alpe <richard.alpe@...csson.com>
Date: Tue, 23 Sep 2014 13:12:47 +0200
> Ideally I would like to use the existing dump framework .dumpit
> (netlink_dump_start()) but I can't figure out a way to pass the socket
> for which to dump publications. I really don't want to reinvent the
> dumping mechanism. Any suggestions?
Look at inet_diag, and how the dump netlink request passes in a key
to match upon.
The key is of the form: include/uapi/linux/inet_diag.h:inet_diag_req{,_v2}
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists