1. 14 Feb, 2007 8 commits
  2. 13 Feb, 2007 2 commits
    • Linus Torvalds's avatar
      Fix up CIFS for "test_clear_page_dirty()" removal · b3d68567
      Linus Torvalds authored
      This also adds he required page "writeback" flag handling, that cifs
      hasn't been doing and that the page dirty flag changes made obvious.
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      Acked-by: default avatarSteve French <smfltc@us.ibm.com>
      b3d68567
    • Hugh Dickins's avatar
      fix umask when noACL kernel meets extN tuned for ACLs · 0e894923
      Hugh Dickins authored
      Fix insecure default behaviour reported by Tigran Aivazian: if an
      ext2 or ext3 filesystem is tuned to mount with "acl", but mounted by
      a kernel built without ACL support, then umask was ignored when creating
      inodes - though root or user has umask 022, touch creates files as 0666,
      and mkdir creates directories as 0777.
      
      This appears to have worked right until 2.6.11, when a fix to the default
      mode on symlinks (always 0777) assumed VFS applies umask: which it does,
      unless the mount is marked for ACLs; but ext[23] set MS_POSIXACL in
      s_flags according to s_mount_opt set according to def_mount_opts.
      
      We could revert to the 2.6.10 ext[23]_init_acl (adding an S_ISLNK test);
      but other filesystems only set MS_POSIXACL when ACLs are configured.  We
      could fix this at another level; but it seems most robust to avoid setting
      the s_mount_opt flag in the first place (at the expense of more ifdefs).
      
      Likewise don't set the XATTR_USER flag when built without XATTR support.
      Signed-off-by: default avatarHugh Dickins <hugh@veritas.com>
      Signed-off-by: default avatarAdrian Bunk <bunk@stusta.de>
      0e894923
  3. 10 Feb, 2007 1 commit
  4. 03 Feb, 2007 8 commits
  5. 30 Jan, 2007 5 commits
  6. 26 Jan, 2007 7 commits
  7. 25 Jan, 2007 4 commits
  8. 24 Jan, 2007 4 commits
  9. 23 Jan, 2007 1 commit
    • Adrian Bunk's avatar
      [Bluetooth] Let BT_HIDP depend on INPUT · 99c7cf71
      Adrian Bunk authored
      This patch lets BT_HIDP depend on instead of select INPUT. This fixes
      the following warning during an s390 build:
      
      net/bluetooth/hidp/Kconfig:4:warning: 'select' used by config symbol
      'BT_HIDP' refer to undefined symbol 'INPUT'
      
      A dependency on INPUT also implies !S390 (and therefore makes the
      explicit dependency obsolete) since INPUT is not available on s390.
      
      The practical difference should be nearly zero, since INPUT is always
      set to y unless EMBEDDED=y (or S390=y).
      Signed-off-by: default avatarAdrian Bunk <bunk@stusta.de>
      99c7cf71