13 Jan, 2018

1 commit


11 Jan, 2018

1 commit

  • Daniel Borkmann says:

    ====================
    pull-request: bpf 2018-01-09

    The following pull-request contains BPF updates for your *net* tree.

    The main changes are:

    1) Prevent out-of-bounds speculation in BPF maps by masking the
    index after bounds checks in order to fix spectre v1, and
    add an option BPF_JIT_ALWAYS_ON into Kconfig that allows for
    removing the BPF interpreter from the kernel in favor of
    JIT-only mode to make spectre v2 harder, from Alexei.

    2) Remove false sharing of map refcount with max_entries which
    was used in spectre v1, from Daniel.

    3) Add a missing NULL psock check in sockmap in order to fix
    a race, from John.

    4) Fix test_align BPF selftest case since a recent change in
    verifier rejects the bit-wise arithmetic on pointers
    earlier but test_align update was missing, from Alexei.
    ====================

    Signed-off-by: David S. Miller

    David S. Miller
     

10 Jan, 2018

1 commit

  • The BPF interpreter has been used as part of the spectre 2 attack CVE-2017-5715.

    A quote from goolge project zero blog:
    "At this point, it would normally be necessary to locate gadgets in
    the host kernel code that can be used to actually leak data by reading
    from an attacker-controlled location, shifting and masking the result
    appropriately and then using the result of that as offset to an
    attacker-controlled address for a load. But piecing gadgets together
    and figuring out which ones work in a speculation context seems annoying.
    So instead, we decided to use the eBPF interpreter, which is built into
    the host kernel - while there is no legitimate way to invoke it from inside
    a VM, the presence of the code in the host kernel's text section is sufficient
    to make it usable for the attack, just like with ordinary ROP gadgets."

    To make attacker job harder introduce BPF_JIT_ALWAYS_ON config
    option that removes interpreter from the kernel in favor of JIT-only mode.
    So far eBPF JIT is supported by:
    x64, arm64, arm32, sparc64, s390, powerpc64, mips64

    The start of JITed program is randomized and code page is marked as read-only.
    In addition "constant blinding" can be turned on with net.core.bpf_jit_harden

    v2->v3:
    - move __bpf_prog_ret0 under ifdef (Daniel)

    v1->v2:
    - fix init order, test_bpf and cBPF (Daniel's feedback)
    - fix offloaded bpf (Jakub's feedback)
    - add 'return 0' dummy in case something can invoke prog->bpf_func
    - retarget bpf tree. For bpf-next the patch would need one extra hunk.
    It will be sent when the trees are merged back to net-next

    Considered doing:
    int bpf_jit_enable __read_mostly = BPF_EBPF_JIT_DEFAULT;
    but it seems better to land the patch as-is and in bpf-next remove
    bpf_jit_enable global variable from all JITs, consolidate in one place
    and remove this jit_init() function.

    Signed-off-by: Alexei Starovoitov
    Signed-off-by: Daniel Borkmann

    Alexei Starovoitov
     

09 Jan, 2018

1 commit

  • On uniprocessor systems, critical and non-critical tasks cannot be
    isolated, as there is only a single CPU core. Hence enabling CPU
    isolation by default on such systems does not make much sense.

    Instead of changing the default for !SMP, fix this by making the feature
    depend on SMP, with an override for compile-testing. Note that its sole
    selector (NO_HZ_FULL) already depends on SMP.

    This decreases kernel size for a default uniprocessor kernel by ca. 1 KiB.

    Signed-off-by: Geert Uytterhoeven
    Acked-by: Nicolas Pitre
    Cc: Frederic Weisbecker
    Cc: Linus Torvalds
    Cc: Peter Zijlstra
    Cc: Thomas Gleixner
    Fixes: 2c43838c99d9d23f ("sched/isolation: Enable CONFIG_CPU_ISOLATION=y by default")
    Link: http://lkml.kernel.org/r/1514891590-20782-1-git-send-email-geert@linux-m68k.org
    Signed-off-by: Ingo Molnar

    Geert Uytterhoeven
     

01 Jan, 2018

1 commit

  • Pull scheduler fixes from Thomas Gleixner:
    "Three patches addressing the fallout of the CPU_ISOLATION changes
    especially with NO_HZ_FULL plus documentation of boot parameter
    dependency"

    * 'sched-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip:
    sched/isolation: Document boot parameters dependency on CONFIG_CPU_ISOLATION=y
    sched/isolation: Enable CONFIG_CPU_ISOLATION=y by default
    sched/isolation: Make CONFIG_NO_HZ_FULL select CONFIG_CPU_ISOLATION

    Linus Torvalds
     

30 Dec, 2017

1 commit

  • Pull x86 page table isolation updates from Thomas Gleixner:
    "This is the final set of enabling page table isolation on x86:

    - Infrastructure patches for handling the extra page tables.

    - Patches which map the various bits and pieces which are required to
    get in and out of user space into the user space visible page
    tables.

    - The required changes to have CR3 switching in the entry/exit code.

    - Optimizations for the CR3 switching along with documentation how
    the ASID/PCID mechanism works.

    - Updates to dump pagetables to cover the user space page tables for
    W+X scans and extra debugfs files to analyze both the kernel and
    the user space visible page tables

    The whole functionality is compile time controlled via a config switch
    and can be turned on/off on the command line as well"

    * 'x86-pti-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (32 commits)
    x86/ldt: Make the LDT mapping RO
    x86/mm/dump_pagetables: Allow dumping current pagetables
    x86/mm/dump_pagetables: Check user space page table for WX pages
    x86/mm/dump_pagetables: Add page table directory to the debugfs VFS hierarchy
    x86/mm/pti: Add Kconfig
    x86/dumpstack: Indicate in Oops whether PTI is configured and enabled
    x86/mm: Clarify the whole ASID/kernel PCID/user PCID naming
    x86/mm: Use INVPCID for __native_flush_tlb_single()
    x86/mm: Optimize RESTORE_CR3
    x86/mm: Use/Fix PCID to optimize user/kernel switches
    x86/mm: Abstract switching CR3
    x86/mm: Allow flushing for future ASID switches
    x86/pti: Map the vsyscall page if needed
    x86/pti: Put the LDT in its own PGD if PTI is on
    x86/mm/64: Make a full PGD-entry size hole in the memory map
    x86/events/intel/ds: Map debug buffers in cpu_entry_area
    x86/cpu_entry_area: Add debugstore entries to cpu_entry_area
    x86/mm/pti: Map ESPFIX into user space
    x86/mm/pti: Share entry text PMD
    x86/entry: Align entry text section to PMD boundary
    ...

    Linus Torvalds
     

24 Dec, 2017

2 commits

  • Add the initial files for kernel page table isolation, with a minimal init
    function and the boot time detection for this misfeature.

    Signed-off-by: Thomas Gleixner
    Reviewed-by: Borislav Petkov
    Cc: Andy Lutomirski
    Cc: Boris Ostrovsky
    Cc: Borislav Petkov
    Cc: Brian Gerst
    Cc: Dave Hansen
    Cc: David Laight
    Cc: Denys Vlasenko
    Cc: Eduardo Valentin
    Cc: Greg KH
    Cc: H. Peter Anvin
    Cc: Josh Poimboeuf
    Cc: Juergen Gross
    Cc: Linus Torvalds
    Cc: Peter Zijlstra
    Cc: Will Deacon
    Cc: aliguori@amazon.com
    Cc: daniel.gruss@iaik.tugraz.at
    Cc: hughd@google.com
    Cc: keescook@google.com
    Signed-off-by: Ingo Molnar

    Thomas Gleixner
     
  • Pull x86 PTI preparatory patches from Thomas Gleixner:
    "Todays Advent calendar window contains twentyfour easy to digest
    patches. The original plan was to have twenty three matching the date,
    but a late fixup made that moot.

    - Move the cpu_entry_area mapping out of the fixmap into a separate
    address space. That's necessary because the fixmap becomes too big
    with NRCPUS=8192 and this caused already subtle and hard to
    diagnose failures.

    The top most patch is fresh from today and cures a brain slip of
    that tall grumpy german greybeard, who ignored the intricacies of
    32bit wraparounds.

    - Limit the number of CPUs on 32bit to 64. That's insane big already,
    but at least it's small enough to prevent address space issues with
    the cpu_entry_area map, which have been observed and debugged with
    the fixmap code

    - A few TLB flush fixes in various places plus documentation which of
    the TLB functions should be used for what.

    - Rename the SYSENTER stack to CPU_ENTRY_AREA stack as it is used for
    more than sysenter now and keeping the name makes backtraces
    confusing.

    - Prevent LDT inheritance on exec() by moving it to arch_dup_mmap(),
    which is only invoked on fork().

    - Make vysycall more robust.

    - A few fixes and cleanups of the debug_pagetables code. Check
    PAGE_PRESENT instead of checking the PTE for 0 and a cleanup of the
    C89 initialization of the address hint array which already was out
    of sync with the index enums.

    - Move the ESPFIX init to a different place to prepare for PTI.

    - Several code moves with no functional change to make PTI
    integration simpler and header files less convoluted.

    - Documentation fixes and clarifications"

    * 'x86-pti-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (24 commits)
    x86/cpu_entry_area: Prevent wraparound in setup_cpu_entry_area_ptes() on 32bit
    init: Invoke init_espfix_bsp() from mm_init()
    x86/cpu_entry_area: Move it out of the fixmap
    x86/cpu_entry_area: Move it to a separate unit
    x86/mm: Create asm/invpcid.h
    x86/mm: Put MMU to hardware ASID translation in one place
    x86/mm: Remove hard-coded ASID limit checks
    x86/mm: Move the CR3 construction functions to tlbflush.h
    x86/mm: Add comments to clarify which TLB-flush functions are supposed to flush what
    x86/mm: Remove superfluous barriers
    x86/mm: Use __flush_tlb_one() for kernel memory
    x86/microcode: Dont abuse the TLB-flush interface
    x86/uv: Use the right TLB-flush API
    x86/entry: Rename SYSENTER_stack to CPU_ENTRY_AREA_entry_stack
    x86/doc: Remove obvious weirdnesses from the x86 MM layout documentation
    x86/mm/64: Improve the memory map documentation
    x86/ldt: Prevent LDT inheritance on exec
    x86/ldt: Rework locking
    arch, mm: Allow arch_dup_mmap() to fail
    x86/vsyscall/64: Warn and fail vsyscall emulation in NATIVE mode
    ...

    Linus Torvalds
     

23 Dec, 2017

1 commit

  • init_espfix_bsp() needs to be invoked before the page table isolation
    initialization. Move it into mm_init() which is the place where pti_init()
    will be added.

    While at it get rid of the #ifdeffery and provide proper stub functions.

    Signed-off-by: Thomas Gleixner
    Cc: Andy Lutomirski
    Cc: Borislav Petkov
    Cc: Dave Hansen
    Cc: H. Peter Anvin
    Cc: Josh Poimboeuf
    Cc: Juergen Gross
    Cc: Linus Torvalds
    Cc: Peter Zijlstra
    Signed-off-by: Ingo Molnar

    Thomas Gleixner
     

18 Dec, 2017

1 commit

  • The "isolcpus=" boot parameter support was always built-in before we
    moved the related code under CONFIG_CPU_ISOLATION. Having it disabled by
    default is very confusing for people accustomed to use this parameter.

    So enable it by dafault to keep the previous behaviour but keep it
    optable for those who want to tinify their kernels.

    Signed-off-by: Frederic Weisbecker
    Cc: Chris Metcalf
    Cc: Christoph Lameter
    Cc: John Stultz
    Cc: Linus Torvalds
    Cc: Luiz Capitulino
    Cc: Mike Galbraith
    Cc: Paul E. McKenney
    Cc: Peter Zijlstra
    Cc: Rik van Riel
    Cc: Thomas Gleixner
    Cc: Wanpeng Li
    Cc: kernel test robot
    Link: http://lkml.kernel.org/r/1513275507-29200-3-git-send-email-frederic@kernel.org
    Signed-off-by: Ingo Molnar

    Frederic Weisbecker
     

28 Nov, 2017

1 commit


18 Nov, 2017

5 commits

  • Clean up the EXPERT menu (yet again).

    Move FHANDLE and CHECKPOINT_RESTORE into the primary EXPERT menu since
    they already depend on EXPERT.

    Move BPF_SYSCALL and USERFAULTFD out of the EXPERT Kconfig symbols menu
    list since they do not depend on EXPERT and were breaking the continuity
    of that menu list.

    Move all of the KALLSYMS Kconfig symbols to the end of the EXPERT menu.
    This separates the kernel services from the build options.

    This patch depends on [PATCH] pci: move PCI_QUIRKS to the PCI bus menu
    (https://lkml.org/lkml/2017/11/2/907).

    Link: http://lkml.kernel.org/r/72e4465a-a5ff-cb3c-1a90-11aa4861b161@infradead.org
    Signed-off-by: Randy Dunlap
    Acked-by: Daniel Borkmann [BPF]
    Cc: Andrea Arcangeli
    Cc: Alexei Starovoitov
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Randy Dunlap
     
  • The cpio format uses a 32-bit number to encode file timestamps, which
    breaks initramfs support in 2038. This reinterprets the timestamp as
    unsigned, to give us another 68 years and avoids breaking until 2106.

    Link: http://lkml.kernel.org/r/20171019095536.801199-1-arnd@arndb.de
    Signed-off-by: Arnd Bergmann
    Cc: Al Viro
    Cc: Deepa Dinamani
    Cc: Arnd Bergmann
    Cc: Daniel Thompson
    Cc: Lokesh Vutla
    Cc: Stafford Horne
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Arnd Bergmann
     
  • pidhash is no longer required as all the information can be looked up
    from idr tree. nr_hashed represented the number of pids that had been
    hashed. Since, nr_hashed and PIDNS_HASH_ADDING are no longer relevant,
    it has been renamed to pid_allocated and PIDNS_ADDING respectively.

    [gs051095@gmail.com: v6]
    Link: http://lkml.kernel.org/r/1507760379-21662-3-git-send-email-gs051095@gmail.com
    Link: http://lkml.kernel.org/r/1507583624-22146-3-git-send-email-gs051095@gmail.com
    Signed-off-by: Gargi Sharma
    Reviewed-by: Rik van Riel
    Tested-by: Tony Luck [ia64]
    Cc: Julia Lawall
    Cc: Ingo Molnar
    Cc: Pavel Tatashin
    Cc: Kirill Tkhai
    Cc: Oleg Nesterov
    Cc: Eric W. Biederman
    Cc: Christoph Hellwig
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Gargi Sharma
     
  • Patch series "Replacing PID bitmap implementation with IDR API", v4.

    This series replaces kernel bitmap implementation of PID allocation with
    IDR API. These patches are written to simplify the kernel by replacing
    custom code with calls to generic code.

    The following are the stats for pid and pid_namespace object files
    before and after the replacement. There is a noteworthy change between
    the IDR and bitmap implementation.

    Before
    text data bss dec hex filename
    8447 3894 64 12405 3075 kernel/pid.o
    After
    text data bss dec hex filename
    3397 304 0 3701 e75 kernel/pid.o

    Before
    text data bss dec hex filename
    5692 1842 192 7726 1e2e kernel/pid_namespace.o
    After
    text data bss dec hex filename
    2854 216 16 3086 c0e kernel/pid_namespace.o

    The following are the stats for ps, pstree and calling readdir on /proc
    for 10,000 processes.

    ps:
    With IDR API With bitmap
    real 0m1.479s 0m2.319s
    user 0m0.070s 0m0.060s
    sys 0m0.289s 0m0.516s

    pstree:
    With IDR API With bitmap
    real 0m1.024s 0m1.794s
    user 0m0.348s 0m0.612s
    sys 0m0.184s 0m0.264s

    proc:
    With IDR API With bitmap
    real 0m0.059s 0m0.074s
    user 0m0.000s 0m0.004s
    sys 0m0.016s 0m0.016s

    This patch (of 2):

    Replace the current bitmap implementation for Process ID allocation.
    Functions that are no longer required, for example, free_pidmap(),
    alloc_pidmap(), etc. are removed. The rest of the functions are
    modified to use the IDR API. The change was made to make the PID
    allocation less complex by replacing custom code with calls to generic
    API.

    [gs051095@gmail.com: v6]
    Link: http://lkml.kernel.org/r/1507760379-21662-2-git-send-email-gs051095@gmail.com
    [avagin@openvz.org: restore the old behaviour of the ns_last_pid sysctl]
    Link: http://lkml.kernel.org/r/20171106183144.16368-1-avagin@openvz.org
    Link: http://lkml.kernel.org/r/1507583624-22146-2-git-send-email-gs051095@gmail.com
    Signed-off-by: Gargi Sharma
    Reviewed-by: Rik van Riel
    Acked-by: Oleg Nesterov
    Cc: Julia Lawall
    Cc: Ingo Molnar
    Cc: Pavel Tatashin
    Cc: Kirill Tkhai
    Cc: Eric W. Biederman
    Cc: Christoph Hellwig
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Gargi Sharma
     
  • init/version.c has nothing to do with modules, so remove the
    .

    Instead, include for EXPORT_SYMBOL_GPL.

    This cuts off a lot of unnecessary header parsing.

    Link: http://lkml.kernel.org/r/1505920984-8523-1-git-send-email-yamada.masahiro@socionext.com
    Signed-off-by: Masahiro Yamada
    Cc: Paul Gortmaker
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Masahiro Yamada
     

16 Nov, 2017

6 commits

  • Merge updates from Andrew Morton:

    - a few misc bits

    - ocfs2 updates

    - almost all of MM

    * emailed patches from Andrew Morton : (131 commits)
    memory hotplug: fix comments when adding section
    mm: make alloc_node_mem_map a void call if we don't have CONFIG_FLAT_NODE_MEM_MAP
    mm: simplify nodemask printing
    mm,oom_reaper: remove pointless kthread_run() error check
    mm/page_ext.c: check if page_ext is not prepared
    writeback: remove unused function parameter
    mm: do not rely on preempt_count in print_vma_addr
    mm, sparse: do not swamp log with huge vmemmap allocation failures
    mm/hmm: remove redundant variable align_end
    mm/list_lru.c: mark expected switch fall-through
    mm/shmem.c: mark expected switch fall-through
    mm/page_alloc.c: broken deferred calculation
    mm: don't warn about allocations which stall for too long
    fs: fuse: account fuse_inode slab memory as reclaimable
    mm, page_alloc: fix potential false positive in __zone_watermark_ok
    mm: mlock: remove lru_add_drain_all()
    mm, sysctl: make NUMA stats configurable
    shmem: convert shmem_init_inodecache() to void
    Unify migrate_pages and move_pages access checks
    mm, pagevec: rename pagevec drained field
    ...

    Linus Torvalds
     
  • Convert all allocations that used a NOTRACK flag to stop using it.

    Link: http://lkml.kernel.org/r/20171007030159.22241-3-alexander.levin@verizon.com
    Signed-off-by: Sasha Levin
    Cc: Alexander Potapenko
    Cc: Eric W. Biederman
    Cc: Michal Hocko
    Cc: Pekka Enberg
    Cc: Steven Rostedt
    Cc: Tim Hansen
    Cc: Vegard Nossum
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Levin, Alexander (Sasha Levin)
     
  • Patch series "kmemcheck: kill kmemcheck", v2.

    As discussed at LSF/MM, kill kmemcheck.

    KASan is a replacement that is able to work without the limitation of
    kmemcheck (single CPU, slow). KASan is already upstream.

    We are also not aware of any users of kmemcheck (or users who don't
    consider KASan as a suitable replacement).

    The only objection was that since KASAN wasn't supported by all GCC
    versions provided by distros at that time we should hold off for 2
    years, and try again.

    Now that 2 years have passed, and all distros provide gcc that supports
    KASAN, kill kmemcheck again for the very same reasons.

    This patch (of 4):

    Remove kmemcheck annotations, and calls to kmemcheck from the kernel.

    [alexander.levin@verizon.com: correctly remove kmemcheck call from dma_map_sg_attrs]
    Link: http://lkml.kernel.org/r/20171012192151.26531-1-alexander.levin@verizon.com
    Link: http://lkml.kernel.org/r/20171007030159.22241-2-alexander.levin@verizon.com
    Signed-off-by: Sasha Levin
    Cc: Alexander Potapenko
    Cc: Eric W. Biederman
    Cc: Michal Hocko
    Cc: Pekka Enberg
    Cc: Steven Rostedt
    Cc: Tim Hansen
    Cc: Vegard Nossum
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Levin, Alexander (Sasha Levin)
     
  • According to discussion with Christoph
    (https://marc.info/?l=linux-kernel&m=150695909709711&w=2), it sounds like
    it is pointless to keep CONFIG_SLABINFO around.

    This patch removes the CONFIG_SLABINFO config option, but /proc/slabinfo
    is still available.

    [yang.s@alibaba-inc.com: v11]
    Link: http://lkml.kernel.org/r/1507656303-103845-3-git-send-email-yang.s@alibaba-inc.com
    Link: http://lkml.kernel.org/r/1507152550-46205-3-git-send-email-yang.s@alibaba-inc.com
    Signed-off-by: Yang Shi
    Acked-by: David Rientjes
    Cc: Christoph Lameter
    Cc: Joonsoo Kim
    Cc: Michal Hocko
    Cc: Pekka Enberg
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Yang Shi
     
  • Pull PCI updates from Bjorn Helgaas:

    - detach driver before tearing down procfs/sysfs (Alex Williamson)

    - disable PCIe services during shutdown (Sinan Kaya)

    - fix ASPM oops on systems with no Root Ports (Ard Biesheuvel)

    - fix ASPM LTR_L1.2_THRESHOLD programming (Bjorn Helgaas)

    - fix ASPM Common_Mode_Restore_Time computation (Bjorn Helgaas)

    - fix portdrv MSI/MSI-X vector allocation (Dongdong Liu, Bjorn
    Helgaas)

    - report non-fatal AER errors only to the affected endpoint (Gabriele
    Paoloni)

    - distribute bus numbers, MMIO, and I/O space among hotplug bridges to
    allow more devices to be hot-added (Mika Westerberg)

    - fix pciehp races during initialization and surprise link down (Mika
    Westerberg)

    - handle surprise-removed devices in PME handling (Qiang)

    - support resizable BARs for large graphics devices (Christian König)

    - expose SR-IOV offset, stride, and VF device ID via sysfs (Filippo
    Sironi)

    - create SR-IOV virtfn/physfn sysfs links before attaching driver
    (Stuart Hayes)

    - fix SR-IOV "ARI Capable Hierarchy" restore issue (Tony Nguyen)

    - enforce Kconfig IOV/REALLOC dependency (Sascha El-Sharkawy)

    - avoid slot reset if bridge itself is broken (Jan Glauber)

    - clean up pci_reset_function() path (Jan H. Schönherr)

    - make pci_map_rom() fail if the option ROM is invalid (Changbin Du)

    - convert timers to timer_setup() (Kees Cook)

    - move PCI_QUIRKS to PCI bus Kconfig menu (Randy Dunlap)

    - constify pci_dev_type and intel_mid_pci_ops (Bhumika Goyal)

    - remove unnecessary pci_dev, pci_bus, resource, pcibios_set_master()
    declarations (Bjorn Helgaas)

    - fix endpoint framework overflows and BUG()s (Dan Carpenter)

    - fix endpoint framework issues (Kishon Vijay Abraham I)

    - avoid broken Cavium CN8xxx bus reset behavior (David Daney)

    - extend Cavium ACS capability quirks (Vadim Lomovtsev)

    - support Synopsys DesignWare RC in ECAM mode (Ard Biesheuvel)

    - turn off dra7xx clocks cleanly on shutdown (Keerthy)

    - fix Faraday probe error path (Wei Yongjun)

    - support HiSilicon STB SoC PCIe host controller (Jianguo Sun)

    - fix Hyper-V interrupt affinity issue (Dexuan Cui)

    - remove useless ACPI warning for Hyper-V pass-through devices (Vitaly
    Kuznetsov)

    - support multiple MSI on iProc (Sandor Bodo-Merle)

    - support Layerscape LS1012a and LS1046a PCIe host controllers (Hou
    Zhiqiang)

    - fix Layerscape default error response (Minghuan Lian)

    - support MSI on Tango host controller (Marc Gonzalez)

    - support Tegra186 PCIe host controller (Manikanta Maddireddy)

    - use generic accessors on Tegra when possible (Thierry Reding)

    - support V3 Semiconductor PCI host controller (Linus Walleij)

    * tag 'pci-v4.15-changes' of git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci: (85 commits)
    PCI/ASPM: Add L1 Substates definitions
    PCI/ASPM: Reformat ASPM register definitions
    PCI/ASPM: Use correct capability pointer to program LTR_L1.2_THRESHOLD
    PCI/ASPM: Account for downstream device's Port Common_Mode_Restore_Time
    PCI: xgene: Rename xgene_pcie_probe_bridge() to xgene_pcie_probe()
    PCI: xilinx: Rename xilinx_pcie_link_is_up() to xilinx_pcie_link_up()
    PCI: altera: Rename altera_pcie_link_is_up() to altera_pcie_link_up()
    PCI: Fix kernel-doc build warning
    PCI: Fail pci_map_rom() if the option ROM is invalid
    PCI: Move pci_map_rom() error path
    PCI: Move PCI_QUIRKS to the PCI bus menu
    alpha/PCI: Make pdev_save_srm_config() static
    PCI: Remove unused declarations
    PCI: Remove redundant pci_dev, pci_bus, resource declarations
    PCI: Remove redundant pcibios_set_master() declarations
    PCI/PME: Handle invalid data when reading Root Status
    PCI: hv: Use effective affinity mask
    PCI: pciehp: Do not clear Presence Detect Changed during initialization
    PCI: pciehp: Fix race condition handling surprise link down
    PCI: Distribute available resources to hotplug-capable bridges
    ...

    Linus Torvalds
     
  • Pull trivial tree updates from Jiri Kosina:
    "The usual rocket-science from trivial tree for 4.15"

    * 'for-linus' of ssh://gitolite.kernel.org/pub/scm/linux/kernel/git/jikos/trivial:
    MAINTAINERS: relinquish kconfig
    MAINTAINERS: Update my email address
    treewide: Fix typos in Kconfig
    kfifo: Fix comments
    init/Kconfig: Fix module signing document location
    misc: ibmasm: Return error on error path
    HID: logitech-hidpp: fix mistake in printk, "feeback" -> "feedback"
    MAINTAINERS: Correct path to uDraw PS3 driver
    tracing: Fix doc mistakes in trace sample
    tracing: Kconfig text fixes for CONFIG_HWLAT_TRACER
    MIPS: Alchemy: Remove reverted CONFIG_NETLINK_MMAP from db1xxx_defconfig
    mm/huge_memory.c: fixup grammar in comment
    lib/xz: Add fall-through comments to a switch statement

    Linus Torvalds
     

14 Nov, 2017

1 commit

  • Pull x86 APIC updates from Thomas Gleixner:
    "This update provides a major overhaul of the APIC initialization and
    vector allocation code:

    - Unification of the APIC and interrupt mode setup which was
    scattered all over the place and was hard to follow. This also
    distangles the timer setup from the APIC initialization which
    brings a clear separation of functionality.

    Great detective work from Dou Lyiang!

    - Refactoring of the x86 vector allocation mechanism. The existing
    code was based on nested loops and rather convoluted APIC callbacks
    which had a horrible worst case behaviour and tried to serve all
    different use cases in one go. This led to quite odd hacks when
    supporting the new managed interupt facility for multiqueue devices
    and made it more or less impossible to deal with the vector space
    exhaustion which was a major roadblock for server hibernation.

    Aside of that the code dealing with cpu hotplug and the system
    vectors was disconnected from the actual vector management and
    allocation code, which made it hard to follow and maintain.

    Utilizing the new bitmap matrix allocator core mechanism, the new
    allocator and management code consolidates the handling of system
    vectors, legacy vectors, cpu hotplug mechanisms and the actual
    allocation which needs to be aware of system and legacy vectors and
    hotplug constraints into a single consistent entity.

    This has one visible change: The support for multi CPU targets of
    interrupts, which is only available on a certain subset of
    CPUs/APIC variants has been removed in favour of single interrupt
    targets. A proper analysis of the multi CPU target feature revealed
    that there is no real advantage as the vast majority of interrupts
    end up on the CPU with the lowest APIC id in the set of target CPUs
    anyway. That change was agreed on by the relevant folks and allowed
    to simplify the implementation significantly and to replace rather
    fragile constructs like the vector cleanup IPI with straight
    forward and solid code.

    Furthermore this allowed to cleanly separate the allocation details
    for legacy, normal and managed interrupts:

    * Legacy interrupts are not longer wasting 16 vectors
    unconditionally

    * Managed interrupts have now a guaranteed vector reservation, but
    the actual vector assignment happens when the interrupt is
    requested. It's guaranteed not to fail.

    * Normal interrupts no longer allocate vectors unconditionally
    when the interrupt is set up (IO/APIC init or MSI(X) enable).
    The mechanism has been switched to a best effort reservation
    mode. The actual allocation happens when the interrupt is
    requested. Contrary to managed interrupts the request can fail
    due to vector space exhaustion, but drivers must handle a fail
    of request_irq() anyway. When the interrupt is freed, the vector
    is handed back as well.

    This solves a long standing problem with large unconditional
    vector allocations for a certain class of enterprise devices
    which prevented server hibernation due to vector space
    exhaustion when the unused allocated vectors had to be migrated
    to CPU0 while unplugging all non boot CPUs.

    The code has been equipped with trace points and detailed debugfs
    information to aid analysis of the vector space"

    * 'x86-apic-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (60 commits)
    x86/vector/msi: Select CONFIG_GENERIC_IRQ_RESERVATION_MODE
    PCI/MSI: Set MSI_FLAG_MUST_REACTIVATE in core code
    genirq: Add config option for reservation mode
    x86/vector: Use correct per cpu variable in free_moved_vector()
    x86/apic/vector: Ignore set_affinity call for inactive interrupts
    x86/apic: Fix spelling mistake: "symmectic" -> "symmetric"
    x86/apic: Use dead_cpu instead of current CPU when cleaning up
    ACPI/init: Invoke early ACPI initialization earlier
    x86/vector: Respect affinity mask in irq descriptor
    x86/irq: Simplify hotplug vector accounting
    x86/vector: Switch IOAPIC to global reservation mode
    x86/vector/msi: Switch to global reservation mode
    x86/vector: Handle managed interrupts proper
    x86/io_apic: Reevaluate vector configuration on activate()
    iommu/amd: Reevaluate vector configuration on activate()
    iommu/vt-d: Reevaluate vector configuration on activate()
    x86/apic/msi: Force reactivation of interrupts at startup time
    x86/vector: Untangle internal state from irq_cfg
    x86/vector: Compile SMP only code conditionally
    x86/apic: Remove unused callbacks
    ...

    Linus Torvalds
     

08 Nov, 2017

2 commits


07 Nov, 2017

1 commit


03 Nov, 2017

1 commit

  • …el/git/gregkh/driver-core

    Pull initial SPDX identifiers from Greg KH:
    "License cleanup: add SPDX license identifiers to some files

    Many source files in the tree are missing licensing information, which
    makes it harder for compliance tools to determine the correct license.

    By default all files without license information are under the default
    license of the kernel, which is GPL version 2.

    Update the files which contain no license information with the
    'GPL-2.0' SPDX license identifier. The SPDX identifier is a legally
    binding shorthand, which can be used instead of the full boiler plate
    text.

    This patch is based on work done by Thomas Gleixner and Kate Stewart
    and Philippe Ombredanne.

    How this work was done:

    Patches were generated and checked against linux-4.14-rc6 for a subset
    of the use cases:

    - file had no licensing information it it.

    - file was a */uapi/* one with no licensing information in it,

    - file was a */uapi/* one with existing licensing information,

    Further patches will be generated in subsequent months to fix up cases
    where non-standard license headers were used, and references to
    license had to be inferred by heuristics based on keywords.

    The analysis to determine which SPDX License Identifier to be applied
    to a file was done in a spreadsheet of side by side results from of
    the output of two independent scanners (ScanCode & Windriver)
    producing SPDX tag:value files created by Philippe Ombredanne.
    Philippe prepared the base worksheet, and did an initial spot review
    of a few 1000 files.

    The 4.13 kernel was the starting point of the analysis with 60,537
    files assessed. Kate Stewart did a file by file comparison of the
    scanner results in the spreadsheet to determine which SPDX license
    identifier(s) to be applied to the file. She confirmed any
    determination that was not immediately clear with lawyers working with
    the Linux Foundation.

    Criteria used to select files for SPDX license identifier tagging was:

    - Files considered eligible had to be source code files.

    - Make and config files were included as candidates if they contained
    >5 lines of source

    - File already had some variant of a license header in it (even if <5
    lines).

    All documentation files were explicitly excluded.

    The following heuristics were used to determine which SPDX license
    identifiers to apply.

    - when both scanners couldn't find any license traces, file was
    considered to have no license information in it, and the top level
    COPYING file license applied.

    For non */uapi/* files that summary was:

    SPDX license identifier # files
    ---------------------------------------------------|-------
    GPL-2.0 11139

    and resulted in the first patch in this series.

    If that file was a */uapi/* path one, it was "GPL-2.0 WITH
    Linux-syscall-note" otherwise it was "GPL-2.0". Results of that
    was:

    SPDX license identifier # files
    ---------------------------------------------------|-------
    GPL-2.0 WITH Linux-syscall-note 930

    and resulted in the second patch in this series.

    - if a file had some form of licensing information in it, and was one
    of the */uapi/* ones, it was denoted with the Linux-syscall-note if
    any GPL family license was found in the file or had no licensing in
    it (per prior point). Results summary:

    SPDX license identifier # files
    ---------------------------------------------------|------
    GPL-2.0 WITH Linux-syscall-note 270
    GPL-2.0+ WITH Linux-syscall-note 169
    ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause) 21
    ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause) 17
    LGPL-2.1+ WITH Linux-syscall-note 15
    GPL-1.0+ WITH Linux-syscall-note 14
    ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause) 5
    LGPL-2.0+ WITH Linux-syscall-note 4
    LGPL-2.1 WITH Linux-syscall-note 3
    ((GPL-2.0 WITH Linux-syscall-note) OR MIT) 3
    ((GPL-2.0 WITH Linux-syscall-note) AND MIT) 1

    and that resulted in the third patch in this series.

    - when the two scanners agreed on the detected license(s), that
    became the concluded license(s).

    - when there was disagreement between the two scanners (one detected
    a license but the other didn't, or they both detected different
    licenses) a manual inspection of the file occurred.

    - In most cases a manual inspection of the information in the file
    resulted in a clear resolution of the license that should apply
    (and which scanner probably needed to revisit its heuristics).

    - When it was not immediately clear, the license identifier was
    confirmed with lawyers working with the Linux Foundation.

    - If there was any question as to the appropriate license identifier,
    the file was flagged for further research and to be revisited later
    in time.

    In total, over 70 hours of logged manual review was done on the
    spreadsheet to determine the SPDX license identifiers to apply to the
    source files by Kate, Philippe, Thomas and, in some cases,
    confirmation by lawyers working with the Linux Foundation.

    Kate also obtained a third independent scan of the 4.13 code base from
    FOSSology, and compared selected files where the other two scanners
    disagreed against that SPDX file, to see if there was new insights.
    The Windriver scanner is based on an older version of FOSSology in
    part, so they are related.

    Thomas did random spot checks in about 500 files from the spreadsheets
    for the uapi headers and agreed with SPDX license identifier in the
    files he inspected. For the non-uapi files Thomas did random spot
    checks in about 15000 files.

    In initial set of patches against 4.14-rc6, 3 files were found to have
    copy/paste license identifier errors, and have been fixed to reflect
    the correct identifier.

    Additionally Philippe spent 10 hours this week doing a detailed manual
    inspection and review of the 12,461 patched files from the initial
    patch version early this week with:

    - a full scancode scan run, collecting the matched texts, detected
    license ids and scores

    - reviewing anything where there was a license detected (about 500+
    files) to ensure that the applied SPDX license was correct

    - reviewing anything where there was no detection but the patch
    license was not GPL-2.0 WITH Linux-syscall-note to ensure that the
    applied SPDX license was correct

    This produced a worksheet with 20 files needing minor correction. This
    worksheet was then exported into 3 different .csv files for the
    different types of files to be modified.

    These .csv files were then reviewed by Greg. Thomas wrote a script to
    parse the csv files and add the proper SPDX tag to the file, in the
    format that the file expected. This script was further refined by Greg
    based on the output to detect more types of files automatically and to
    distinguish between header and source .c files (which need different
    comment types.) Finally Greg ran the script using the .csv files to
    generate the patches.

    Reviewed-by: Kate Stewart <kstewart@linuxfoundation.org>
    Reviewed-by: Philippe Ombredanne <pombredanne@nexb.com>
    Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>"

    * tag 'spdx_identifiers-4.14-rc8' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core:
    License cleanup: add SPDX license identifier to uapi header files with a license
    License cleanup: add SPDX license identifier to uapi header files with no license
    License cleanup: add SPDX GPL-2.0 license identifier to files with no license

    Linus Torvalds
     

02 Nov, 2017

1 commit

  • Many source files in the tree are missing licensing information, which
    makes it harder for compliance tools to determine the correct license.

    By default all files without license information are under the default
    license of the kernel, which is GPL version 2.

    Update the files which contain no license information with the 'GPL-2.0'
    SPDX license identifier. The SPDX identifier is a legally binding
    shorthand, which can be used instead of the full boiler plate text.

    This patch is based on work done by Thomas Gleixner and Kate Stewart and
    Philippe Ombredanne.

    How this work was done:

    Patches were generated and checked against linux-4.14-rc6 for a subset of
    the use cases:
    - file had no licensing information it it.
    - file was a */uapi/* one with no licensing information in it,
    - file was a */uapi/* one with existing licensing information,

    Further patches will be generated in subsequent months to fix up cases
    where non-standard license headers were used, and references to license
    had to be inferred by heuristics based on keywords.

    The analysis to determine which SPDX License Identifier to be applied to
    a file was done in a spreadsheet of side by side results from of the
    output of two independent scanners (ScanCode & Windriver) producing SPDX
    tag:value files created by Philippe Ombredanne. Philippe prepared the
    base worksheet, and did an initial spot review of a few 1000 files.

    The 4.13 kernel was the starting point of the analysis with 60,537 files
    assessed. Kate Stewart did a file by file comparison of the scanner
    results in the spreadsheet to determine which SPDX license identifier(s)
    to be applied to the file. She confirmed any determination that was not
    immediately clear with lawyers working with the Linux Foundation.

    Criteria used to select files for SPDX license identifier tagging was:
    - Files considered eligible had to be source code files.
    - Make and config files were included as candidates if they contained >5
    lines of source
    - File already had some variant of a license header in it (even if
    Reviewed-by: Philippe Ombredanne
    Reviewed-by: Thomas Gleixner
    Signed-off-by: Greg Kroah-Hartman

    Greg Kroah-Hartman
     

27 Oct, 2017

3 commits

  • We want to centralize the isolation management, done by the housekeeping
    subsystem. Therefore we need to handle the nohz_full= parameter from
    there.

    Since nohz_full= so far has involved unbound timers, watchdog, RCU
    and tilegx NAPI isolation, we keep that default behaviour.

    nohz_full= will be deprecated in the future. We want to control
    the isolation features from the isolcpus= parameter.

    Signed-off-by: Frederic Weisbecker
    Acked-by: Thomas Gleixner
    Cc: Chris Metcalf
    Cc: Christoph Lameter
    Cc: Linus Torvalds
    Cc: Luiz Capitulino
    Cc: Mike Galbraith
    Cc: Paul E. McKenney
    Cc: Peter Zijlstra
    Cc: Rik van Riel
    Cc: Wanpeng Li
    Link: http://lkml.kernel.org/r/1509072159-31808-10-git-send-email-frederic@kernel.org
    Signed-off-by: Ingo Molnar

    Frederic Weisbecker
     
  • Split the housekeeping config from CONFIG_NO_HZ_FULL. This way we finally
    separate the isolation code from NOHZ.

    Although a dependency to CONFIG_NO_HZ_FULL remains for now, while the
    housekeeping code still deals with NOHZ internals.

    Signed-off-by: Frederic Weisbecker
    Acked-by: Thomas Gleixner
    Cc: Chris Metcalf
    Cc: Christoph Lameter
    Cc: Linus Torvalds
    Cc: Luiz Capitulino
    Cc: Mike Galbraith
    Cc: Paul E. McKenney
    Cc: Peter Zijlstra
    Cc: Rik van Riel
    Cc: Wanpeng Li
    Link: http://lkml.kernel.org/r/1509072159-31808-8-git-send-email-frederic@kernel.org
    Signed-off-by: Ingo Molnar

    Frederic Weisbecker
     
  • The housekeeping code is currently tied to the NOHZ code. As we are
    planning to make housekeeping independent from it, start with moving
    the relevant code to its own file.

    Signed-off-by: Frederic Weisbecker
    Acked-by: Thomas Gleixner
    Acked-by: Paul E. McKenney
    Cc: Chris Metcalf
    Cc: Christoph Lameter
    Cc: Linus Torvalds
    Cc: Luiz Capitulino
    Cc: Mike Galbraith
    Cc: Peter Zijlstra
    Cc: Rik van Riel
    Cc: Wanpeng Li
    Link: http://lkml.kernel.org/r/1509072159-31808-2-git-send-email-frederic@kernel.org
    Signed-off-by: Ingo Molnar

    Frederic Weisbecker
     

12 Oct, 2017

1 commit


07 Oct, 2017

1 commit

  • The choice containing the CC_OPTIMIZE_FOR_PERFORMANCE symbol
    accidentally added a "CONFIG_" prefix when trying to make it the
    default, selecting an undefined symbol as the default.

    The mistake is harmless here: Since the default symbol is not visible,
    the choice falls back on using the visible symbol as the default
    instead, which is CC_OPTIMIZE_FOR_PERFORMANCE, as intended.

    A patch that makes Kconfig print a warning in this case has been
    submitted separately:
    http://www.spinics.net/lists/linux-kbuild/msg15566.html

    Signed-off-by: Ulf Magnusson
    Acked-by: Arnd Bergmann
    Signed-off-by: Masahiro Yamada

    Ulf Magnusson
     

27 Sep, 2017

1 commit

  • acpi_early_init() unmaps the temporary ACPI Table mappings which are used
    in the early startup code and prepares for permanent table mappings.

    Before the consolidation of the x86 APIC setup code the invocation of
    acpi_early_init() happened before the interrupt remapping unit was
    initialized. With the rework the remapping unit initialization moved in
    front of acpi_early_init() which causes an ACPI warning when the ACPI root
    tables get reallocated afterwards.

    Invoke acpi_early_init() before late_time_init() which is before the access
    to the DMAR tables happens.

    Fixes: 935356cecda8 ("x86/apic: Initialize interrupt mode after timer init")
    Reported-by: Xiaolong Ye
    Signed-off-by: Dou Liyang
    Cc: Tony Luck
    Cc: linux-ia64@vger.kernel.org
    Cc: bhe@redhat.com
    Cc: Fenghua Yu
    Cc: Michael Ellerman
    Cc: "Rafael J. Wysocki"
    Cc: Will Deacon
    Cc: linux-acpi@vger.kernel.org
    Cc: bp@alien8.de
    Cc: Lv"
    Cc: yinghai@kernel.org
    Cc: linux-arm-kernel@lists.infradead.org
    Link: https://lkml.kernel.org/r/1505294274-441-1-git-send-email-douly.fnst@cn.fujitsu.com
    Signed-off-by: Thomas Gleixner

    Dou Liyang
     

15 Sep, 2017

2 commits

  • Pull mount flag updates from Al Viro:
    "Another chunk of fmount preparations from dhowells; only trivial
    conflicts for that part. It separates MS_... bits (very grotty
    mount(2) ABI) from the struct super_block ->s_flags (kernel-internal,
    only a small subset of MS_... stuff).

    This does *not* convert the filesystems to new constants; only the
    infrastructure is done here. The next step in that series is where the
    conflicts would be; that's the conversion of filesystems. It's purely
    mechanical and it's better done after the merge, so if you could run
    something like

    list=$(for i in MS_RDONLY MS_NOSUID MS_NODEV MS_NOEXEC MS_SYNCHRONOUS MS_MANDLOCK MS_DIRSYNC MS_NOATIME MS_NODIRATIME MS_SILENT MS_POSIXACL MS_KERNMOUNT MS_I_VERSION MS_LAZYTIME; do git grep -l $i fs drivers/staging/lustre drivers/mtd ipc mm include/linux; done|sort|uniq|grep -v '^fs/namespace.c$')

    sed -i -e 's/\/SB_RDONLY/g' \
    -e 's/\/SB_NOSUID/g' \
    -e 's/\/SB_NODEV/g' \
    -e 's/\/SB_NOEXEC/g' \
    -e 's/\/SB_SYNCHRONOUS/g' \
    -e 's/\/SB_MANDLOCK/g' \
    -e 's/\/SB_DIRSYNC/g' \
    -e 's/\/SB_NOATIME/g' \
    -e 's/\/SB_NODIRATIME/g' \
    -e 's/\/SB_SILENT/g' \
    -e 's/\/SB_POSIXACL/g' \
    -e 's/\/SB_KERNMOUNT/g' \
    -e 's/\/SB_I_VERSION/g' \
    -e 's/\/SB_LAZYTIME/g' \
    $list

    and commit it with something along the lines of 'convert filesystems
    away from use of MS_... constants' as commit message, it would save a
    quite a bit of headache next cycle"

    * 'work.mount' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs:
    VFS: Differentiate mount flags (MS_*) from internal superblock flags
    VFS: Convert sb->s_flags & MS_RDONLY to sb_rdonly(sb)
    vfs: Add sb_rdonly(sb) to query the MS_RDONLY flag on s_flags

    Linus Torvalds
     
  • Pull ipc compat cleanup and 64-bit time_t from Al Viro:
    "IPC copyin/copyout sanitizing, including 64bit time_t work from Deepa
    Dinamani"

    * 'work.ipc' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs:
    utimes: Make utimes y2038 safe
    ipc: shm: Make shmid_kernel timestamps y2038 safe
    ipc: sem: Make sem_array timestamps y2038 safe
    ipc: msg: Make msg_queue timestamps y2038 safe
    ipc: mqueue: Replace timespec with timespec64
    ipc: Make sys_semtimedop() y2038 safe
    get rid of SYSVIPC_COMPAT on ia64
    semtimedop(): move compat to native
    shmat(2): move compat to native
    msgrcv(2), msgsnd(2): move compat to native
    ipc(2): move compat to native
    ipc: make use of compat ipc_perm helpers
    semctl(): move compat to native
    semctl(): separate all layout-dependent copyin/copyout
    msgctl(): move compat to native
    msgctl(): split the actual work from copyin/copyout
    ipc: move compat shmctl to native
    shmctl: split the work from copyin/copyout

    Linus Torvalds
     

09 Sep, 2017

2 commits

  • Feed the boot command-line as to the /dev/random entropy pool

    Existing Android bootloaders usually pass data which may not be known by
    an external attacker on the kernel command-line. It may also be the
    case on other embedded systems. Sample command-line from a Google Pixel
    running CopperheadOS....

    console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0
    androidboot.hardware=sailfish user_debug=31 ehci-hcd.park=3
    lpm_levels.sleep_disabled=1 cma=32M@0-0xffffffff buildvariant=user
    veritykeyid=id:dfcb9db0089e5b3b4090a592415c28e1cb4545ab
    androidboot.bootdevice=624000.ufshc androidboot.verifiedbootstate=yellow
    androidboot.veritymode=enforcing androidboot.keymaster=1
    androidboot.serialno=FA6CE0305299 androidboot.baseband=msm
    mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_samsung_ea8064tg_1080p_cmd:1:none:cfg:single_dsi
    androidboot.slot_suffix=_b fpsimd.fpsimd_settings=0
    app_setting.use_app_setting=0 kernelflag=0x00000000 debugflag=0x00000000
    androidboot.hardware.revision=PVT radioflag=0x00000000
    radioflagex1=0x00000000 radioflagex2=0x00000000 cpumask=0x00000000
    androidboot.hardware.ddr=4096MB,Hynix,LPDDR4 androidboot.ddrinfo=00000006
    androidboot.ddrsize=4GB androidboot.hardware.color=GRA00
    androidboot.hardware.ufs=32GB,Samsung androidboot.msm.hw_ver_id=268824801
    androidboot.qf.st=2 androidboot.cid=11111111 androidboot.mid=G-2PW4100
    androidboot.bootloader=8996-012001-1704121145
    androidboot.oem_unlock_support=1 androidboot.fp_src=1
    androidboot.htc.hrdump=detected androidboot.ramdump.opt=mem@2g:2g,mem@4g:2g
    androidboot.bootreason=reboot androidboot.ramdump_enable=0 ro
    root=/dev/dm-0 dm="system none ro,0 1 android-verity /dev/sda34"
    rootwait skip_initramfs init=/init androidboot.wificountrycode=US
    androidboot.boottime=1BLL:85,1BLE:669,2BLL:0,2BLE:1777,SW:6,KL:8136

    Among other things, it contains a value unique to the device
    (androidboot.serialno=FA6CE0305299), unique to the OS builds for the
    device variant (veritykeyid=id:dfcb9db0089e5b3b4090a592415c28e1cb4545ab)
    and timings from the bootloader stages in milliseconds
    (androidboot.boottime=1BLL:85,1BLE:669,2BLL:0,2BLE:1777,SW:6,KL:8136).

    [tytso@mit.edu: changelog tweak]
    [labbott@redhat.com: line-wrapped command line]
    Link: http://lkml.kernel.org/r/20170816231458.2299-3-labbott@redhat.com
    Signed-off-by: Daniel Micay
    Signed-off-by: Laura Abbott
    Acked-by: Kees Cook
    Cc: "Theodore Ts'o"
    Cc: Laura Abbott
    Cc: Nick Kralevich
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Daniel Micay
     
  • Patch series "Command line randomness", v3.

    A series to add the kernel command line as a source of randomness.

    This patch (of 2):

    Stack canary intialization involves getting a random number. Getting this
    random number may involve accessing caches or other architectural specific
    features which are not available until after the architecture is setup.
    Move the stack canary initialization later to accommodate this.

    Link: http://lkml.kernel.org/r/20170816231458.2299-2-labbott@redhat.com
    Signed-off-by: Laura Abbott
    Signed-off-by: Laura Abbott
    Acked-by: Kees Cook
    Cc: "Theodore Ts'o"
    Cc: Daniel Micay
    Cc: Nick Kralevich
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Laura Abbott
     

07 Sep, 2017

2 commits

  • Pull percpu updates from Tejun Heo:
    "A lot of changes for percpu this time around. percpu inherited the
    same area allocator from the original pre-virtual-address-mapped
    implementation. This was from the time when percpu allocator wasn't
    used all that much and the implementation was focused on simplicity,
    with the unfortunate computational complexity of O(number of areas
    allocated from the chunk) per alloc / free.

    With the increase in percpu usage, we're hitting cases where the lack
    of scalability is hurting. The most prominent one right now is bpf
    perpcu map creation / destruction which may allocate and free a lot of
    entries consecutively and it's likely that the problem will become
    more prominent in the future.

    To address the issue, Dennis replaced the area allocator with hinted
    bitmap allocator which is more consistent. While the new allocator
    does perform a bit worse in some cases, it outperforms the old
    allocator way more than an order of magnitude in other more common
    scenarios while staying mostly flat in CPU overhead and completely
    flat in memory consumption"

    * 'for-4.14' of git://git.kernel.org/pub/scm/linux/kernel/git/tj/percpu: (27 commits)
    percpu: update header to contain bitmap allocator explanation.
    percpu: update pcpu_find_block_fit to use an iterator
    percpu: use metadata blocks to update the chunk contig hint
    percpu: update free path to take advantage of contig hints
    percpu: update alloc path to only scan if contig hints are broken
    percpu: keep track of the best offset for contig hints
    percpu: skip chunks if the alloc does not fit in the contig hint
    percpu: add first_bit to keep track of the first free in the bitmap
    percpu: introduce bitmap metadata blocks
    percpu: replace area map allocator with bitmap
    percpu: generalize bitmap (un)populated iterators
    percpu: increase minimum percpu allocation size and align first regions
    percpu: introduce nr_empty_pop_pages to help empty page accounting
    percpu: change the number of pages marked in the first_chunk pop bitmap
    percpu: combine percpu address checks
    percpu: modify base_addr to be region specific
    percpu: setup_first_chunk rename schunk/dchunk to chunk
    percpu: end chunk area maps page aligned for the populated bitmap
    percpu: unify allocation of schunk and dchunk
    percpu: setup_first_chunk remove dyn_size and consolidate logic
    ...

    Linus Torvalds
     
  • build_all_zonelists gets a zone parameter to initialize zone's pagesets.
    There is only a single user which gives a non-NULL zone parameter and
    that one doesn't really need the rest of the build_all_zonelists (see
    commit 6dcd73d7011b ("memory-hotplug: allocate zone's pcp before
    onlining pages")).

    Therefore remove setup_zone_pageset from build_all_zonelists and call it
    from its only user directly. This will also remove a pointless zonlists
    rebuilding which is always good.

    Link: http://lkml.kernel.org/r/20170721143915.14161-5-mhocko@kernel.org
    Signed-off-by: Michal Hocko
    Acked-by: Vlastimil Babka
    Cc: Johannes Weiner
    Cc: Joonsoo Kim
    Cc: Mel Gorman
    Cc: Shaohua Li
    Cc: Toshi Kani
    Cc: Wen Congyang
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Michal Hocko