19 Apr, 2017

1 commit


28 Sep, 2016

1 commit

  • CURRENT_TIME macro is not appropriate for filesystems as it
    doesn't use the right granularity for filesystem timestamps.
    Use current_time() instead.

    CURRENT_TIME is also not y2038 safe.

    This is also in preparation for the patch that transitions
    vfs timestamps to use 64 bit time and hence make them
    y2038 safe. As part of the effort current_time() will be
    extended to do range checks. Hence, it is necessary for all
    file system timestamps to use current_time(). Also,
    current_time() will be transitioned along with vfs to be
    y2038 safe.

    Note that whenever a single call to current_time() is used
    to change timestamps in different inodes, it is because they
    share the same time granularity.

    Signed-off-by: Deepa Dinamani
    Reviewed-by: Arnd Bergmann
    Acked-by: Felipe Balbi
    Acked-by: Steven Whitehouse
    Acked-by: Ryusuke Konishi
    Acked-by: David Sterba
    Signed-off-by: Al Viro

    Deepa Dinamani
     

30 Mar, 2016

1 commit


24 Jul, 2015

1 commit


15 Apr, 2014

1 commit


17 Sep, 2013

1 commit


02 Nov, 2011

1 commit


22 May, 2010

1 commit


05 Mar, 2010

3 commits

  • Get rid of the initialize dquot operation - it is now always called from
    the filesystem and if a filesystem really needs it's own (which none
    currently does) it can just call into it's own routine directly.

    Rename the now static low-level dquot_initialize helper to __dquot_initialize
    and vfs_dq_init to dquot_initialize to have a consistent namespace.

    Signed-off-by: Christoph Hellwig
    Signed-off-by: Jan Kara

    Christoph Hellwig
     
  • Get rid of the drop dquot operation - it is now always called from
    the filesystem and if a filesystem really needs it's own (which none
    currently does) it can just call into it's own routine directly.

    Rename the now static low-level dquot_drop helper to __dquot_drop
    and vfs_dq_drop to dquot_drop to have a consistent namespace.

    Signed-off-by: Christoph Hellwig
    Signed-off-by: Jan Kara

    Christoph Hellwig
     
  • Get rid of the alloc_inode and free_inode dquot operations - they are
    always called from the filesystem and if a filesystem really needs
    their own (which none currently does) it can just call into it's
    own routine directly.

    Also get rid of the vfs_dq_alloc/vfs_dq_free wrappers and always
    call the lowlevel dquot_alloc_inode / dqout_free_inode routines
    directly, which now lose the number argument which is always 1.

    Signed-off-by: Christoph Hellwig
    Signed-off-by: Jan Kara

    Christoph Hellwig
     

26 Mar, 2009

1 commit


01 Jan, 2009

1 commit


14 Nov, 2008

1 commit

  • Wrap access to task credentials so that they can be separated more easily from
    the task_struct during the introduction of COW creds.

    Change most current->(|e|s|fs)[ug]id to current_(|e|s|fs)[ug]id().

    Change some task->e?[ug]id to task_e?[ug]id(). In some places it makes more
    sense to use RCU directly rather than a convenient wrapper; these will be
    addressed by later patches.

    Signed-off-by: David Howells
    Reviewed-by: James Morris
    Acked-by: Serge Hallyn
    Acked-by: Dave Kleikamp
    Cc: jfs-discussion@lists.sourceforge.net
    Signed-off-by: James Morris

    David Howells
     

25 Apr, 2007

1 commit

  • This mirrors Jan Kara's patches for ext3. This patch makes sure that
    changes made to inode->i_flags are reflected on disk for jfs. It also
    moves a call of jfs_set_inode_flags() to be more consistent with where
    jfs_get_inode_flags() is called.

    Signed-off-by: Dave Kleikamp

    Dave Kleikamp
     

02 Oct, 2006

