[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <201404242051.DBE04650.SOMVHtQFFOLFOJ@I-love.SAKURA.ne.jp>
Date: Thu, 24 Apr 2014 20:51:35 +0900
From: Tetsuo Handa <penguin-kernel@...ove.SAKURA.ne.jp>
To: paul@...l-moore.com, casey@...aufler-ca.com
Cc: netdev@...r.kernel.org, linux-security-module@...r.kernel.org
Subject: xfrm: Can "struct netlbl_audit" be killed?
Hello, Casey and Paul.
At the ipsec-next tree,
/* Audit Information */
struct xfrm_audit {
u32 secid;
kuid_t loginuid;
unsigned int sessionid;
};
has just been killed
( https://git.kernel.org/cgit/linux/kernel/git/klassert/ipsec-next.git/commit/?id=f1370cc4a01e61007ab3020c761cef6b88ae3729 and
https://git.kernel.org/cgit/linux/kernel/git/klassert/ipsec-next.git/commit/?id=2e71029e2c32ecd59a2e8f351517bfbbad42ac11 )
because these arguments are always calculated from current thread's security
context.
Looking at other security_secid_to_secctx() users, I noticed that
a similar struct in the netlabel code.
/* NetLabel audit information */
struct netlbl_audit {
u32 secid;
kuid_t loginuid;
unsigned int sessionid;
};
Do you know whether we can kill "struct netlbl_audit" as well?
(In other words, is "bool" sufficient for representing "struct netlbl_audit" ?)
Regards.
--
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