25 Jan, 2021

1 commit


18 Jan, 2021

1 commit


07 Jan, 2021

1 commit

  • Free the pages parallely for a task that receives SIGKILL, from ULMK
    process, using the oom_reaper. This freeing of pages will help to give
    the pages to buddy system well advance.

    Add the boot param, reap_mem_when_killed_by=, that configures the
    process name, the kill signal to a process from which makes its memory
    reaped by oom reaper.

    As an example, when reap_mem_when_killed_by=lmkd, then all the processes
    that receives the kill signal from lmkd is added to oom reaper.

    Not initializing this param makes this feature disabled.

    Change-Id: I21adb95de5e380a80d7eb0b87d9b5b553f52e28a
    Bug: 171763461
    Signed-off-by: Charan Teja Reddy
    Signed-off-by: Isaac J. Manjarres

    Charan Teja Reddy
     

04 Jan, 2021

1 commit

  • This is the 5.10.2 stable release

    * tag 'v5.10.2': (17 commits)
    Linux 5.10.2
    serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access
    ALSA: pcm: oss: Fix potential out-of-bounds shift
    ...

    Signed-off-by: Jason Liu

    Conflicts:
    drivers/usb/host/xhci-hub.c
    drivers/usb/host/xhci.h

    Jason Liu
     

21 Dec, 2020

2 commits

  • Changes in 5.10.2
    ptrace: Prevent kernel-infoleak in ptrace_get_syscall_info()
    ktest.pl: If size of log is too big to email, email error message
    ktest.pl: Fix the logic for truncating the size of the log file for email
    USB: legotower: fix logical error in recent commit
    USB: dummy-hcd: Fix uninitialized array use in init()
    USB: add RESET_RESUME quirk for Snapscan 1212
    ALSA: usb-audio: Fix potential out-of-bounds shift
    ALSA: usb-audio: Fix control 'access overflow' errors from chmap
    xhci: Give USB2 ports time to enter U3 in bus suspend
    usb: xhci: Set quirk for XHCI_SG_TRB_CACHE_SIZE_QUIRK
    xhci-pci: Allow host runtime PM as default for Intel Alpine Ridge LP
    xhci-pci: Allow host runtime PM as default for Intel Maple Ridge xHCI
    USB: UAS: introduce a quirk to set no_write_same
    USB: sisusbvga: Make console support depend on BROKEN
    ALSA: pcm: oss: Fix potential out-of-bounds shift
    serial: 8250_omap: Avoid FIFO corruption caused by MDR1 access
    Linux 5.10.2

    Signed-off-by: Greg Kroah-Hartman
    Change-Id: I0dfd41a3ba5b102699ef78641fbe48ed16957a0f

    Greg Kroah-Hartman
     
  • commit 8010622c86ca5bb44bc98492f5968726fc7c7a21 upstream.

    UAS does not share the pessimistic assumption storage is making that
    devices cannot deal with WRITE_SAME. A few devices supported by UAS,
    are reported to not deal well with WRITE_SAME. Those need a quirk.

    Add it to the device that needs it.

    Reported-by: David C. Partridge
    Signed-off-by: Oliver Neukum
    Cc: stable
    Link: https://lore.kernel.org/r/20201209152639.9195-1-oneukum@suse.com
    Signed-off-by: Greg Kroah-Hartman

    Oliver Neukum
     

14 Dec, 2020

2 commits


04 Dec, 2020

1 commit


03 Dec, 2020

2 commits

  • …nel/git/rostedt/linux-trace

    Pull bootconfig fixes from Steven Rostedt:
    "Have bootconfig size and checksum be little endian

    In case the bootconfig is created on one kind of endian machine, and
    then read on the other kind of endian kernel, the size and checksum
    will be incorrect. Instead, have both the size and checksum always be
    little endian and have the tool and the kernel convert it from little
    endian to or from the host endian"

    * tag 'trace-v5.10-rc6-bootconfig' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
    docs: bootconfig: Add the endianness of fields
    tools/bootconfig: Store size and checksum in footer as le32
    bootconfig: Load size and checksum in the footer as le32

    Linus Torvalds
     
  • …nch/cifs-2.6") into android-mainline

    Steps on the way to 5.10-rc7

    Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
    Change-Id: I122855676b56d2501cd65b604ccc8f5936d8fd71

    Greg Kroah-Hartman
     

02 Dec, 2020

