09 May, 2019

1 commit

  • Pull documentation updates from Jonathan Corbet:
    "A reasonably busy cycle for docs, including:

    - Lots of work on the Chinese and Italian translations

    - Some license-rules clarifications from Christoph

    - Various build-script fixes

    - A new document on memory models

    - RST conversion of the live-patching docs

    - The usual collection of typo fixes and corrections"

    * tag 'docs-5.2' of git://git.lwn.net/linux: (140 commits)
    docs/livepatch: Unify style of livepatch documentation in the ReST format
    docs: livepatch: convert docs to ReST and rename to *.rst
    scripts/documentation-file-ref-check: detect broken :doc:`foo`
    scripts/documentation-file-ref-check: don't parse Next/ dir
    LICENSES: Rename other to deprecated
    LICENSES: Clearly mark dual license only licenses
    docs: Don't reference the ZLib license in license-rules.rst
    docs/vm: Minor editorial changes in the THP and hugetlbfs
    docs/vm: add documentation of memory models
    doc:it_IT: translation alignment
    doc: fix typo in PGP guide
    dontdiff: update with Kconfig build artifacts
    docs/zh_CN: fix typos in 1.Intro.rst file
    docs/zh_CN: redirect CoC docs to Chinese version
    doc: mm: migration doesn't use FOLL_SPLIT anymore
    docs: doc-guide: remove the extension from .rst files
    doc: kselftest: Fix KBUILD_OUTPUT usage instructions
    docs: trace: fix some Sphinx warnings
    docs: speculation.txt: mark example blocks as such
    docs: ntb.txt: add blank lines to clean up some Sphinx warnings
    ...

    Linus Torvalds
     

15 Apr, 2019

1 commit

  • In commit b1fca27d384e ("kernel debug: support resetting WARN*_ONCE")
    we got the opportunity to reset state on the one shot messages,
    without having to reboot.

    However printk_once (printk_deferred_once) live in a different file
    and didn't get the same kind of update/conversion, so they remain
    unconditionally one shot, until the system is rebooted.

    For example, we currently have:

    sched/rt.c: printk_deferred_once("sched: RT throttling activated\n");

    ..which could reasonably be tripped as someone is testing and tuning
    a new system/workload and their task placements. For consistency, and
    to avoid reboots in the same vein as the original commit, we make these
    two instances of _once the same as the WARN*_ONCE instances are.

    Link: http://lkml.kernel.org/r/1555121491-31213-1-git-send-email-paul.gortmaker@windriver.com
    Cc: Andi Kleen
    Cc: Petr Mladek
    Cc: Sergey Senozhatsky
    Cc: Steven Rostedt
    Cc: Andrew Morton
    Signed-off-by: Paul Gortmaker
    Reviewed-by: Sergey Senozhatsky
    Signed-off-by: Petr Mladek

    Paul Gortmaker
     

12 Apr, 2019

1 commit


18 Nov, 2017

1 commit

  • I like _ONCE warnings because it's guaranteed that they don't flood the
    log.

    During testing I find it useful to reset the state of the once warnings,
    so that I can rerun tests and see if they trigger again, or can
    guarantee that a test run always hits the same warnings.

    This patch adds a debugfs interface to reset all the _ONCE warnings so
    that they appear again:

    echo 1 > /sys/kernel/debug/clear_warn_once

    This is implemented by putting all the warning booleans into a special
    section, and clearing it.

    [akpm@linux-foundation.org: coding-style fixes]
    Link: http://lkml.kernel.org/r/20171017221455.6740-1-andi@firstfloor.org
    Signed-off-by: Andi Kleen
    Tested-by: Michael Ellerman
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Andi Kleen