1. 27 Jun, 2006 1 commit
  2. 26 Jun, 2006 4 commits
  3. 25 Jun, 2006 1 commit
  4. 20 Jun, 2006 1 commit
    • Amy Griffis's avatar
      [PATCH] audit: path-based rules · f368c07d
      Amy Griffis authored
      In this implementation, audit registers inotify watches on the parent
      directories of paths specified in audit rules.  When audit's inotify
      event handler is called, it updates any affected rules based on the
      filesystem event.  If the parent directory is renamed, removed, or its
      filesystem is unmounted, audit removes all rules referencing that
      inotify watch.
      
      To keep things simple, this implementation limits location-based
      auditing to the directory entries in an existing directory.  Given
      a path-based rule for /foo/bar/passwd, the following table applies:
      
          passwd modified -- audit event logged
          passwd replaced -- audit event logged, rules list updated
          bar renamed     -- rule removed
          foo renamed     -- untracked, meaning that the rule now applies to
      		       the new location
      
      Audit users typically want to have many rules referencing filesystem
      objects, which can significantly impact filtering performance.  This
      patch also adds an inode-number-based rule hash to mitigate this
      situation.
      
      The patch is relative to the audit git tree:
      http://kernel.org/git/?p=linux/kernel/git/viro/audit-current.git;a=summary
      and uses the inotify kernel API:
      http://lkml.org/lkml/2006/6/1/145
      
      Signed-off-by: default avatarAmy Griffis <amy.griffis@hp.com>
      Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
      f368c07d
  5. 08 Jun, 2006 1 commit
  6. 30 May, 2006 1 commit
  7. 15 May, 2006 2 commits
  8. 08 May, 2006 1 commit
  9. 01 May, 2006 1 commit
  10. 18 Apr, 2006 1 commit
  11. 11 Apr, 2006 1 commit
  12. 28 Mar, 2006 1 commit
  13. 26 Mar, 2006 3 commits
  14. 25 Mar, 2006 4 commits
  15. 24 Mar, 2006 1 commit
    • Theodore Ts'o's avatar
      [PATCH] vfs: MS_VERBOSE should be MS_SILENT · 9b04c997
      Theodore Ts'o authored
      
      
      The meaning of MS_VERBOSE is backwards; if the bit is set, it really means,
      "don't be verbose".  This is confusing and counter-intuitive.
      
      In addition, there is also no way to set the MS_VERBOSE flag in the
      mount(8) program in util-linux, but interesting, it does define options
      which would do the right thing if MS_SILENT were defined, which
      unfortunately we do not:
      
      #ifdef MS_SILENT
        { "quiet",    0, 0, MS_SILENT    },   /* be quiet  */
        { "loud",     0, 1, MS_SILENT    },   /* print out messages. */
      #endif
      
      So the obvious fix is to deprecate the use of MS_VERBOSE and replace it
      with MS_SILENT.
      Signed-off-by: default avatar"Theodore Ts'o" <tytso@mit.edu>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      9b04c997
  16. 23 Mar, 2006 5 commits
  17. 12 Mar, 2006 1 commit
    • Adrian Bunk's avatar
      Kconfig: remove the CONFIG_CC_ALIGN_* options · 8cab77a2
      Adrian Bunk authored
      
      
      I don't see any use case for the CONFIG_CC_ALIGN_* options:
      - they are only available if EMBEDDED
      - people using EMBEDDED will most likely also enable
        CC_OPTIMIZE_FOR_SIZE
      - the default for -Os is to disable alignment
      
      In case someone is doing performance comparisons and discovers that the
      default settings gcc chooses aren't good, the only sane thing is to discuss
      whether it makes sense to change this, not through offering options to change
      this locally.
      Signed-off-by: default avatarAdrian Bunk <bunk@stusta.de>
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarSam Ravnborg <sam@ravnborg.org>
      8cab77a2
  18. 10 Feb, 2006 2 commits
  19. 07 Feb, 2006 1 commit
  20. 03 Feb, 2006 1 commit
  21. 17 Jan, 2006 1 commit
  22. 14 Jan, 2006 2 commits
  23. 11 Jan, 2006 1 commit
  24. 10 Jan, 2006 2 commits