1 commit

  • Pull tracing fixes from Steven Rostedt:

    - Use correct timestamp variable for ring buffer write stamp update

    - Fix up before stamp and write stamp when crossing ring buffer sub
    buffers

    - Keep a zero delta in ring buffer in slow path if cmpxchg fails

    - Fix trace_printk static buffer for archs that care

    - Fix ftrace record accounting for ftrace ops with trampolines

    - Fix DYNAMIC_FTRACE_WITH_DIRECT_CALLS dependency

    - Remove WARN_ON in hwlat tracer that triggers on something that is OK

    - Make "my_tramp" trampoline in ftrace direct sample code global

    - Fixes in the bootconfig tool for better alignment management

    * tag 'trace-v5.10-rc6' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace:
    ring-buffer: Always check to put back before stamp when crossing pages
    ftrace: Fix DYNAMIC_FTRACE_WITH_DIRECT_CALLS dependency
    ftrace: Fix updating FTRACE_FL_TRAMP
    tracing: Fix alignment of static buffer
    tracing: Remove WARN_ON in start_thread()
    samples/ftrace: Mark my_tramp[12]? global
    ring-buffer: Set the right timestamp in the slow path of __rb_reserve_next()
    ring-buffer: Update write stamp with the correct ts
    docs: bootconfig: Update file format on initrd image
    tools/bootconfig: Align the bootconfig applied initrd image size to 4
    tools/bootconfig: Fix to check the write failure correctly
    tools/bootconfig: Fix errno reference after printf()

    Linus Torvalds
     

01 Dec, 2020

1 commit

  • Add a description about the endianness of the size and the checksum
    fields. Those must be stored as le32 instead of u32. This will allow
    us to apply bootconfig to the cross build initrd without caring
    the endianness.

    Link: https://lkml.kernel.org/r/160583936246.547349.10964204130590955409.stgit@devnote2

    Reported-by: Steven Rostedt
    Suggested-by: Linus Torvalds
    Signed-off-by: Masami Hiramatsu
    Signed-off-by: Steven Rostedt (VMware)

    Masami Hiramatsu
     

20 Nov, 2020

2 commits

  • …nux/kernel/git/netdev/net") into android-mainline

    Steps on the way to 5.10-rc5

    Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
    Change-Id: I00726ee0d08f08ae6ac5edd07c8fa502b41d4800

    Greg Kroah-Hartman
     
  • Pull powerpc fixes from Michael Ellerman:
    "Fixes for CVE-2020-4788.

    From Daniel's cover letter:

    IBM Power9 processors can speculatively operate on data in the L1
    cache before it has been completely validated, via a way-prediction
    mechanism. It is not possible for an attacker to determine the
    contents of impermissible memory using this method, since these
    systems implement a combination of hardware and software security
    measures to prevent scenarios where protected data could be leaked.

    However these measures don't address the scenario where an attacker
    induces the operating system to speculatively execute instructions
    using data that the attacker controls. This can be used for example to
    speculatively bypass "kernel user access prevention" techniques, as
    discovered by Anthony Steinhauser of Google's Safeside Project. This
    is not an attack by itself, but there is a possibility it could be
    used in conjunction with side-channels or other weaknesses in the
    privileged code to construct an attack.

    This issue can be mitigated by flushing the L1 cache between privilege
    boundaries of concern.

    This patch series flushes the L1 cache on kernel entry (patch 2) and
    after the kernel performs any user accesses (patch 3). It also adds a
    self-test and performs some related cleanups"

    * tag 'powerpc-cve-2020-4788' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux:
    powerpc/64s: rename pnv|pseries_setup_rfi_flush to _setup_security_mitigations
    selftests/powerpc: refactor entry and rfi_flush tests
    selftests/powerpc: entry flush test
    powerpc: Only include kup-radix.h for 64-bit Book3S
    powerpc/64s: flush L1D after user accesses
    powerpc/64s: flush L1D on kernel entry
    selftests/powerpc: rfi_flush: disable entry flush if present

    Linus Torvalds
     

19 Nov, 2020

