1. 11 Mar, 2013 1 commit
  2. 23 Feb, 2013 1 commit
  3. 03 Oct, 2012 1 commit
  4. 21 Sep, 2012 1 commit
  5. 14 Jul, 2012 1 commit
    • Al Viro's avatar
      stop passing nameidata to ->lookup() · 00cd8dd3
      Al Viro authored
      Just the flags; only NFS cares even about that, but there are
      legitimate uses for such argument.  And getting rid of that
      completely would require splitting ->lookup() into a couple
      of methods (at least), so let's leave that alone for now...
      Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
      00cd8dd3
  6. 21 Mar, 2012 1 commit
  7. 20 Mar, 2012 1 commit
  8. 10 Mar, 2012 7 commits
  9. 04 Jan, 2012 1 commit
    • Al Viro's avatar
      vfs: fix the stupidity with i_dentry in inode destructors · 6b520e05
      Al Viro authored
      Seeing that just about every destructor got that INIT_LIST_HEAD() copied into
      it, there is no point whatsoever keeping this INIT_LIST_HEAD in inode_init_once();
      the cost of taking it into inode_init_always() will be negligible for pipes
      and sockets and negative for everything else.  Not to mention the removal of
      boilerplate code from ->destroy_inode() instances...
      Signed-off-by: default avatarAl Viro <viro@zeniv.linux.org.uk>
      6b520e05
  10. 03 Jan, 2012 1 commit
    • Phillip Lougher's avatar
      Squashfs: fix i_blocks calculation with extended regular files · 3d4a1c80
      Phillip Lougher authored
      The le64_to_cpu() forces the calculation to be unsigned, with
      the effect that it can underflow leading to an incorrect large
      value.
      
      This bug only triggers in rare(ish) circumstances, an empty file
      encoded as an extended regular file or a completely sparse file.
      Normally empty files are encoded as a regular file rather than as
      an extended regular file (and the regular file i_blocks calculation
      doesn't have this bug).  To save space regular file inodes are
      optimised to encode the most commonly occurring files.  Less
      common regular files are encoded using extended regular file inodes
      which contain extra information.
      
      Empty files with nlinks greater than 1, and or empty files
      with extended attributes are encoded using extended regular file
      inodes and they will hit this bug.
      Signed-off-by: default avatarPhillip Lougher <phillip@squashfs.org.uk>
      3d4a1c80
  11. 02 Jan, 2012 1 commit
  12. 30 Dec, 2011 2 commits
  13. 02 Nov, 2011 2 commits
  14. 27 Sep, 2011 1 commit
    • Paul Bolle's avatar
      doc: fix broken references · 395cf969
      Paul Bolle authored
      There are numerous broken references to Documentation files (in other
      Documentation files, in comments, etc.). These broken references are
      caused by typo's in the references, and by renames or removals of the
      Documentation files. Some broken references are simply odd.
      
      Fix these broken references, sometimes by dropping the irrelevant text
      they were part of.
      Signed-off-by: default avatarPaul Bolle <pebolle@tiscali.nl>
      Signed-off-by: default avatarJiri Kosina <jkosina@suse.cz>
      395cf969
  15. 22 Jul, 2011 1 commit
  16. 20 Jul, 2011 2 commits
  17. 29 May, 2011 1 commit
  18. 26 May, 2011 1 commit
  19. 25 May, 2011 7 commits
  20. 10 May, 2011 1 commit
  21. 31 Mar, 2011 1 commit
  22. 22 Mar, 2011 1 commit
  23. 16 Mar, 2011 1 commit
    • Phillip Lougher's avatar
      Squashfs: handle corruption of directory structure · 44cff8a9
      Phillip Lougher authored
      Handle the rare case where a directory metadata block is uncompressed and
      corrupted, leading to a kernel oops in directory scanning (memcpy).
      Normally corruption is detected at the decompression stage and dealt with
      then, however, this will not happen if:
      
      - metadata isn't compressed (users can optionally request no metadata
        compression), or
      - the compressed metadata block was larger than the original, in which
        case the uncompressed version was used, or
      - the data was corrupt after decompression
      
      This patch fixes this by adding some sanity checks against known maximum
      values.
      Signed-off-by: default avatarPhillip Lougher <phillip@lougher.demon.co.uk>
      44cff8a9
  24. 28 Feb, 2011 2 commits