1. 06 3月, 2019 2 次提交
  2. 08 1月, 2019 1 次提交
  3. 12 12月, 2018 1 次提交
  4. 22 10月, 2018 1 次提交
  5. 06 9月, 2018 1 次提交
  6. 03 8月, 2018 2 次提交
  7. 05 6月, 2018 8 次提交
  8. 02 4月, 2018 6 次提交
  9. 01 3月, 2018 1 次提交
  10. 26 2月, 2018 2 次提交
  11. 28 11月, 2017 1 次提交
    • L
      Rename superblock flags (MS_xyz -> SB_xyz) · 1751e8a6
      Linus Torvalds 提交于
      This is a pure automated search-and-replace of the internal kernel
      superblock flags.
      
      The s_flags are now called SB_*, with the names and the values for the
      moment mirroring the MS_* flags that they're equivalent to.
      
      Note how the MS_xyz flags are the ones passed to the mount system call,
      while the SB_xyz flags are what we then use in sb->s_flags.
      
      The script to do this was:
      
          # places to look in; re security/*: it generally should *not* be
          # touched (that stuff parses mount(2) arguments directly), but
          # there are two places where we really deal with superblock flags.
          FILES="drivers/mtd drivers/staging/lustre fs ipc mm \
                  include/linux/fs.h include/uapi/linux/bfs_fs.h \
                  security/apparmor/apparmorfs.c security/apparmor/include/lib.h"
          # the list of MS_... constants
          SYMS="RDONLY NOSUID NODEV NOEXEC SYNCHRONOUS REMOUNT MANDLOCK \
                DIRSYNC NOATIME NODIRATIME BIND MOVE REC VERBOSE SILENT \
                POSIXACL UNBINDABLE PRIVATE SLAVE SHARED RELATIME KERNMOUNT \
                I_VERSION STRICTATIME LAZYTIME SUBMOUNT NOREMOTELOCK NOSEC BORN \
                ACTIVE NOUSER"
      
          SED_PROG=
          for i in $SYMS; do SED_PROG="$SED_PROG -e s/MS_$i/SB_$i/g"; done
      
          # we want files that contain at least one of MS_...,
          # with fs/namespace.c and fs/pnode.c excluded.
          L=$(for i in $SYMS; do git grep -w -l MS_$i $FILES; done| sort|uniq|grep -v '^fs/namespace.c'|grep -v '^fs/pnode.c')
      
          for f in $L; do sed -i $f $SED_PROG; done
      Requested-by: NAl Viro <viro@zeniv.linux.org.uk>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      1751e8a6
  12. 13 11月, 2017 1 次提交
    • J
      ceph: present consistent fsid, regardless of arch endianness · 080a330e
      Jeff Layton 提交于
      Since its inception, ceph has presented the fsid as an opaque value
      without any sort of endianness conversion. This means that the value
      presented is different on architectures of different endianness.
      
      While the value that should be stuffed into f_fsid is poorly-defined,
      I think it would be best to strive for consistency here between
      architectures, and clients (we need to present this properly to the
      userland client as well).
      
      Change ceph_statfs to convert the opaque words to host-endian before
      doing the xor. On an upgrade, a big-endian box may see a different fsid
      than it did before, but little-endian arches should see no change with
      this patch.
      Signed-off-by: NJeff Layton <jlayton@redhat.com>
      Reviewed-by: NSage Weil <sage@redhat.com>
      Signed-off-by: NIlya Dryomov <idryomov@gmail.com>
      080a330e
  13. 07 9月, 2017 6 次提交
  14. 07 7月, 2017 2 次提交
  15. 04 5月, 2017 1 次提交
  16. 21 4月, 2017 1 次提交
  17. 25 2月, 2017 1 次提交
  18. 20 2月, 2017 1 次提交
  19. 13 12月, 2016 1 次提交