| commit | 334c85569b8adeaa820c0f2fab3c8f0a9dc8b92e | |
| author | Venkat Yekkirala <vyekkirala@TrustedCS.com> | |
| Tue, 16 Jan 2007 00:38:45 +0000 (15 16:38 -0800) | ||
| committer | David S. Miller <davem@sunset.davemloft.net> | |
| Wed, 24 Jan 2007 04:25:41 +0000 (23 20:25 -0800) | ||
| tree | a813e11fc4168e8eb2597364b7d809cd981859ac | treesnapshot (tar.gz zip) |
| parent | d88ae4cc97b24783ee4480697fbdcc02ab4133a6 | commitdiff |
[SELINUX]: increment flow cache genid
Currently, old flow cache entries remain valid even after
a reload of SELinux policy.
This patch increments the flow cache generation id
on policy (re)loads so that flow cache entries are
revalidated as needed.
Thanks to Herbet Xu for pointing this out. See:
http://marc.theaimsgroup.com/?l=linux-netdev&m=116841378704536&w=2
There's also a general issue as well as a solution proposed
by David Miller for when flow_cache_genid wraps. I might be
submitting a separate patch for that later.
I request that this be applied to 2.6.20 since it's
a security relevant fix.
Signed-off-by: Venkat Yekkirala <vyekkirala@TrustedCS.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Currently, old flow cache entries remain valid even after
a reload of SELinux policy.
This patch increments the flow cache generation id
on policy (re)loads so that flow cache entries are
revalidated as needed.
Thanks to Herbet Xu for pointing this out. See:
http://marc.theaimsgroup.com/?l=linux-netdev&m=116841378704536&w=2
There's also a general issue as well as a solution proposed
by David Miller for when flow_cache_genid wraps. I might be
submitting a separate patch for that later.
I request that this be applied to 2.6.20 since it's
a security relevant fix.
Signed-off-by: Venkat Yekkirala <vyekkirala@TrustedCS.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
| security/selinux/ss/services.c | diffblobblamehistory |