3 commits

  • To align the total file size, add padding null character when appending
    the bootconfig to initrd image.

    Link: https://lkml.kernel.org/r/160576522916.320071.4145530996151028855.stgit@devnote2

    Signed-off-by: Masami Hiramatsu
    Signed-off-by: Steven Rostedt (VMware)

    Masami Hiramatsu
     
  • IBM Power9 processors can speculatively operate on data in the L1 cache
    before it has been completely validated, via a way-prediction mechanism. It
    is not possible for an attacker to determine the contents of impermissible
    memory using this method, since these systems implement a combination of
    hardware and software security measures to prevent scenarios where
    protected data could be leaked.

    However these measures don't address the scenario where an attacker induces
    the operating system to speculatively execute instructions using data that
    the attacker controls. This can be used for example to speculatively bypass
    "kernel user access prevention" techniques, as discovered by Anthony
    Steinhauser of Google's Safeside Project. This is not an attack by itself,
    but there is a possibility it could be used in conjunction with
    side-channels or other weaknesses in the privileged code to construct an
    attack.

    This issue can be mitigated by flushing the L1 cache between privilege
    boundaries of concern. This patch flushes the L1 cache after user accesses.

    This is part of the fix for CVE-2020-4788.

    Signed-off-by: Nicholas Piggin
    Signed-off-by: Daniel Axtens
    Signed-off-by: Michael Ellerman

    Nicholas Piggin
     
  • IBM Power9 processors can speculatively operate on data in the L1 cache
    before it has been completely validated, via a way-prediction mechanism. It
    is not possible for an attacker to determine the contents of impermissible
    memory using this method, since these systems implement a combination of
    hardware and software security measures to prevent scenarios where
    protected data could be leaked.

    However these measures don't address the scenario where an attacker induces
    the operating system to speculatively execute instructions using data that
    the attacker controls. This can be used for example to speculatively bypass
    "kernel user access prevention" techniques, as discovered by Anthony
    Steinhauser of Google's Safeside Project. This is not an attack by itself,
    but there is a possibility it could be used in conjunction with
    side-channels or other weaknesses in the privileged code to construct an
    attack.

    This issue can be mitigated by flushing the L1 cache between privilege
    boundaries of concern. This patch flushes the L1 cache on kernel entry.

    This is part of the fix for CVE-2020-4788.

    Signed-off-by: Nicholas Piggin
    Signed-off-by: Daniel Axtens
    Signed-off-by: Michael Ellerman

    Nicholas Piggin
     

06 Nov, 2020

3 commits

  • …it.kernel.org/pub/scm/linux/kernel/git/shuah/linux-kselftest") into android-mainline

    Steps on the way to 5.10-rc3

    Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
    Change-Id: I57f80255bf5d396e92a54807a516cc41cf07be61

    Greg Kroah-Hartman
     
  • …rnel.org/pub/scm/linux/kernel/git/acme/linux") into android-mainline

    Steps on the way to 5.10-rc3

    Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>
    Change-Id: Ia09418a96a25f6c602af953db5d3258e032c0f30

    Greg Kroah-Hartman
     
  • Pull power management fixes from Rafael Wysocki:
    "These fix the device links support in runtime PM, correct mistakes in
    the cpuidle documentation, fix the handling of policy limits changes
    in the schedutil cpufreq governor, fix assorted issues in the OPP
    (operating performance points) framework and make one janitorial
    change.

    Specifics:

    - Unify the handling of managed and stateless device links in the
    runtime PM framework and prevent runtime PM references to devices
    from being leaked after device link removal (Rafael Wysocki).

    - Fix two mistakes in the cpuidle documentation (Julia Lawall).

    - Prevent the schedutil cpufreq governor from missing policy limits
    updates in some cases (Viresh Kumar).

    - Prevent static OPPs from being dropped by mistake (Viresh Kumar).

    - Prevent helper function in the OPP framework from returning
    prematurely (Viresh Kumar).

    - Prevent opp_table_lock from being held too long during removal of
    OPP tables with no more active references (Viresh Kumar).

    - Drop redundant semicolon from the Intel RAPL power capping driver
    (Tom Rix)"

    * tag 'pm-5.10-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm:
    PM: runtime: Resume the device earlier in __device_release_driver()
    PM: runtime: Drop pm_runtime_clean_up_links()
    PM: runtime: Drop runtime PM references to supplier on link removal
    powercap/intel_rapl: remove unneeded semicolon
    Documentation: PM: cpuidle: correct path name
    Documentation: PM: cpuidle: correct typo
    cpufreq: schedutil: Don't skip freq update if need_freq_update is set
    opp: Reduce the size of critical section in _opp_table_kref_release()
    opp: Fix early exit from dev_pm_opp_register_set_opp_helper()
    opp: Don't always remove static OPPs in _of_add_opp_table_v1()

    Linus Torvalds
     

04 Nov, 2020

