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

Subversion リポジトリの参照

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

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

revision 4334 by kumaneko, Tue Jan 11 07:45:54 2011 UTC revision 4794 by kumaneko, Fri Apr 1 04:34:12 2011 UTC
# Line 2659  Fix 2010/10/28 Line 2659  Fix 2010/10/28
2659    
2660        This change allows you to jump to arbitrary domain.        This change allows you to jump to arbitrary domain.
2661    
2662          Note that this change also reverts "Change /proc/ccs/info/self_domain ."
2663          made on 2006/10/24. Now, 'cat < /proc/ccs/info/self_domain' will act like
2664          'cat /proc/ccs/info/self_domain'. Programs depending on old assumption
2665          need to be updated.
2666    
2667      @ Add "task auto_domain_transition".      @ Add "task auto_domain_transition".
2668    
2669        This is similar to "task manual_domain_transition", but is automatically        This is similar to "task manual_domain_transition", but is automatically
# Line 2714  Fix 2010/12/17 Line 2719  Fix 2010/12/17
2719        experience temporary inconsistency, but such threads are about to be        experience temporary inconsistency, but such threads are about to be
2720        killed by SIGKILL signal.        killed by SIGKILL signal.
2721    
2722  Fix 2010/01/11  Fix 2011/01/11
2723    
2724        @ Use filesystem name for unnamed devices when vfsmount is missing.
2725    
2726          "Change pathname for non-rename()able filesystems." changed to use
2727          "$fsname:" if the filesystem does not support rename() operation and
2728          "dev($major,$minor):" otherwise when vfsmount is missing. But it turned
2729          out that it is useless to use "dev($major,$minor):" for unnamed devices
2730          (filesystems with $major == 0). Thus, I changed to use "$fsname:" rather
2731          than "dev($major,$minor):" for filesystems with $major == 0 when vfsmount
2732          is missing.
2733    
2734    Fix 2011/02/07
2735    
2736        @ Fix infinite loop bug when reading /proc/ccs/audit or /proc/ccs/query .
2737    
2738          In ccs_flush(), head->r.w[0] holds pointer to string data to be printed.
2739          But head->r.w[0] was updated only when the string data was partially
2740          printed (because head->r.w[0] will be updated by head->r.w[1] later if
2741          completely printed). However, regarding /proc/ccs/audit and
2742          /proc/ccs/query , an additional '\0' is printed after the string data was
2743          completely printed. But if free space for read buffer became 0 before
2744          printing the additional '\0', ccs_flush() was returning without updating
2745          head->r.w[0]. As a result, ccs_flush() forever reprints already printed
2746          string data.
2747    
2748    Fix 2011/03/01
2749    
2750        @ Run garbage collector without waiting for /proc/ccs/ users.
2751    
2752          Currently TOMOYO holds SRCU lock upon open() and releases it upon close()
2753          because list elements stored in the "struct ccs_io_buffer" instances are
2754          accessed until close() is called. However, such SRCU usage causes lockdep
2755          to complain about leaving the kernel with SRCU lock held. Therefore,
2756          I changed to hold/release SRCU upon each read()/write() by selectively
2757          deferring kfree() by keeping track of the "struct ccs_io_buffer"
2758          instances.
2759    
2760    Fix 2011/03/05
2761    
2762        @ Support built-in policy configuration.
2763    
2764          To be able to start using enforcing mode from the early stage of boot
2765          sequence, I added support for built-in policy configuration and
2766          activating access control without calling external policy loader program.
2767    
2768          This will be useful for systems where operations which can lead to the
2769          hijacking of the boot sequence are needed before loading the policy.
2770          For example, you can activate immediately after loading the fixed part of
2771          policy which will allow only operations needed for mounting a partition
2772          which contains the variant part of policy and verifying (e.g. running GPG
2773          check) and loading the variant part of policy. Since you can start using
2774          enforcing mode from the beginning, you can reduce the possibility of
2775          hijacking the boot sequence.
2776    
2777    Fix 2011/03/10
2778    
2779        @ Remove /proc/ccs/meminfo interface.
2780    
2781          Please use /proc/ccs/stat interface instead.
2782    
2783    Fix 2011/03/15
2784    
2785        @ Pack policy when printing via /proc/ccs/ interface.
2786    
2787          The kernel side is ready for accepting packed input like
2788    
2789            file read/write/execute /path/to/file
2790    
2791          but was using unpacked output like
2792    
2793            file read /path/to/file
2794            file write /path/to/file
2795            file execute /path/to/file
2796    
2797          because most of userland tools were not ready for accepting packed input.
2798    
2799          The advantages of using packed policy are that it makes policy files
2800          smaller and it speeds up loading/saving policy files.
2801    
2802          Since most of userland tools are ready for accepting packed input by now,
2803          I changed to use packed policy for both input and output.
2804    
2805    Fix 2011/03/31
2806    
2807        @ Fix conditional policy parsing.
2808    
2809          Since exec.realpath= and symlink.target= accept path_group,
2810          symlink.target="@foo" was by error parsed as symlink.target=@foo .
2811    
2812        @ Serialize updating profile's comment line.
2813    
2814     @ Use filesystem name for unnamed devices when vfsmount is missing.        We need to serialize when updating COMMENT= line in /proc/ccs/profile .
2815    
2816       "Change pathname for non-rename()able filesystems." changed to use  Version 1.8.1   2011/04/01   Usability enhancement with "Zettai, Daijoubudayo" release!
      "$fsname:" if the filesystem does not support rename() operation and  
      "dev($major,$minor):" otherwise when vfsmount is missing. But it turned  
      out that it is useless to use "dev($major,$minor):" for unnamed devices  
      (filesystems with $major == 0). Thus, I changed to use "$fsname:" rather  
      than "dev($major,$minor):" for filesystems with $major == 0 when vfsmount  
      is missing.  

Legend:
Removed from v.4334  
changed lines
  Added in v.4794

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