オープンソース・ソフトウェアの開発とダウンロード

Subversion リポジトリの参照

Diff of /trunk/1.8.x/ccs-patch/README.ccs

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 2003 by kumaneko, Wed Dec 24 07:07:28 2008 UTC revision 2201 by kumaneko, Thu Feb 26 06:06:13 2009 UTC
# Line 1753  Fix 2008/12/01 Line 1753  Fix 2008/12/01
1753        new conditions for checking file's type and permissions.        new conditions for checking file's type and permissions.
1754        For example,        For example,
1755    
1756          allow_read /etc/fstab if path1.type=regular path1.perm=0644          allow_read /etc/fstab if path1.type=file path1.perm=0644
1757    
1758        will allow opening /etc/fstab for reading only if /etc/fstab is a regular        will allow opening /etc/fstab for reading only if /etc/fstab is a regular
1759        file and it's permission is 0644, and        file and it's permission is 0644, and
# Line 1796  Fix 2008/12/24 Line 1796  Fix 2008/12/24
1796    
1797        I meant to print SYAORAN-ERROR: message when error == -EPERM,        I meant to print SYAORAN-ERROR: message when error == -EPERM,
1798        but I was printing it when error == 0 since 1.6.0 .        but I was printing it when error == 0 since 1.6.0 .
1799    
1800    Fix 2009/01/05
1801    
1802        @ Use kmap_atomic()/kunmap_atomic() for reading "struct linux_binprm".
1803    
1804          As remove_arg_zero() uses kmap_atomic(KM_USER0), I modified to use
1805          kmap_atomic(KM_USER0) rather than kmap().
1806    
1807        @ Relocate definitions and functions.
1808    
1809          To reduce exposed symbols, I relocated some definitions and functions.
1810    
1811    Fix 2009/01/28
1812    
1813        @ Fix "allow_read" + "allow_write" != "allow_read/write" problem.
1814    
1815          Since 1.6.0 , due to a bug in ccs_update_single_path_acl(),
1816          appending "allow_read/write" entry didn't update internal "allow_read"
1817          and "allow_write" entries. As a result, attempt to open(O_RDWR) succeeds
1818          but open(O_RDONLY) and open(O_WRONLY) fail.
1819    
1820          Workaround is to write an entry twice when newly appending that entry.
1821          If written twice, internal "allow_read" and "allow_write" entries
1822          are updated.
1823    
1824    Fix 2009/02/26
1825    
1826        @ Fix profile read error.
1827    
1828          Incorrect profiles were shown in /proc/ccs/profile
1829          if either CONFIG_SAKURA or CONFIG_TOMOYO is disabled.

Legend:
Removed from v.2003  
changed lines
  Added in v.2201

Back to OSDN">Back to OSDN
ViewVC Help
Powered by ViewVC 1.1.26