From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Wright Subject: Re: [RFC] SO_PEERSEC - security credentials for Unix stream sockets Date: Mon, 15 Dec 2003 17:32:41 -0800 Sender: linux-security-module-bounces@wirex.com Message-ID: <20031215173241.B14552@osdlab.pdx.osdl.net> References: <20031212161617.C24246@osdlab.pdx.osdl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "David S. Miller" , kuznet@ms2.inr.ac.ru, linux-security-module@wirex.com, Stephen Smalley , netdev@oss.sgi.com Return-path: To: James Morris Content-Disposition: inline In-Reply-To: ; from jmorris@redhat.com on Fri, Dec 12, 2003 at 10:44:24PM -0500 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: linux-security-module-bounces@wirex.com List-Id: netdev.vger.kernel.org * James Morris (jmorris@redhat.com) wrote: > I'm not sure how this would be a namespace issue -- do you mean a data > format issue? I just mean, applications are coded for specific security module. > Yep, allowing the security module to update the returned length is now > implemented. > > > Perhaps buffer is too small, can len be vector for that info? > > I would not advise updating len on error -- it's a bad idea in general to > interpret any returned data from failed syscalls except the error number. Right, in some cases a NULL buffer or 0 buflen is a probe for size. thanks, -chris -- Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net