diff options
author | Catherine Zhang <cxzhang@watson.ibm.com> | 2006-08-02 14:12:06 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2006-08-02 14:12:06 -0700 |
commit | dc49c1f94e3469d94b952e8f5160dd4ccd791d79 (patch) | |
tree | e47b1974c262a03dbabf0a148325d9089817e78e /Kbuild | |
parent | 2b7e24b66d31d677d76b49918e711eb360c978b6 (diff) | |
download | kernel-crypto-dc49c1f94e3469d94b952e8f5160dd4ccd791d79.tar.gz kernel-crypto-dc49c1f94e3469d94b952e8f5160dd4ccd791d79.tar.xz kernel-crypto-dc49c1f94e3469d94b952e8f5160dd4ccd791d79.zip |
[AF_UNIX]: Kernel memory leak fix for af_unix datagram getpeersec patch
From: Catherine Zhang <cxzhang@watson.ibm.com>
This patch implements a cleaner fix for the memory leak problem of the
original unix datagram getpeersec patch. Instead of creating a
security context each time a unix datagram is sent, we only create the
security context when the receiver requests it.
This new design requires modification of the current
unix_getsecpeer_dgram LSM hook and addition of two new hooks, namely,
secid_to_secctx and release_secctx. The former retrieves the security
context and the latter releases it. A hook is required for releasing
the security context because it is up to the security module to decide
how that's done. In the case of Selinux, it's a simple kfree
operation.
Acked-by: Stephen Smalley <sds@tycho.nsa.gov>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions