| 3030 |
CONFIG::file::getattr are by default configured to use CONFIG::file or |
CONFIG::file::getattr are by default configured to use CONFIG::file or |
| 3031 |
CONFIG settings. |
CONFIG settings. |
| 3032 |
|
|
| 3033 |
Fix 2011/12/08 |
Fix 2011/12/13 |
| 3034 |
|
|
| 3035 |
@ Follow __d_path() behavior change. (Only 2.6.36 and later) |
@ Follow __d_path() behavior change. (Only 2.6.36 and later) |
| 3036 |
|
|
| 3041 |
|
|
| 3042 |
The patch that changed the behavior of __d_path() might be backported to |
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 |
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. |
backported, or 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 |
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 |
handling pathnames under lazy-unmounted directory. Until now, TOMOYO was |
| 3054 |
lazy-unmounted directory should not happen unless the administrator |
lazy-unmounted directory should not happen unless the administrator |
| 3055 |
explicitly does lazy unmounts. But pathnames which is defined for such |
explicitly does lazy unmounts. But pathnames which is defined for such |
| 3056 |
conditions in the policy file (if any) will need to be rewritten. |
conditions in the policy file (if any) will need to be rewritten. |
| 3057 |
|
|
| 3058 |
|
Fix 2012/01/20 |
| 3059 |
|
|
| 3060 |
|
@ Follow changes in 3.3-rc1. |
| 3061 |
|
|
| 3062 |
|
Use umode_t rather than mode_t. |
| 3063 |
|
Remove ipv6_addr_copy() usage. |
| 3064 |
|
|
| 3065 |
|
Fix 2012/02/25 |
| 3066 |
|
|
| 3067 |
|
@ Follow changes in linux-next. |
| 3068 |
|
|
| 3069 |
|
UMH_WAIT_PROC constant (currently 1) is scheduled for renumbering in 3.4. |
| 3070 |
|
|
| 3071 |
|
Use UMH_WAIT_PROC constant instead of hardcoded constant in preparation |
| 3072 |
|
for backporting call_usermodehelper() related changes. If renumbering was |
| 3073 |
|
backported, you will start experiencing the kernel panic upon execution |
| 3074 |
|
of external policy loader (i.e. /sbin/ccs-init), for the kernel will no |
| 3075 |
|
longer wait for completion of external policy loader process. |
| 3076 |
|
|
| 3077 |
|
Although I changed to use UMH_WAIT_PROC constant, this change could fail |
| 3078 |
|
to detect renumbering in 2.6.22 and earlier kernels, for UMH_WAIT_PROC |
| 3079 |
|
constant is currently available to only 2.6.23 and later kernels. If you |
| 3080 |
|
started to experience the kernel panic, please check whether renumbering |
| 3081 |
|
was backported or not. |
| 3082 |
|
|
| 3083 |
|
Fix 2012/02/29 |
| 3084 |
|
|
| 3085 |
|
@ Fix mount flags checking order. |
| 3086 |
|
|
| 3087 |
|
Userspace can pass in arbitrary combinations of MS_* flags to mount(). |
| 3088 |
|
|
| 3089 |
|
If both MS_BIND and one of MS_SHARED/MS_PRIVATE/MS_SLAVE/MS_UNBINDABLE |
| 3090 |
|
are passed, device name which should be checked for MS_BIND was not |
| 3091 |
|
checked because MS_SHARED/MS_PRIVATE/MS_SLAVE/MS_UNBINDABLE had higher |
| 3092 |
|
priority than MS_BIND. |
| 3093 |
|
|
| 3094 |
|
If both one of MS_BIND/MS_MOVE and MS_REMOUNT are passed, device name |
| 3095 |
|
which should not be checked for MS_REMOUNT was checked because MS_BIND/ |
| 3096 |
|
MS_MOVE had higher priority than MS_REMOUNT. |
| 3097 |
|
|
| 3098 |
|
Fix these bugs by changing priority to MS_REMOUNT -> MS_BIND -> |
| 3099 |
|
MS_SHARED/MS_PRIVATE/MS_SLAVE/MS_UNBINDABLE -> MS_MOVE as with do_mount() |
| 3100 |
|
does. Also, I changed to unconditionally return -EINVAL if more than one |
| 3101 |
|
of MS_SHARED/MS_PRIVATE/MS_SLAVE/MS_UNBINDABLE is passed so that TOMOYO |
| 3102 |
|
will not generate inaccurate audit logs, for commit 7a2e8a8f "VFS: Sanity |
| 3103 |
|
check mount flags passed to change_mnt_propagation()" clarified that |
| 3104 |
|
these flags must be exclusively passed. |
| 3105 |
|
|
| 3106 |
|
Fix 2012/03/08 |
| 3107 |
|
|
| 3108 |
|
@ Allow returning other errors when ptrace permission cannot be checked. |
| 3109 |
|
|
| 3110 |
|
Currently -EPERM is returned when ccs_ptrace_permission() returned an |
| 3111 |
|
error code. I changed to return return value from ccs_ptrace_permission() |
| 3112 |
|
so that we can return -ESRCH when target process was not found. |
| 3113 |
|
|
| 3114 |
|
Fix 2012/03/16 |
| 3115 |
|
|
| 3116 |
|
@ Return appropriate value to poll(). |
| 3117 |
|
|
| 3118 |
|
Return POLLIN | POLLRDNORM | POLLOUT | POLLWRNORM if ready to read/write, |
| 3119 |
|
POLLOUT | POLLWRNORM otherwise. |
| 3120 |
|
|
| 3121 |
|
Fix 2012/04/22 |
| 3122 |
|
|
| 3123 |
|
@ Readd RHEL_MINOR/AX_MINOR checks. |
| 3124 |
|
|
| 3125 |
|
This check was added in revision 3741 and was removed in revision 4084. |
| 3126 |
|
|
| 3127 |
|
Add it back in order to support RHEL 5.0, 5.1, 5.2 kernels. |
TOMOYO
Parent Directory
Revision Log
Patch