| 3011 |
"task auto_domain_transition"/"task auto_execute_handler"/ |
"task auto_domain_transition"/"task auto_execute_handler"/ |
| 3012 |
"task denied_execute_handler" because these are not appended by learning |
"task denied_execute_handler" because these are not appended by learning |
| 3013 |
mode. |
mode. |
| 3014 |
|
|
| 3015 |
|
Fix 2011/11/11 |
| 3016 |
|
|
| 3017 |
|
@ Optimize for object's size. |
| 3018 |
|
|
| 3019 |
|
I rearranged functions/variables into three groups in order to reduce |
| 3020 |
|
object's filesize. Also, I added kernel config options for reducing more |
| 3021 |
|
by excluding unnecessary functionality. |
| 3022 |
|
|
| 3023 |
|
Fix 2011/11/18 |
| 3024 |
|
|
| 3025 |
|
@ Fix kernel config mapping error. |
| 3026 |
|
|
| 3027 |
|
Due to a typo in ccs_p2mac definition, mode for CONFIG::file::execute was |
| 3028 |
|
by error used when checking "file getattr" permission. Most users will |
| 3029 |
|
not be affected by this error because CONFIG::file::execute and |
| 3030 |
|
CONFIG::file::getattr are by default configured to use CONFIG::file or |
| 3031 |
|
CONFIG settings. |
| 3032 |
|
|
| 3033 |
|
Fix 2011/12/08 |
| 3034 |
|
|
| 3035 |
|
@ Follow __d_path() behavior change. (Only 2.6.36 and later) |
| 3036 |
|
|
| 3037 |
|
The behavior of __d_path() has changed in 3.2-rc5. __d_path() now returns |
| 3038 |
|
NULL when the pathname cannot be calculated. You must update to this |
| 3039 |
|
version when using with 3.2-rc5 and later kernels, or the kernel will |
| 3040 |
|
panic because ccs_get_absolute_path() triggers NULL pointer dereference. |
| 3041 |
|
|
| 3042 |
|
The patch that changed the behavior of __d_path() might be backported to |
| 3043 |
|
2.6.36 to 3.1 kernels. You must update to this version if the patch was |
| 3044 |
|
backported, for you will experience the kernel panic as with 3.2-rc5. |
| 3045 |
|
|
| 3046 |
|
The patch that changed the behavior of __d_path() also changed the way of |
| 3047 |
|
handling pathnames under lazy-unmounted directory. Until now, TOMOYO was |
| 3048 |
|
using incomplete pathnames returned by __d_path() when the pathname is |
| 3049 |
|
under lazy-unmounted directory. But from now on, TOMOYO uses different |
| 3050 |
|
pathnames returned by ccs_get_local_path() when the pathname is under |
| 3051 |
|
lazy-unmounted directory (because __d_path() no longer returns it). |
| 3052 |
|
|
| 3053 |
|
Since applications unlikely do lazy unmounts, requesting pathnames under |
| 3054 |
|
lazy-unmounted directory should not happen unless the administrator |
| 3055 |
|
explicitly does lazy unmounts. But pathnames which is defined for such |
| 3056 |
|
conditions in the policy file (if any) will need to be rewritten. |
TOMOYO
Parent Directory
Revision Log
Patch