1 commit

  • Pull documentation build warning fixes from Jonathan Corbet:
    "This contains a series of warning fixes from Mauro; once applied, the
    number of warnings from the once-noisy docs build process is nearly
    zero.

    Getting to this point has required a lot of work; once there,
    hopefully we can keep things that way.

    I have packaged this as a separate pull because it does a fair amount
    of reaching outside of Documentation/. The changes are all in comments
    and in code placement. It's all been in linux-next since last week"

    * tag 'docs-5.10-warnings' of git://git.lwn.net/linux: (24 commits)
    docs: SafeSetID: fix a warning
    amdgpu: fix a few kernel-doc markup issues
    selftests: kselftest_harness.h: fix kernel-doc markups
    drm: amdgpu_dm: fix a typo
    gpu: docs: amdgpu.rst: get rid of wrong kernel-doc markups
    drm: amdgpu: kernel-doc: update some adev parameters
    docs: fs: api-summary.rst: get rid of kernel-doc include
    IB/srpt: docs: add a description for cq_size member
    locking/refcount: move kernel-doc markups to the proper place
    docs: lockdep-design: fix some warning issues
    MAINTAINERS: fix broken doc refs due to yaml conversion
    ice: docs fix a devlink info that broke a table
    crypto: sun8x-ce*: update entries to its documentation
    net: phy: remove kernel-doc duplication
    mm: pagemap.h: fix two kernel-doc markups
    blk-mq: docs: add kernel-doc description for a new struct member
    docs: userspace-api: add iommu.rst to the index file
    docs: hwmon: mp2975.rst: address some html build warnings
    docs: net: statistics.rst: remove a duplicated kernel-doc
    docs: kasan.rst: add two missing blank lines
    ...

    Linus Torvalds
     

03 Nov, 2020

2 commits


02 Nov, 2020

1 commit


30 Oct, 2020

5 commits

  • Now that ABI/testing documents were fixed, add --rst-sources to
    the ABI/testing too.

    Acked-by: Jonathan Corbet
    Signed-off-by: Mauro Carvalho Chehab
    Link: https://lore.kernel.org/r/9242473fd3df785565bb6084b1b814cc15074fb2.1604042072.git.mchehab+huawei@kernel.org
    Signed-off-by: Greg Kroah-Hartman

    Mauro Carvalho Chehab
     
  • With just a single fix, the contents there can be parsed properly
    without the need to escape any ReST incompatible stuff.

    Acked-by: Jonathan Corbet
    Signed-off-by: Mauro Carvalho Chehab
    Link: https://lore.kernel.org/r/472f4574b6aa2ff4de5a819db1a4a5c9a34f5168.1604042072.git.mchehab+huawei@kernel.org
    Signed-off-by: Greg Kroah-Hartman

    Mauro Carvalho Chehab
     
  • That helps to identify what ABI files are adding titles.

    Acked-by: Jonathan Corbet
    Signed-off-by: Mauro Carvalho Chehab
    Link: https://lore.kernel.org/r/e267b36ae7f32bab2a86f1da6b40bb3e62c877d4.1604042072.git.mchehab+huawei@kernel.org
    Signed-off-by: Greg Kroah-Hartman

    Mauro Carvalho Chehab
     
  • Now that the stable ABI files are compatible with ReST,
    parse them without converting complex descriptions as literal
    blocks nor escaping special characters.

    Please notice that escaping special characters will probably
    be needed at descriptions, at least for the asterisk character.

    Acked-by: Jonathan Corbet
    Signed-off-by: Mauro Carvalho Chehab
    Link: https://lore.kernel.org/r/59ccbaa75ff05f23e701dd9a0bbe118e9343a553.1604042072.git.mchehab+huawei@kernel.org
    Signed-off-by: Greg Kroah-Hartman

    Mauro Carvalho Chehab
     
  • As we don't want a generic Sphinx extension to execute commands,
    change the one proposed to Markus to call the abi_book.pl
    script.

    Use a script to parse the Documentation/ABI directory and output
    it at the admin-guide.

    Acked-by: Jonathan Corbet
    Signed-off-by: Mauro Carvalho Chehab
    Link: https://lore.kernel.org/r/5651482b06500e69a1acdf92152f90a203e6521d.1604042072.git.mchehab+huawei@kernel.org
    Signed-off-by: Greg Kroah-Hartman

    Mauro Carvalho Chehab
     

29 Oct, 2020

3 commits


27 Oct, 2020

1 commit


26 Oct, 2020

6 commits