1. 21 4月, 2008 1 次提交
  2. 18 4月, 2008 2 次提交
  3. 30 1月, 2008 1 次提交
  4. 08 11月, 2007 1 次提交
  5. 17 10月, 2007 2 次提交
  6. 12 7月, 2007 1 次提交
    • E
      selinux: introduce schedule points in policydb_destroy() · 9dc99780
      Eric Paris 提交于
      During the LSPP testing we found that it was possible for
      policydb_destroy() to take 10+ seconds of kernel time to complete.
      Basically all policydb_destroy() does is walk some (possibly long) lists
      and free the memory it finds.  Turning off slab debugging config options
      made the problem go away since the actual functions which took most of
      the time were (as seen by oprofile)
      
      > 121202   23.9879  .check_poison_obj
      > 78247    15.4864  .check_slabp
      
      were caused by that.  So I decided to also add some voluntary schedule
      points in that code so config voluntary preempt would be enough to solve
      the problem.  Something similar was done in places like
      shmem_free_pages() when we have to walk a list of memory and free it.
      This was tested by the LSPP group on the hardware which could reproduce
      the problem just loading a new policy and was found to not trigger the
      softlock detector.  It takes just as much processing time, but the
      kernel doesn't spend all that time stuck doing one thing and never
      scheduling.
      
      Someday a better way to handle memory might make the time needed in this
      function a lot less, but this fixes the current issue as it stands
      today.
      Signed-off-by: NEric Paris <eparis@redhat.com>
      Signed-off-by: NJames Morris <jmorris@namei.org>
      9dc99780
  7. 27 2月, 2007 1 次提交
    • E
      Reassign printk levels in selinux kernel code · fadcdb45
      Eric Paris 提交于
      Below is a patch which demotes many printk lines to KERN_DEBUG from
      KERN_INFO.  It should help stop the spamming of logs with messages in
      which users are not interested nor is there any action that users should
      take.  It also promotes some KERN_INFO to KERN_ERR such as when there
      are improper attempts to register/unregister security modules.
      
      A similar patch was discussed a while back on list:
      http://marc.theaimsgroup.com/?t=116656343500003&r=1&w=2
      This patch addresses almost all of the issues raised.  I believe the
      only advice not taken was in the demoting of messages related to
      undefined permissions and classes.
      Signed-off-by: NEric Paris <eparis@redhat.com>
      Acked-by: NStephen Smalley <sds@tycho.nsa.gov>
      
       security/selinux/hooks.c       |   20 ++++++++++----------
       security/selinux/ss/avtab.c    |    2 +-
       security/selinux/ss/policydb.c |    6 +++---
       security/selinux/ss/sidtab.c   |    2 +-
       4 files changed, 15 insertions(+), 15 deletions(-)
      Signed-off-by: NJames Morris <jmorris@namei.org>
      fadcdb45
  8. 03 12月, 2006 1 次提交
  9. 12 10月, 2006 1 次提交
    • C
      SELinux: Bug fix in polidydb_destroy · 6e8c751e
      Chad Sellers 提交于
      This patch fixes two bugs in policydb_destroy. Two list pointers
      (policydb.ocontexts[i] and policydb.genfs) were not being reset to NULL when
      the lists they pointed to were being freed. This caused a problem when the
      initial policy load failed, as the policydb being destroyed was not a
      temporary new policydb that was thrown away, but rather was the global
      (active) policydb. Consequently, later functions, particularly
      sys_bind->selinux_socket_bind->security_node_sid and
      do_rw_proc->selinux_sysctl->selinux_proc_get_sid->security_genfs_sid tried
      to dereference memory that had previously been freed.
      Signed-off-by: NChad Sellers <csellers@tresys.com>
      Signed-off-by: NJames Morris <jmorris@namei.org>
      6e8c751e
  10. 26 9月, 2006 1 次提交
  11. 01 8月, 2006 1 次提交
  12. 07 1月, 2006 1 次提交
  13. 07 11月, 2005 1 次提交
  14. 31 10月, 2005 1 次提交
  15. 24 10月, 2005 1 次提交
  16. 05 9月, 2005 2 次提交
  17. 26 6月, 2005 1 次提交
  18. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4