| 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/28 |
| 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 -> MS_SHARED |
| 3099 |
|
-> MS_PRIVATE -> MS_SLAVE -> MS_UNBINDABLE -> MS_MOVE as with do_mount() |
| 3100 |
|
does. |
TOMOYO
Parent Directory
Revision Log
Patch