Quoting Chris Wright ([EMAIL PROTECTED]):
* Serge E. Hallyn ([EMAIL PROTECTED]) wrote:
I guess now that I've written this out, it seems pretty clear
that capget64() and capget64() are the way to go. Any objections?
How is capget64() different from capget() that supports 2 different
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Serge E. Hallyn wrote:
Quoting Chris Wright ([EMAIL PROTECTED]):
* Serge E. Hallyn ([EMAIL PROTECTED]) wrote:
I guess now that I've written this out, it seems pretty clear
that capget64() and capget64() are the way to go. Any objections?
How is
Quoting Andrew Morgan ([EMAIL PROTECTED]):
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Serge E. Hallyn wrote:
Quoting Chris Wright ([EMAIL PROTECTED]):
* Serge E. Hallyn ([EMAIL PROTECTED]) wrote:
I guess now that I've written this out, it seems pretty clear
that capget64() and
* Serge E. Hallyn ([EMAIL PROTECTED]) wrote:
Quoting Chris Wright ([EMAIL PROTECTED]):
* Serge E. Hallyn ([EMAIL PROTECTED]) wrote:
I guess now that I've written this out, it seems pretty clear
that capget64() and capget64() are the way to go. Any objections?
How is capget64()
--- Al Viro [EMAIL PROTECTED] wrote:
On Tue, Oct 16, 2007 at 09:17:40PM -0700, Casey Schaufler wrote:
At random:
+static int smack_netlabel(struct sock *sk)
+{
+ static int initialized;
+ struct socket_smack *ssp = sk-sk_security;
+ struct netlbl_lsm_secattr secattr;
+
