Searched hist:"77 b071b3" (Results 1 – 4 of 4) sorted by relevance
| /openbmc/linux/security/apparmor/include/ |
| H A D | policy.h | 77b071b3 Wed Jul 10 23:07:43 CDT 2013 John Johansen <john.johansen@canonical.com> apparmor: change how profile replacement update is done
remove the use of replaced by chaining and move to profile invalidation
and lookup to handle task replacement.
Replacement chaining can result in large chains of profiles being pinned
in memory when one profile in the chain is use. With implicit labeling
this will be even more of a problem, so move to a direct lookup method.
Signed-off-by: John Johansen <john.johansen@canonical.com>
77b071b3 Wed Jul 10 23:07:43 CDT 2013 John Johansen <john.johansen@canonical.com> apparmor: change how profile replacement update is done
remove the use of replaced by chaining and move to profile invalidation
and lookup to handle task replacement.
Replacement chaining can result in large chains of profiles being pinned
in memory when one profile in the chain is use. With implicit labeling
this will be even more of a problem, so move to a direct lookup method.
Signed-off-by: John Johansen <john.johansen@canonical.com>
|
| /openbmc/linux/security/apparmor/ |
| H A D | policy.c | 77b071b3 Wed Jul 10 23:07:43 CDT 2013 John Johansen <john.johansen@canonical.com> apparmor: change how profile replacement update is done
remove the use of replaced by chaining and move to profile invalidation
and lookup to handle task replacement.
Replacement chaining can result in large chains of profiles being pinned
in memory when one profile in the chain is use. With implicit labeling
this will be even more of a problem, so move to a direct lookup method.
Signed-off-by: John Johansen <john.johansen@canonical.com>
|
| H A D | domain.c | 77b071b3 Wed Jul 10 23:07:43 CDT 2013 John Johansen <john.johansen@canonical.com> apparmor: change how profile replacement update is done
remove the use of replaced by chaining and move to profile invalidation
and lookup to handle task replacement.
Replacement chaining can result in large chains of profiles being pinned
in memory when one profile in the chain is use. With implicit labeling
this will be even more of a problem, so move to a direct lookup method.
Signed-off-by: John Johansen <john.johansen@canonical.com>
77b071b3 Wed Jul 10 23:07:43 CDT 2013 John Johansen <john.johansen@canonical.com> apparmor: change how profile replacement update is done
remove the use of replaced by chaining and move to profile invalidation
and lookup to handle task replacement.
Replacement chaining can result in large chains of profiles being pinned
in memory when one profile in the chain is use. With implicit labeling
this will be even more of a problem, so move to a direct lookup method.
Signed-off-by: John Johansen <john.johansen@canonical.com>
|
| H A D | lsm.c | 77b071b3 Wed Jul 10 23:07:43 CDT 2013 John Johansen <john.johansen@canonical.com> apparmor: change how profile replacement update is done
remove the use of replaced by chaining and move to profile invalidation
and lookup to handle task replacement.
Replacement chaining can result in large chains of profiles being pinned
in memory when one profile in the chain is use. With implicit labeling
this will be even more of a problem, so move to a direct lookup method.
Signed-off-by: John Johansen <john.johansen@canonical.com>
|