From: Chris Wright Subject: Re: [RFC][PATCH 2/3] netlink check sender, audit Date: Tue, 15 Feb 2005 16:11:20 -0800 Message-ID: <20050216001120.GJ15867@shell0.pdx.osdl.net> References: <20050212010243.W24171@build.pdx.osdl.net> <20050212010504.X24171@build.pdx.osdl.net> <420E334B.8060805@eurodev.net> <420E77FA.6080007@eurodev.net> <20050215001334.GB27645@shell0.pdx.osdl.net> <42115E7E.6050909@eurodev.net> <20050215034708.GG27645@shell0.pdx.osdl.net> <4212757D.5070401@eurodev.net> <20050215222246.GI15867@shell0.pdx.osdl.net> <42127764.5050507@eurodev.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Chris Wright , netdev@oss.sgi.com, davem@davemloft.net, jmorris@redhat.com, sds@epoch.ncsc.mil, serue@us.ibm.com To: Pablo Neira Content-Disposition: inline In-Reply-To: <42127764.5050507@eurodev.net> Sender: netdev-bounce@oss.sgi.com Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org * Pablo Neira (pablo@eurodev.net) wrote: > I was aware of that. Actually I think that we can modify all calls to > netlink_kernel_create (that aren't that much) to fit the new interface, > I can post a patch to do that. I prefer providing just one function to > create a netlink socket in kernel space. My only thought is as an exported symobl it's harder to be clear on who's using it (possibly out-of-tree). thanks, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net