1146 |
|
|
1147 |
Fix 2008/02/05 |
Fix 2008/02/05 |
1148 |
|
|
1149 |
@ Use find_task_by_vpid() instead of find_task_pid(). |
@ Use find_task_by_vpid() instead of find_task_by_pid(). |
1150 |
|
|
1151 |
Kernel 2.6.24 introduced PID namespace. |
Kernel 2.6.24 introduced PID namespace. |
1152 |
To search PID given from userland, the kernel needs to use |
To search PID given from userland, the kernel needs to use |
1153 |
find_task_by_vpid() instead of find_task_pid(). |
find_task_by_vpid() instead of find_task_by_pid(). |
1154 |
|
|
1155 |
Fix 2008/02/14 |
Fix 2008/02/14 |
1156 |
|
|
1427 |
echo Shared: 1048576 > /proc/ccs/meminfo |
echo Shared: 1048576 > /proc/ccs/meminfo |
1428 |
echo Private: 1048576 > /proc/ccs/meminfo |
echo Private: 1048576 > /proc/ccs/meminfo |
1429 |
|
|
1430 |
Version 1.6.1 2008/05/?? Bug fix release. |
Version 1.6.1 2008/05/10 Bug fix release. |
1431 |
|
|
1432 |
|
Fix 2008/06/04 |
1433 |
|
|
1434 |
|
@ Check open mode of /proc/ccs/ interface. |
1435 |
|
|
1436 |
|
It turned out that I can avoid allocating memory for reading if |
1437 |
|
FMODE_READ is not set and memory for writing if FMODE_WRITE is not set. |
1438 |
|
|
1439 |
|
@ Wait for completion of /sbin/ccs-init . |
1440 |
|
|
1441 |
|
Since 2.4 kernel's call_usermodehelper() can't wait for termination of |
1442 |
|
the executed program, I was using the close() request of |
1443 |
|
/proc/ccs/meminfo to indicate that loading policy has finished. |
1444 |
|
But since /proc/ccs/meminfo could be accessed for setting memory quota |
1445 |
|
by /etc/ccs/ccs-post-init , I stopped using the close() request. |
1446 |
|
The policy loader no longer need to access /proc/ccs/meminfo to notify |
1447 |
|
the kernel that loading policy has finished. |
1448 |
|
|
1449 |
|
Fix 2008/06/05 |
1450 |
|
|
1451 |
|
@ Fix realpath for pipes and sockets. |
1452 |
|
|
1453 |
|
Kernel 2.6.22 and later use different method for calculating d_path(). |
1454 |
|
Since fs/realpath.c didn't notice the change, the realpath of pipes |
1455 |
|
appeared as "pipe:" rather than "pipe:[\$]" when they are opened via |
1456 |
|
/proc/PID/fd/ directory. |
1457 |
|
|
1458 |
|
@ Add process's information into /proc/ccs/query . |
1459 |
|
|
1460 |
|
While /proc/ccs/grant_log and /proc/ccs/reject_log contain process's |
1461 |
|
information, /proc/ccs/query doesn't contain it. |
1462 |
|
To be able to utilize ccs-queryd and ccs-notifyd more, I added it into |
1463 |
|
/proc/ccs/query . |
1464 |
|
|
1465 |
|
Fix 2008/06/10 |
1466 |
|
|
1467 |
|
@ Allow using patterns for globally readable files. |
1468 |
|
|
1469 |
|
To allow users specify locale specific files to globally readable files, |
1470 |
|
I relaxed checking in update_globally_readable_entry(). |
1471 |
|
|
1472 |
|
@ Move ALLOW_ENFORCE_GRACE=enabled checking to write_answer(). |
1473 |
|
|
1474 |
|
To allow users use ccs-notifyd without turning ALLOW_ENFORCE_GRACE on, |
1475 |
|
I moved it from ccs_check_supervisor() to write_answer(). |
1476 |
|
|
1477 |
|
Fix 2008/06/11 |
1478 |
|
|
1479 |
|
@ Remove ALLOW_ENFORCE_GRACE parameter. |
1480 |
|
|
1481 |
|
Since unexpected requests caused by doing software updates can happen |
1482 |
|
in all profiles, users likely have to write ALLOW_ENFORCE_GRACE=enabled |
1483 |
|
to all profiles. And it makes meaningless to allow users to selectively |
1484 |
|
enable specific profile's ALLOW_ENFORCE_GRACE parameter. |
1485 |
|
So, I removed ALLOW_ENFORCE_GRACE parameter. |
1486 |
|
Now, the system behaves as if ALLOW_ENFORCE_GRACE=enabled is specified. |
1487 |
|
The behavior of "delayed enforcing" mode is defined in the following |
1488 |
|
order. |
1489 |
|
|
1490 |
|
(1) The requests are rejected immediately if nobody is opening |
1491 |
|
/proc/ccs/query interface. |
1492 |
|
(2) The requests will be rejected in 10 seconds if somebody other than |
1493 |
|
ccs-queryd (such as less(1)) is opening /proc/ccs/query interface, |
1494 |
|
for such process doesn't write dummy decisions. |
1495 |
|
|
1496 |
|
Fix 2008/06/22 |
1497 |
|
|
1498 |
|
@ Pass escaped pathname to audit_execute_handler_log(). |
1499 |
|
|
1500 |
|
I was passing unescaped pathname to audit_execute_handler_log() |
1501 |
|
which causes /proc/ccs/grant_log contain whitespace characters |
1502 |
|
if execute handler's pathname contains whitespace characters. |
1503 |
|
|
1504 |
|
Version 1.6.2 2008/??/?? Usability enhancement release. |