1. 10 10月, 2014 1 次提交
    • K
      selftests/vm/transhuge-stress: stress test for memory compaction · 0085d61f
      Konstantin Khlebnikov 提交于
      This tool induces memory fragmentation via sequential allocation of
      transparent huge pages and splitting off everything except their last
      sub-pages.  It easily generates pressure to the memory compaction code.
      
      $ perf stat -e 'compaction:*' -e 'migrate:*' ./transhuge-stress
      transhuge-stress: allocate 7858 transhuge pages, using 15716 MiB virtual memory and 61 MiB of ram
      transhuge-stress: 1.653 s/loop, 0.210 ms/page,   9504.828 MiB/s	7858 succeed,    0 failed, 2439 different pages
      transhuge-stress: 1.537 s/loop, 0.196 ms/page,  10226.227 MiB/s	7858 succeed,    0 failed, 2364 different pages
      transhuge-stress: 1.658 s/loop, 0.211 ms/page,   9479.215 MiB/s	7858 succeed,    0 failed, 2179 different pages
      transhuge-stress: 1.617 s/loop, 0.206 ms/page,   9716.992 MiB/s	7858 succeed,    0 failed, 2421 different pages
      ^C./transhuge-stress: Interrupt
      
       Performance counter stats for './transhuge-stress':
      
               1.744.051      compaction:mm_compaction_isolate_migratepages
                   1.014      compaction:mm_compaction_isolate_freepages
               1.744.051      compaction:mm_compaction_migratepages
                   1.647      compaction:mm_compaction_begin
                   1.647      compaction:mm_compaction_end
               1.744.051      migrate:mm_migrate_pages
                       0      migrate:mm_numa_migrate_ratelimit
      
             7,964696835 seconds time elapsed
      Signed-off-by: NKonstantin Khlebnikov <koct9i@gmail.com>
      Cc: Rafael Aquini <aquini@redhat.com>
      Cc: Andrey Ryabinin <ryabinin.a.a@gmail.com>
      Cc: Shuah Khan <shuahkh@osg.samsung.com>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      0085d61f
  2. 08 10月, 2014 1 次提交
  3. 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
  4. 30 9月, 2014 2 次提交
  5. 23 9月, 2014 3 次提交
  6. 17 9月, 2014 5 次提交
  7. 11 9月, 2014 1 次提交
  8. 08 9月, 2014 9 次提交
  9. 05 9月, 2014 2 次提交
  10. 30 8月, 2014 1 次提交
  11. 09 8月, 2014 3 次提交
  12. 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
  13. 28 7月, 2014 10 次提交