1. 04 10月, 2014 1 次提交
    • M
      ftracetest: Add POSIX.3 standard and XFAIL result codes · 915de2ad
      Masami Hiramatsu 提交于
      Add XFAIL and POSIX 1003.3 standard codes (UNRESOLVED/
      UNTESTED/UNSUPPORTED) as result codes. These are used for the
      results that test case is expected to fail or unsupported
      feature (by config).
      
      To return these result code, this introduces exit_unresolved,
      exit_untested, exit_unsupported and exit_xfail functions,
      which use real-time signals to notify the result code to
      ftracetest.
      
      This also set "errexit" option for the testcases, so that
      the tests don't need to exit explicitly.
      
      Note that if the test returns UNRESOLVED/UNSUPPORTED/FAIL,
      its test log including executed commands is shown on console
      and main logfile as below.
      
        ------
        # ./ftracetest samples/
        === Ftrace unit tests ===
        [1] failure-case example        [FAIL]
        execute: /home/fedora/ksrc/linux-3/tools/testing/selftests/ftrace/samples/fail.tc
        + . /home/fedora/ksrc/linux-3/tools/testing/selftests/ftrace/samples/fail.tc
        ++ cat non-exist-file
        cat: non-exist-file: No such file or directory
        [2] pass-case example   [PASS]
        [3] unresolved-case example     [UNRESOLVED]
        execute: /home/fedora/ksrc/linux-3/tools/testing/selftests/ftrace/samples/unresolved.tc
        + . /home/fedora/ksrc/linux-3/tools/testing/selftests/ftrace/samples/unresolved.tc
        ++ trap exit_unresolved INT
        ++ kill -INT 29324
        +++ exit_unresolved
        +++ kill -s 38 29265
        +++ exit 0
        [4] unsupported-case example    [UNSUPPORTED]
        execute: /home/fedora/ksrc/linux-3/tools/testing/selftests/ftrace/samples/unsupported.tc
        + . /home/fedora/ksrc/linux-3/tools/testing/selftests/ftrace/samples/unsupported.tc
        ++ exit_unsupported
        ++ kill -s 40 29265
        ++ exit 0
        [5] untested-case example       [UNTESTED]
        [6] xfail-case example  [XFAIL]
      
        # of passed:  1
        # of failed:  1
        # of unresolved:  1
        # of untested:  1
        # of unsupported:  1
        # of xfailed:  1
        # of undefined(test bug):  0
        ------
      
      Link: http://lkml.kernel.org/p/20140929120211.30203.99510.stgit@kbuild-f20.novalocalAcked-by: NNamhyung Kim <namhyung@kernel.org>
      Signed-off-by: NMasami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
      Signed-off-by: NSteven Rostedt <rostedt@goodmis.org>
      915de2ad
  2. 23 9月, 2014 3 次提交
  3. 30 8月, 2014 1 次提交
  4. 09 8月, 2014 3 次提交
  5. 01 8月, 2014 1 次提交
    • E
      mnt: Add tests for unprivileged remount cases that have found to be faulty · db181ce0
      Eric W. Biederman 提交于
      Kenton Varda <kenton@sandstorm.io> discovered that by remounting a
      read-only bind mount read-only in a user namespace the
      MNT_LOCK_READONLY bit would be cleared, allowing an unprivileged user
      to the remount a read-only mount read-write.
      
      Upon review of the code in remount it was discovered that the code allowed
      nosuid, noexec, and nodev to be cleared.  It was also discovered that
      the code was allowing the per mount atime flags to be changed.
      
      The first naive patch to fix these issues contained the flaw that using
      default atime settings when remounting a filesystem could be disallowed.
      
      To avoid this problems in the future add tests to ensure unprivileged
      remounts are succeeding and failing at the appropriate times.
      
      Cc: stable@vger.kernel.org
      Acked-by: NSerge E. Hallyn <serge.hallyn@ubuntu.com>
      Signed-off-by: N"Eric W. Biederman" <ebiederm@xmission.com>
      db181ce0
  6. 28 7月, 2014 10 次提交
  7. 18 7月, 2014 1 次提交
  8. 12 7月, 2014 7 次提交
  9. 10 7月, 2014 1 次提交
  10. 04 7月, 2014 3 次提交
  11. 27 6月, 2014 2 次提交
  12. 24 6月, 2014 1 次提交
  13. 11 6月, 2014 5 次提交
  14. 07 6月, 2014 1 次提交
    • K
      tools/testing/selftests/sysctl: validate sysctl_writes_strict · 24fe831c
      Kees Cook 提交于
      This adds several behavioral tests to sysctl string and number writing
      to detect unexpected cases that behaved differently when the sysctl
      kernel.sysctl_writes_strict != 1.
      
      [ original ]
          root@localhost:~# make test_num
          == Testing sysctl behavior against /proc/sys/kernel/domainname ==
          Writing test file ... ok
          Checking sysctl is not set to test value ... ok
          Writing sysctl from shell ... ok
          Resetting sysctl to original value ... ok
          Writing entire sysctl in single write ... ok
          Writing middle of sysctl after synchronized seek ... FAIL
          Writing beyond end of sysctl ... FAIL
          Writing sysctl with multiple long writes ... FAIL
          Writing entire sysctl in short writes ... FAIL
          Writing middle of sysctl after unsynchronized seek ... ok
          Checking sysctl maxlen is at least 65 ... ok
          Checking sysctl keeps original string on overflow append ... FAIL
          Checking sysctl stays NULL terminated on write ... ok
          Checking sysctl stays NULL terminated on overwrite ... ok
          make: *** [test_num] Error 1
          root@localhost:~# make test_string
          == Testing sysctl behavior against /proc/sys/vm/swappiness ==
          Writing test file ... ok
          Checking sysctl is not set to test value ... ok
          Writing sysctl from shell ... ok
          Resetting sysctl to original value ... ok
          Writing entire sysctl in single write ... ok
          Writing middle of sysctl after synchronized seek ... FAIL
          Writing beyond end of sysctl ... FAIL
          Writing sysctl with multiple long writes ... ok
          make: *** [test_string] Error 1
      
      [ with CONFIG_PROC_SYSCTL_STRICT_WRITES ]
          root@localhost:~# make run_tests
          == Testing sysctl behavior against /proc/sys/kernel/domainname ==
          Writing test file ... ok
          Checking sysctl is not set to test value ... ok
          Writing sysctl from shell ... ok
          Resetting sysctl to original value ... ok
          Writing entire sysctl in single write ... ok
          Writing middle of sysctl after synchronized seek ... ok
          Writing beyond end of sysctl ... ok
          Writing sysctl with multiple long writes ... ok
          Writing entire sysctl in short writes ... ok
          Writing middle of sysctl after unsynchronized seek ... ok
          Checking sysctl maxlen is at least 65 ... ok
          Checking sysctl keeps original string on overflow append ... ok
          Checking sysctl stays NULL terminated on write ... ok
          Checking sysctl stays NULL terminated on overwrite ... ok
          == Testing sysctl behavior against /proc/sys/vm/swappiness ==
          Writing test file ... ok
          Checking sysctl is not set to test value ... ok
          Writing sysctl from shell ... ok
          Resetting sysctl to original value ... ok
          Writing entire sysctl in single write ... ok
          Writing middle of sysctl after synchronized seek ... ok
          Writing beyond end of sysctl ... ok
          Writing sysctl with multiple long writes ... ok
      Signed-off-by: NKees Cook <keescook@chromium.org>
      Cc: Randy Dunlap <rdunlap@infradead.org>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      24fe831c