2 commits

  • Removed trailing spaces & tabs, and spaces preceding tabs.
    Also a couple very minor comment cleanups.

    Signed-off-by: Dave Kleikamp
    (cherry picked from f74156539964d7b3d5164fdf8848e6a682f75b97 commit)

    Dave Kleikamp
     
  • I have seen confusing behavior on JFS when I injected many intentional
    slab allocation errors. The cp command failed with no disk space error
    with enough disk space.

    This patch makes:

    - change the return value in case slab allocation failures happen
    from -ENOSPC to -ENOMEM

    - ialloc() return error code so that the caller can know the reason
    of failures

    Signed-off-by: Akinobu Mita
    Signed-off-by: Dave Kleikamp
    (cherry picked from 2b46f77976f798f3fe800809a1d0ed38763c71c8 commit)

    Akinobu Mita
     

27 Sep, 2006

1 commit

  • This eliminates the i_blksize field from struct inode. Filesystems that want
    to provide a per-inode st_blksize can do so by providing their own getattr
    routine instead of using the generic_fillattr() function.

    Note that some filesystems were providing pretty much random (and incorrect)
    values for i_blksize.

    [bunk@stusta.de: cleanup]
    [akpm@osdl.org: generic_fillattr() fix]
    Signed-off-by: "Theodore Ts'o"
    Signed-off-by: Adrian Bunk
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Theodore Ts'o
     

10 Mar, 2006

1 commit

  • OS/2 doesn't initialize the uid, gid, or unix-style permission bits. The
    uid, gid, & umask mount options perform pretty much like those for the fat
    file system, overriding what is stored on disk. This is useful for users
    sharing the file system with OS/2.

    I implemented a little feature so that if you mask the execute bit, it
    will be re-enabled on directories when the appropriate read bit is unmasked.
    I didn't want to implement an fmask & dmask option.

    Signed-off-by: Dave Kleikamp

    Dave Kleikamp
     

10 Feb, 2006

1 commit


09 Feb, 2006

1 commit

  • ext2 inode attributes with relevance for jfs:

    'a' EXT2_APPEND_FL -> append only
    'i' EXT2_IMMUTABLE_FL -> immutable file
    's' EXT2_SECRM_FL -> zero file
    'u' EXT2_UNRM_FL -> allow for unrm
    'A' EXT2_NOATIME_FL -> no access time
    'D' EXT2_DIRSYNC_FL -> dirsync
    'S' EXT2_SYNC_FL -> sync

    overview of jfs flags (partially for OS/2)

    value (OS/2) Linux ext2 attrs
    ------------------------------------------------
    0x00010000 IFJOURNAL -
    0x00020000 ISPARSE used
    0x00040000 INLINEEA used
    0x00080000 - - JFS_NOATIME_FL

    0x00100000 - - JFS_DIRSYNC_FL
    0x00200000 - - JFS_SYNC_FL
    0x00400000 - - JFS_SECRM_FL
    0x00800000 ISWAPFILE - JFS_UNRM_FL

    0x01000000 - - JFS_APPEND_FL
    0x02000000 IREADONLY - JFS_IMMUTABLE_FL
    0x04000000 IHIDDEN - -
    0x08000000 ISYSTEM - -

    0x10000000 - -
    0x20000000 IDIRECTORY used
    0x40000000 IARCHIVE -
    0x80000000 INEWNAME -

    the implementation is straight forward, except
    for the fact that the attributes have to be mapped
    to match with the ext2 ones to avoid a separate
    tool for manipulating them (this could be avoided
    when using a separate flag field in the on-disk
    representation, but the overhead is minimal)

    a special jfs_ioctl is added to allow for the new
    JFS_IOC_GETFLAGS and JFS_IOC_SETFLAGS calls.

    a helper function jfs_set_inode_flags() to transfer
    the flags from the on-disk version to the inode

    minor changes to allow flag inheritance on inode
    creation, as well as a cleanup of the on-disk
    flags (including the new ones)

    beforementioned helper to map between ext2 and jfs
    versions of the new flags ...

    the JFS_SECRM_FL and JFS_UNRM_FL are not done yet
    and I'm not 100% sure they are worth the effort,
    the rest seems to work out of the box ...

    Signed-off-by: Herbert Poetzl
    Signed-off-by: Dave Kleikamp

    Herbert Poetzl
     

05 May, 2005

1 commit


17 Apr, 2005

1 commit

  • 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!

    Linus Torvalds