https://github.com/google/kmsan
- HEAD
- refs/heads/dependabot/pip/Documentation/sphinx/pip-0424063bf4
- refs/heads/initialize-all
- refs/heads/kmsan-4.11-rc5
- refs/heads/kmsan-4.12-new
- refs/heads/kmsan-4.19-rc3-last
- refs/heads/kmsan-4.19-rc4-last
- refs/heads/kmsan-4.19-rc8-last
- refs/heads/kmsan-4.19-squeezed
- refs/heads/kmsan-review-v5.13
- refs/heads/kmsan-review-v5.16-rc5
- refs/heads/kmsan-v4.12
- refs/heads/kmsan-v4.13
- refs/heads/kmsan-v4.13-rc7
- refs/heads/kmsan-v4.15
- refs/heads/kmsan-v4.16
- refs/heads/kmsan-v4.16-last
- refs/heads/kmsan-v4.16-rc4
- refs/heads/kmsan-v4.17
- refs/heads/kmsan-v4.17-last
- refs/heads/kmsan-v4.17-rc3
- refs/heads/kmsan-v4.17-rc3-last
- refs/heads/kmsan-v4.17-rc5
- refs/heads/kmsan-v4.17-rc5-last
- refs/heads/kmsan-v4.18-rc4-last
- refs/heads/kmsan-v4.18-rc5
- refs/heads/kmsan-v4.18-rc5-last
- refs/heads/kmsan-v4.18-rc8
- refs/heads/kmsan-v4.18-rc8-last
- refs/heads/kmsan-v4.19
- refs/heads/kmsan-v4.19-last
- refs/heads/kmsan-v4.19-rc1
- refs/heads/kmsan-v4.19-rc1-last
- refs/heads/kmsan-v4.19-rc3
- refs/heads/kmsan-v4.19-rc4
- refs/heads/kmsan-v4.19-rc7
- refs/heads/kmsan-v4.19-rc7-last
- refs/heads/kmsan-v4.19-rc8
- refs/heads/kmsan-v4.20-rc2
- refs/heads/kmsan-v4.20-rc2-last
- refs/heads/kmsan-v4.20-rc3
- refs/heads/kmsan-v4.20-rc3-last
- refs/heads/kmsan-v4.20-rc5
- refs/heads/kmsan-v4.20-rc5-last
- refs/heads/kmsan-v4.20-rc7
- refs/heads/kmsan-v4.20-rc7-last
- refs/heads/kmsan-v5.0
- refs/heads/kmsan-v5.0-last
- refs/heads/kmsan-v5.0-rc1
- refs/heads/kmsan-v5.0-rc1-last
- refs/heads/kmsan-v5.1
- refs/heads/kmsan-v5.1-last
- refs/heads/kmsan-v5.1-rc2
- refs/heads/kmsan-v5.1-rc2-last
- refs/heads/kmsan-v5.1-rc4
- refs/heads/kmsan-v5.1-rc4-last
- refs/heads/kmsan-v5.1-rc7
- refs/heads/kmsan-v5.1-rc7-last
- refs/heads/kmsan-v5.10-rc1
- refs/heads/kmsan-v5.10-rc1-last
- refs/heads/kmsan-v5.10-rc4
- refs/heads/kmsan-v5.10-rc4-last
- refs/heads/kmsan-v5.11-rc7
- refs/heads/kmsan-v5.11-rc7-last
- refs/heads/kmsan-v5.12-rc6
- refs/heads/kmsan-v5.12-rc6-last
- refs/heads/kmsan-v5.12-rc6-squashed
- refs/heads/kmsan-v5.13
- refs/heads/kmsan-v5.13-last
- refs/heads/kmsan-v5.15
- refs/heads/kmsan-v5.15-last
- refs/heads/kmsan-v5.15-rc2
- refs/heads/kmsan-v5.15-rc2-last
- refs/heads/kmsan-v5.15-rc6
- refs/heads/kmsan-v5.15-rc6-last
- refs/heads/kmsan-v5.15-rc7
- refs/heads/kmsan-v5.15-rc7-last
- refs/heads/kmsan-v5.16-rc2
- refs/heads/kmsan-v5.16-rc2-last
- refs/heads/kmsan-v5.16-rc3
- refs/heads/kmsan-v5.16-rc3-last
- refs/heads/kmsan-v5.16-rc4
- refs/heads/kmsan-v5.16-rc4-last
- refs/heads/kmsan-v5.16-rc5
- refs/heads/kmsan-v5.16-rc5-last
- refs/heads/kmsan-v5.17
- refs/heads/kmsan-v5.17-last
- refs/heads/kmsan-v5.17-rc4
- refs/heads/kmsan-v5.17-rc4-last
- refs/heads/kmsan-v5.17-rc8
- refs/heads/kmsan-v5.17-rc8-last
- refs/heads/kmsan-v5.18
- refs/heads/kmsan-v5.18-last
- refs/heads/kmsan-v5.18-rc3
- refs/heads/kmsan-v5.18-rc3-last
- refs/heads/kmsan-v5.18-rc4
- refs/heads/kmsan-v5.18-rc4-last
- refs/heads/kmsan-v5.19
- refs/heads/kmsan-v5.19-last
- refs/heads/kmsan-v5.19-rc3
- refs/heads/kmsan-v5.19-rc3-last
- refs/heads/kmsan-v5.19-rc4
- refs/heads/kmsan-v5.19-rc4-last
- refs/heads/kmsan-v5.19-rc8
- refs/heads/kmsan-v5.19-rc8-last
- refs/heads/kmsan-v5.2
- refs/heads/kmsan-v5.2-last
- refs/heads/kmsan-v5.2-rc4
- refs/heads/kmsan-v5.2-rc4-last
- refs/heads/kmsan-v5.3
- refs/heads/kmsan-v5.3-last
- refs/heads/kmsan-v5.3-rc3
- refs/heads/kmsan-v5.3-rc3-last
- refs/heads/kmsan-v5.3-rc6
- refs/heads/kmsan-v5.3-rc6-last
- refs/heads/kmsan-v5.3-rc7
- refs/heads/kmsan-v5.3-rc7-last
- refs/heads/kmsan-v5.4-rc2
- refs/heads/kmsan-v5.4-rc2-last
- refs/heads/kmsan-v5.4-rc3
- refs/heads/kmsan-v5.4-rc3-last
- refs/heads/kmsan-v5.4-rc5
- refs/heads/kmsan-v5.4-rc5-last
- refs/heads/kmsan-v5.4-rc8
- refs/heads/kmsan-v5.5-rc1
- refs/heads/kmsan-v5.5-rc1-last
- refs/heads/kmsan-v5.5-rc5
- refs/heads/kmsan-v5.5-rc5-last
- refs/heads/kmsan-v5.6-rc2
- refs/heads/kmsan-v5.6-rc2-last
- refs/heads/kmsan-v5.6-rc6
- refs/heads/kmsan-v5.6-rc6-last
- refs/heads/kmsan-v5.6-rc7
- refs/heads/kmsan-v5.6-rc7-last
- refs/heads/kmsan-v5.7-rc4
- refs/heads/kmsan-v5.7-rc4-last
- refs/heads/kmsan-v5.8-rc5
- refs/heads/kmsan-v5.9-rc4
- refs/heads/kmsan-v5.9-rc4-last
- refs/heads/kmsan-v5.9-rc8
- refs/heads/kmsan-v5.9-rc8-last
- refs/heads/kmsan-v6.0-rc2
- refs/heads/kmsan-v6.0-rc2-last
- refs/heads/kmsan-v6.0-rc3
- refs/heads/kmsan-v6.0-rc3-last
- refs/heads/kmsan-v6.0-rc4
- refs/heads/kmsan-v6.0-rc4-last
- refs/heads/kmsan-v6.0-rc5
- refs/heads/kmsan-v6.1
- refs/heads/kmsan-v6.1-last
- refs/heads/kmsan-v6.1-rc1-last
- refs/heads/kmsan-v6.1-rc2
- refs/heads/kmsan-v6.1-rc2-last
- refs/heads/kmsan-v6.1-rc3
- refs/heads/kmsan-v6.1-rc3-last
- refs/heads/kmsan-v6.1-rc4
- refs/heads/kmsan-v6.1-rc4-last
- refs/heads/kmsan-v6.1-rc5
- refs/heads/kmsan-v6.1-rc5-last
- refs/heads/kmsan-v6.1-rc6
- refs/heads/kmsan-v6.1-rc6-last
- refs/heads/kmsan-v6.1-rc7
- refs/heads/kmsan-v6.1-rc7-last
- refs/heads/kmsan-v6.1-rc8
- refs/heads/kmsan-v6.1-rc8-last
- refs/heads/kmsan-v6.2
- refs/heads/kmsan-v6.2-last
- refs/heads/kmsan-v6.2-rc3
- refs/heads/kmsan-v6.2-rc3-last
- refs/heads/kmsan-v6.2-rc5
- refs/heads/kmsan-v6.2-rc5-last
- refs/heads/kmsan-v6.2-rc6
- refs/heads/kmsan-v6.2-rc6-last
- refs/heads/kmsan-v6.2-rc7
- refs/heads/kmsan-v6.2-rc7-last
- refs/heads/kmsan-v6.2-rc8
- refs/heads/kmsan-v6.2-rc8-last
- refs/heads/kmsan-v6.3
- refs/heads/kmsan-v6.3-last
- refs/heads/kmsan-v6.3-rc1
- refs/heads/kmsan-v6.3-rc1-last
- refs/heads/kmsan-v6.3-rc2
- refs/heads/kmsan-v6.3-rc2-last
- refs/heads/kmsan-v6.3-rc3
- refs/heads/kmsan-v6.3-rc3-last
- refs/heads/kmsan-v6.3-rc5
- refs/heads/kmsan-v6.3-rc5-last
- refs/heads/kmsan-v6.3-rc6
- refs/heads/kmsan-v6.3-rc6-last
- refs/heads/kmsan-v6.3-rc7
- refs/heads/kmsan-v6.3-rc7-last
- refs/heads/kmsan-v6.4
- refs/heads/kmsan-v6.4-last
- refs/heads/kmsan-v6.4-rc1
- refs/heads/kmsan-v6.4-rc1-last
- refs/heads/kmsan-v6.4-rc2
- refs/heads/kmsan-v6.4-rc2-last
- refs/heads/kmsan-v6.4-rc3
- refs/heads/kmsan-v6.4-rc3-last
- refs/heads/kmsan-v6.4-rc4
- refs/heads/kmsan-v6.4-rc4-last
- refs/heads/kmsan-v6.4-rc6
- refs/heads/kmsan-v6.4-rc6-last
- refs/heads/kmsan-v6.4-rc7
- refs/heads/kmsan-v6.4-rc7-last
- refs/heads/kmsan-v6.5-rc1
- refs/heads/master
- refs/heads/torvalds-v5.13
- refs/tags/kmsan-v4.19-rc7-first
Take a new snapshot of a software origin
If the archived software origin currently browsed is not synchronized with its upstream version (for instance when new commits have been issued), you can explicitly request Software Heritage to take a new snapshot of it.
Use the form below to proceed. Once a request has been submitted and accepted, it will be processed as soon as possible. You can then check its processing state by visiting this dedicated page.![swh spinner](/static/img/swh-spinner.gif)
Processing "take a new snapshot" request ...
Permalinks
To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.
Revision | Author | Date | Message | Commit Date |
---|---|---|---|---|
c245345 | Alexander Potapenko | 26 September 2019, 15:49:57 UTC | kmsan: kcov: prettify the code unpoisoning area->list Unpoisoning area->list seems to fix all the problems with kcov_remote_start() false positives. | 14 October 2019, 14:15:25 UTC |
40d8d3f | Andrey Konovalov | 11 July 2019, 12:39:40 UTC | DO-NOT-SUBMIT: usb-fuzzer: main usb gadget fuzzer driver Change-Id: I9a2aa61d24cce60f000f9221bcdc6af1db7f163d | 14 October 2019, 14:15:25 UTC |
0a24190 | Andrey Konovalov | 17 January 2019, 18:26:05 UTC | DO-NOT-SUBMIT: usb, kcov: annotate hub_event Signed-off-by: Andrey Konovalov <andreyknvl@google.com> Change-Id: I03c155761c3f2118288b19ac55c7882ed8538aa8 | 14 October 2019, 14:15:24 UTC |
6bc74b6 | Andrey Konovalov | 17 January 2019, 18:25:34 UTC | DO-NOT-SUBMIT: kcov: remote coverage support Signed-off-by: Andrey Konovalov <andreyknvl@google.com> Change-Id: I9d4631db13ce3c26abd7efba6ddbccd80cc14aae | 14 October 2019, 14:15:24 UTC |
2a80f37 | Alexander Potapenko | 07 August 2019, 11:09:24 UTC | Revert "drm/bochs: Use shadow buffer for bochs framebuffer console" This reverts commit 58540594570778fd149cd8c9b2bff61f2cefa8c9. KMSAN starts reporting a lot of false positives if the drm_fb_helper_dirty_work() callback is invoked. Perhaps the vmap dark magic in drivers/gpu/drm/drm_gem_vram_helper.c is involved. Disable the shadow buffer for now. Change-Id: I255645030b160bc3fe9cf0a472fc78cd4144545b | 14 October 2019, 14:15:24 UTC |
1fc3329 | Alexander Potapenko | 03 December 2018, 14:22:30 UTC | kasan: kmsan: put memory tools into Kconfig.memtools Change-Id: I28dba154db6d07a3bd8b9490c103646041e2d666 | 14 October 2019, 14:15:24 UTC |
6a1b9ef | Alexander Potapenko | 23 November 2018, 16:37:33 UTC | net: support CONFIG_GENERIC_CSUM on x86, enable it for KASAN/KMSAN This is needed to allow memory tools like KASAN and KMSAN see the memory accesses from the checksum code. Without CONFIG_GENERIC_CSUM the tools can't see memory accesses originating from handwritten assembly code. For KASAN it's a question of detecting more bugs, for KMSAN using the C implementation also helps avoid false positives originating from seemingly uninitialized checksum values. Change-Id: I645e2c097253a8d5717ad87e2e2df6f6f67251f3 | 14 October 2019, 14:15:24 UTC |
c345a2a | Alexander Potapenko | 20 November 2018, 14:20:56 UTC | kmsan: add ReST documentation Add Documentation/dev-tools/kmsan.rst and reference it in the dev-tools index. Change-Id: Iac6345065e6804ef811f1124fdf779c67ff1530e | 14 October 2019, 14:15:24 UTC |
3430fc7 | Alexander Potapenko | 09 July 2018, 16:45:43 UTC | kmsan: disable strscpy() optimization under KMSAN Change-Id: I25d1acf5c3df6eff85894cd94f5ddbe93308271c | 14 October 2019, 14:15:24 UTC |
62cccd9 | Alexander Potapenko | 09 November 2018, 16:48:58 UTC | kmsan: hooks for copy_to_user() and friends: Change-Id: I38428b9c7d1909b8441dcec1749b080494a7af99 | 14 October 2019, 14:15:24 UTC |
2323e0e | Alexander Potapenko | 09 November 2018, 16:40:43 UTC | kmsan: unpoisoning buffers from devices etc. Change-Id: Id460e7a86ce564f1357469f53d0c7410ca08f0e9 | 14 October 2019, 14:15:24 UTC |
95a0d00 | Alexander Potapenko | 09 November 2018, 16:24:47 UTC | kmsan: use __msan_memcpy() where possible. Change-Id: Ib2512ce5aa8d457453dd38caa12f58f002166813 | 14 October 2019, 14:15:24 UTC |
d27194b | Alexander Potapenko | 04 December 2018, 12:43:42 UTC | kmsan: disable instrumentation of certain functions kmsan: unpoison |tlb| in arch_tlb_gather_mmu() This is a hack to reduce stackdepot pressure. Change-Id: I684d23dac5a22eb0a4cea71993cb934302b17cea | 14 October 2019, 14:15:24 UTC |
cb3e89d | Alexander Potapenko | 20 December 2018, 16:12:35 UTC | kmsan: call KMSAN hooks where needed Change-Id: I1250a928d9263bf71fdaa067a070bdee686ef47b | 14 October 2019, 14:15:23 UTC |
ef3bfa8 | Alexander Potapenko | 20 December 2018, 16:10:15 UTC | kmsan: mm: call KMSAN hooks from SL[AU]B code In order to report uninitialized memory coming from heap allocations KMSAN has to poison them unless they're created with __GFP_ZERO. Change-Id: I51103b7981d3aabed747d0c85cbdc85568665871 | 14 October 2019, 14:15:23 UTC |
fa5a98b | Alexander Potapenko | 30 November 2018, 10:43:16 UTC | kmsan: disable KMSAN instrumentation for certain kernel parts Change-Id: I90961eabf2dcb9ae992aed259088953bad5e4d6d | 14 October 2019, 14:15:23 UTC |
d4711a1 | Alexander Potapenko | 21 December 2018, 11:05:50 UTC | kmsan: Changing existing files to enable KMSAN builds Change-Id: I37e0b7f2d2f2b0aeac5753ff9d6b411485fc374e | 14 October 2019, 14:15:23 UTC |
349b74f | Alexander Potapenko | 20 December 2018, 14:24:26 UTC | kmsan: Kconfig changes to disable options incompatible with KMSAN Certain config options are currently incompatible with KMSAN, disable them. Change-Id: I4521f5c764cfaeba2fae79c954925c302c5e3bc0 | 14 October 2019, 14:15:23 UTC |
d196b21 | Alexander Potapenko | 04 December 2018, 10:33:21 UTC | kmsan: make READ_ONCE_TASK_STACK() return initialized values To avoid false positives, assume that reading from the task stack always produces initialized values. Change-Id: Ie73e5a41fdc8195699928e65f5cbe0d3d3c9e2fa | 14 October 2019, 14:15:23 UTC |
8f0fe59 | Alexander Potapenko | 09 November 2018, 12:35:36 UTC | kmsan: test_kmsan.c Change-Id: I287e86ae83a82b770f2baa46e5bbdce1dfa65195 | 14 October 2019, 14:15:23 UTC |
506ee44 | Alexander Potapenko | 15 May 2019, 15:06:46 UTC | kmsan: x86: sync metadata pages on page fault Change-Id: I0d54855489870ef1180b37fe2120b601da464bf7 | 14 October 2019, 14:15:23 UTC |
bfaafc5 | Alexander Potapenko | 09 November 2018, 12:35:06 UTC | kmsan: add KMSAN runtime This patch adds the KernelMemorySanitizer runtime and associated files: - arch/x86/include/asm/kmsan.h: assembly definitions for hooking interrupt handlers; - include/linux/kmsan-checks.h: user API to enable/disable KMSAN, poison/unpoison memory etc. - include/linux/kmsan.h: declarations of KMSAN memory hooks to be referenced outside KMSAN runtime - lib/Kconfig.kmsan: declarations for CONFIG_KMSAN and CONFIG_TEST_KMSAN - mm/kmsan/Makefile: boilerplate Makefile - mm/kmsan/kmsan.h: internal KMSAN declarations - mm/kmsan/kmsan.c: core functions that operate with shadow and origin memory and perform checks, utility functions - mm/kmsan/kmsan_entry.c: KMSAN hooks for entry_64.S - mm/kmsan/kmsan_hooks.c: KMSAN hooks for kernel subsystems - mm/kmsan/kmsan_init.c: KMSAN initialization routines - mm/kmsan/kmsan_instr.c: functions called by KMSAN instrumentation - scripts/Makefile.kmsan: CFLAGS_KMSAN Change-Id: I4b3a7aba6d5804afac4f5f7274cadf8675b6e119 | 14 October 2019, 14:15:23 UTC |
8240d29 | Alexander Potapenko | 14 October 2019, 12:57:21 UTC | printk_safe: externalize printk_context Petr Mladek suggested we use this_cpu_read(printk_context) & PRINTK_SAFE_CONTEXT_MASK instead of checking the spinlock status in kmsan_pr_err() This appears to be less intrusive, although we'll need to declare printk_context in some printk header. | 14 October 2019, 14:15:20 UTC |
157064d | Alexander Potapenko | 14 March 2019, 13:18:12 UTC | kmsan: reduce vmalloc space KMSAN is going to use 3/4 of existing vmalloc space to hold the metadata, therefore we lower VMALLOC_END to make sure vmalloc() doesn't allocate past the first 1/4. Change-Id: Iaa5e8e0fc2aa66c956f937f5a1de6e5ef40d57cc | 14 October 2019, 14:15:20 UTC |
4118a38 | Alexander Potapenko | 07 October 2019, 15:10:19 UTC | stackdepot: reserve 5 extra bits in depot_stack_handle_t Some users (currently only KMSAN) may want to use spare bits in depot_stack_handle_t. Let them do so and provide get_dsh_extra_bits() and set_dsh_extra_bits() to access those bits. | 14 October 2019, 14:14:21 UTC |
134fd9a | Alexander Potapenko | 27 September 2019, 13:09:12 UTC | kasan: stackdepot: move filter_irq_stacks() to stackdepot.c filter_irq_stacks() can be used by other tools (e.g. KMSAN), so it needs to be moved to a common location. lib/stackdepot.c seems a good place, as filter_irq_stacks() is usually applied to the output of stack_trace_save(). Signed-off-by: Alexander Potapenko <glider@google.com> | 14 October 2019, 14:04:53 UTC |
092fc85 | Alexander Potapenko | 03 December 2018, 09:00:13 UTC | compiler.h: rename __no_kasan_or_inline into __no_memory_tool_or_inline As we use it for KMSAN as well now, let's change the name to be more generic. Change-Id: I842d88b841bf1c75ab659b0016a808c6dcf7cdae | 14 October 2019, 14:04:53 UTC |
59d036f | Alexander Potapenko | 03 December 2018, 09:13:56 UTC | kmsan: introduce __no_sanitize_memory and __SANITIZE_MEMORY__ __no_sanitize_memory is a function attribute that makes KMSAN ignore the uninitialized values coming from the function's inputs, and initialize the function's outputs. Functions marked with this attribute can't be inlined into functions not marked with it, and vice versa. __SANITIZE_MEMORY__ is a macro that's defined iff the file is instrumented with KMSAN. This is not the same as CONFIG_KMSAN, which is defined for every file. Change-Id: I1f1672652c8392f15f7ca8ac26cd4e71f9cc1e4b | 14 October 2019, 14:04:53 UTC |
166f133 | Alexander Potapenko | 29 November 2018, 17:41:51 UTC | kmsan: gfp: introduce __GFP_NO_KMSAN_SHADOW This flag is to be used by KMSAN runtime to mark that newly created memory pages don't need KMSAN metadata backing them. --- We can't decide what to do here: - do we need to conditionally define ___GFP_NO_KMSAN_SHADOW depending on CONFIG_KMSAN like LOCKDEP does? - if KMSAN is defined, and LOCKDEP is not, do we want to "compactify" the GFP bits? Change-Id: If5d0352fd5711ad103328e2c185eb885e826423a | 14 October 2019, 14:04:53 UTC |
7d17605 | Alexander Potapenko | 02 September 2019, 12:25:03 UTC | stackdepot: prevent Clang from optimizing away stackdepot_memcmp() Clang may replace stackdepot_memcmp() with a call to instrumented bcmp(), which is exactly what we wanted to avoid creating stackdepot_memcmp(). Add a compiler barrier() to prevent optimizations. | 14 October 2019, 14:04:53 UTC |
a5cd49f | Alexander Potapenko | 14 March 2019, 18:47:18 UTC | stackdepot: check depot_index before accessing the stack slab Avoid crashes on corrupted stack ids. Change-Id: I0a0b38ed5057090696a2c6ff0be7cfcc24ae6738 Signed-off-by: Alexander Potapenko <glider@google.com> | 14 October 2019, 14:04:52 UTC |
30fde5f | Alexander Potapenko | 20 November 2018, 09:19:19 UTC | kmsan: added .config.example, .config.extended and README.md Move along, nothing to see here. This patch is only to reduce diff between KMSAN development and review branches. Change-Id: I415f1c33906f09d84b7ae0f4ebac1d4a70bd0648 | 14 October 2019, 14:04:52 UTC |
4f5cafb | Linus Torvalds | 13 October 2019, 23:37:36 UTC | Linux 5.4-rc3 | 13 October 2019, 23:37:36 UTC |
d4615e5 | Linus Torvalds | 13 October 2019, 21:47:10 UTC | Merge tag 'trace-v5.4-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace Pull tracing fixes from Steven Rostedt: "A few tracing fixes: - Remove lockdown from tracefs itself and moved it to the trace directory. Have the open functions there do the lockdown checks. - Fix a few races with opening an instance file and the instance being deleted (Discovered during the lockdown updates). Kept separate from the clean up code such that they can be backported to stable easier. - Clean up and consolidated the checks done when opening a trace file, as there were multiple checks that need to be done, and it did not make sense having them done in each open instance. - Fix a regression in the record mcount code. - Small hw_lat detector tracer fixes. - A trace_pipe read fix due to not initializing trace_seq" * tag 'trace-v5.4-rc2' of git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace: tracing: Initialize iter->seq after zeroing in tracing_read_pipe() tracing/hwlat: Don't ignore outer-loop duration when calculating max_latency tracing/hwlat: Report total time spent in all NMIs during the sample recordmcount: Fix nop_mcount() function tracing: Do not create tracefs files if tracefs lockdown is in effect tracing: Add locked_down checks to the open calls of files created for tracefs tracing: Add tracing_check_open_get_tr() tracing: Have trace events system open call tracing_open_generic_tr() tracing: Get trace_array reference for available_tracers files ftrace: Get a reference counter for the trace_array on filter files tracefs: Revert ccbd54ff54e8 ("tracefs: Restrict tracefs when the kernel is locked down") | 13 October 2019, 21:47:10 UTC |
2581efa | Linus Torvalds | 13 October 2019, 15:40:31 UTC | Merge tag 'hwmon-for-v5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging Pull hwmon fixes from Guenter Roeck: - Update/fix inspur-ipsps1 and k10temp Documentation - Fix nct7904 driver - Fix HWMON_P_MIN_ALARM mask in hwmon core * tag 'hwmon-for-v5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging: hwmon: docs: Extend inspur-ipsps1 title underline hwmon: (nct7904) Add array fan_alarm and vsen_alarm to store the alarms in nct7904_data struct. docs: hwmon: Include 'inspur-ipsps1.rst' into docs hwmon: Fix HWMON_P_MIN_ALARM mask hwmon: (k10temp) Update documentation and add temp2_input info hwmon: (nct7904) Fix the incorrect value of vsen_mask in nct7904_data struct | 13 October 2019, 15:40:31 UTC |
71b1b55 | Linus Torvalds | 13 October 2019, 15:26:54 UTC | Merge tag 'fixes-for-5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux Pull MTD fixes from Richard Weinberger: "Two fixes for MTD: - spi-nor: Fix for a regression in write_sr() - rawnand: Regression fix for the au1550nd driver" * tag 'fixes-for-5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux: mtd: rawnand: au1550nd: Fix au_read_buf16() prototype mtd: spi-nor: Fix direction of the write_sr() transfer | 13 October 2019, 15:26:54 UTC |
b27528b | Linus Torvalds | 13 October 2019, 15:15:35 UTC | Merge tag 'for-linus-20191012' of git://git.kernel.dk/linux-block Pull io_uring fix from Jens Axboe: "Single small fix for a regression in the sequence logic for linked commands" * tag 'for-linus-20191012' of git://git.kernel.dk/linux-block: io_uring: fix sequence logic for timeout requests | 13 October 2019, 15:15:35 UTC |
d303de1 | Petr Mladek | 11 October 2019, 14:21:34 UTC | tracing: Initialize iter->seq after zeroing in tracing_read_pipe() A customer reported the following softlockup: [899688.160002] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [test.sh:16464] [899688.160002] CPU: 0 PID: 16464 Comm: test.sh Not tainted 4.12.14-6.23-azure #1 SLE12-SP4 [899688.160002] RIP: 0010:up_write+0x1a/0x30 [899688.160002] Kernel panic - not syncing: softlockup: hung tasks [899688.160002] RIP: 0010:up_write+0x1a/0x30 [899688.160002] RSP: 0018:ffffa86784d4fde8 EFLAGS: 00000257 ORIG_RAX: ffffffffffffff12 [899688.160002] RAX: ffffffff970fea00 RBX: 0000000000000001 RCX: 0000000000000000 [899688.160002] RDX: ffffffff00000001 RSI: 0000000000000080 RDI: ffffffff970fea00 [899688.160002] RBP: ffffffffffffffff R08: ffffffffffffffff R09: 0000000000000000 [899688.160002] R10: 0000000000000000 R11: 0000000000000000 R12: ffff8b59014720d8 [899688.160002] R13: ffff8b59014720c0 R14: ffff8b5901471090 R15: ffff8b5901470000 [899688.160002] tracing_read_pipe+0x336/0x3c0 [899688.160002] __vfs_read+0x26/0x140 [899688.160002] vfs_read+0x87/0x130 [899688.160002] SyS_read+0x42/0x90 [899688.160002] do_syscall_64+0x74/0x160 It caught the process in the middle of trace_access_unlock(). There is no loop. So, it must be looping in the caller tracing_read_pipe() via the "waitagain" label. Crashdump analyze uncovered that iter->seq was completely zeroed at this point, including iter->seq.seq.size. It means that print_trace_line() was never able to print anything and there was no forward progress. The culprit seems to be in the code: /* reset all but tr, trace, and overruns */ memset(&iter->seq, 0, sizeof(struct trace_iterator) - offsetof(struct trace_iterator, seq)); It was added by the commit 53d0aa773053ab182877 ("ftrace: add logic to record overruns"). It was v2.6.27-rc1. It was the time when iter->seq looked like: struct trace_seq { unsigned char buffer[PAGE_SIZE]; unsigned int len; }; There was no "size" variable and zeroing was perfectly fine. The solution is to reinitialize the structure after or without zeroing. Link: http://lkml.kernel.org/r/20191011142134.11997-1-pmladek@suse.com Signed-off-by: Petr Mladek <pmladek@suse.com> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> | 13 October 2019, 00:49:34 UTC |
fc64e4a | Srivatsa S. Bhat (VMware) | 10 October 2019, 18:51:01 UTC | tracing/hwlat: Don't ignore outer-loop duration when calculating max_latency max_latency is intended to record the maximum ever observed hardware latency, which may occur in either part of the loop (inner/outer). So we need to also consider the outer-loop sample when updating max_latency. Link: http://lkml.kernel.org/r/157073345463.17189.18124025522664682811.stgit@srivatsa-ubuntu Fixes: e7c15cd8a113 ("tracing: Added hardware latency tracer") Cc: stable@vger.kernel.org Signed-off-by: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> | 13 October 2019, 00:49:33 UTC |
98dc19c | Srivatsa S. Bhat (VMware) | 10 October 2019, 18:50:46 UTC | tracing/hwlat: Report total time spent in all NMIs during the sample nmi_total_ts is supposed to record the total time spent in *all* NMIs that occur on the given CPU during the (active portion of the) sampling window. However, the code seems to be overwriting this variable for each NMI, thereby only recording the time spent in the most recent NMI. Fix it by accumulating the duration instead. Link: http://lkml.kernel.org/r/157073343544.17189.13911783866738671133.stgit@srivatsa-ubuntu Fixes: 7b2c86250122 ("tracing: Add NMI tracing in hwlat detector") Cc: stable@vger.kernel.org Signed-off-by: Srivatsa S. Bhat (VMware) <srivatsa@csail.mit.edu> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> | 13 October 2019, 00:49:33 UTC |
7f8557b | Steven Rostedt (VMware) | 09 October 2019, 15:05:38 UTC | recordmcount: Fix nop_mcount() function The removal of the longjmp code in recordmcount.c mistakenly made the return of make_nop() being negative an exit of nop_mcount(). It should not exit the routine, but instead just not process that part of the code. By exiting with an error code, it would cause the update of recordmcount to fail some files which would fail the build if ftrace function tracing was enabled. Link: http://lkml.kernel.org/r/20191009110538.5909fec6@gandalf.local.home Reported-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Tested-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Fixes: 3f1df12019f3 ("recordmcount: Rewrite error/success handling") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> | 13 October 2019, 00:49:33 UTC |
bf8e602 | Steven Rostedt (VMware) | 12 October 2019, 00:41:41 UTC | tracing: Do not create tracefs files if tracefs lockdown is in effect If on boot up, lockdown is activated for tracefs, don't even bother creating the files. This can also prevent instances from being created if lockdown is in effect. Link: http://lkml.kernel.org/r/CAHk-=whC6Ji=fWnjh2+eS4b15TnbsS4VPVtvBOwCy1jjEG_JHQ@mail.gmail.com Suggested-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> | 13 October 2019, 00:49:07 UTC |
17911ff | Steven Rostedt (VMware) | 11 October 2019, 21:22:50 UTC | tracing: Add locked_down checks to the open calls of files created for tracefs Added various checks on open tracefs calls to see if tracefs is in lockdown mode, and if so, to return -EPERM. Note, the event format files (which are basically standard on all machines) as well as the enabled_functions file (which shows what is currently being traced) are not lockde down. Perhaps they should be, but it seems counter intuitive to lockdown information to help you know if the system has been modified. Link: http://lkml.kernel.org/r/CAHk-=wj7fGPKUspr579Cii-w_y60PtRaiDgKuxVtBAMK0VNNkA@mail.gmail.com Suggested-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> | 13 October 2019, 00:48:06 UTC |
8530dec | Steven Rostedt (VMware) | 11 October 2019, 21:39:57 UTC | tracing: Add tracing_check_open_get_tr() Currently, most files in the tracefs directory test if tracing_disabled is set. If so, it should return -ENODEV. The tracing_disabled is called when tracing is found to be broken. Originally it was done in case the ring buffer was found to be corrupted, and we wanted to prevent reading it from crashing the kernel. But it's also called if a tracing selftest fails on boot. It's a one way switch. That is, once it is triggered, tracing is disabled until reboot. As most tracefs files can also be used by instances in the tracefs directory, they need to be carefully done. Each instance has a trace_array associated to it, and when the instance is removed, the trace_array is freed. But if an instance is opened with a reference to the trace_array, then it requires looking up the trace_array to get its ref counter (as there could be a race with it being deleted and the open itself). Once it is found, a reference is added to prevent the instance from being removed (and the trace_array associated with it freed). Combine the two checks (tracing_disabled and trace_array_get()) into a single helper function. This will also make it easier to add lockdown to tracefs later. Link: http://lkml.kernel.org/r/20191011135458.7399da44@gandalf.local.home Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> | 13 October 2019, 00:44:07 UTC |
aa07d71 | Steven Rostedt (VMware) | 11 October 2019, 23:12:21 UTC | tracing: Have trace events system open call tracing_open_generic_tr() Instead of having the trace events system open call open code the taking of the trace_array descriptor (with trace_array_get()) and then calling trace_open_generic(), have it use the tracing_open_generic_tr() that does the combination of the two. This requires making tracing_open_generic_tr() global. Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> | 13 October 2019, 00:43:00 UTC |
194c2c7 | Steven Rostedt (VMware) | 11 October 2019, 22:19:17 UTC | tracing: Get trace_array reference for available_tracers files As instances may have different tracers available, we need to look at the trace_array descriptor that shows the list of the available tracers for the instance. But there's a race between opening the file and an admin deleting the instance. The trace_array_get() needs to be called before accessing the trace_array. Cc: stable@vger.kernel.org Fixes: 607e2ea167e56 ("tracing: Set up infrastructure to allow tracers for instances") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> | 13 October 2019, 00:40:50 UTC |
9ef1669 | Steven Rostedt (VMware) | 11 October 2019, 21:56:57 UTC | ftrace: Get a reference counter for the trace_array on filter files The ftrace set_ftrace_filter and set_ftrace_notrace files are specific for an instance now. They need to take a reference to the instance otherwise there could be a race between accessing the files and deleting the instance. It wasn't until the :mod: caching where these file operations started referencing the trace_array directly. Cc: stable@vger.kernel.org Fixes: 673feb9d76ab3 ("ftrace: Add :mod: caching infrastructure to trace_array") Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> | 13 October 2019, 00:40:21 UTC |
3ed270b | Steven Rostedt (VMware) | 11 October 2019, 17:54:58 UTC | tracefs: Revert ccbd54ff54e8 ("tracefs: Restrict tracefs when the kernel is locked down") Running the latest kernel through my "make instances" stress tests, I triggered the following bug (with KASAN and kmemleak enabled): mkdir invoked oom-killer: gfp_mask=0x40cd0(GFP_KERNEL|__GFP_COMP|__GFP_RECLAIMABLE), order=0, oom_score_adj=0 CPU: 1 PID: 2229 Comm: mkdir Not tainted 5.4.0-rc2-test #325 Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.6 02/22/2014 Call Trace: dump_stack+0x64/0x8c dump_header+0x43/0x3b7 ? trace_hardirqs_on+0x48/0x4a oom_kill_process+0x68/0x2d5 out_of_memory+0x2aa/0x2d0 __alloc_pages_nodemask+0x96d/0xb67 __alloc_pages_node+0x19/0x1e alloc_slab_page+0x17/0x45 new_slab+0xd0/0x234 ___slab_alloc.constprop.86+0x18f/0x336 ? alloc_inode+0x2c/0x74 ? irq_trace+0x12/0x1e ? tracer_hardirqs_off+0x1d/0xd7 ? __slab_alloc.constprop.85+0x21/0x53 __slab_alloc.constprop.85+0x31/0x53 ? __slab_alloc.constprop.85+0x31/0x53 ? alloc_inode+0x2c/0x74 kmem_cache_alloc+0x50/0x179 ? alloc_inode+0x2c/0x74 alloc_inode+0x2c/0x74 new_inode_pseudo+0xf/0x48 new_inode+0x15/0x25 tracefs_get_inode+0x23/0x7c ? lookup_one_len+0x54/0x6c tracefs_create_file+0x53/0x11d trace_create_file+0x15/0x33 event_create_dir+0x2a3/0x34b __trace_add_new_event+0x1c/0x26 event_trace_add_tracer+0x56/0x86 trace_array_create+0x13e/0x1e1 instance_mkdir+0x8/0x17 tracefs_syscall_mkdir+0x39/0x50 ? get_dname+0x31/0x31 vfs_mkdir+0x78/0xa3 do_mkdirat+0x71/0xb0 sys_mkdir+0x19/0x1b do_fast_syscall_32+0xb0/0xed I bisected this down to the addition of the proxy_ops into tracefs for lockdown. It appears that the allocation of the proxy_ops and then freeing it in the destroy_inode callback, is causing havoc with the memory system. Reading the documentation about destroy_inode and talking with Linus about this, this is buggy and wrong. When defining the destroy_inode() method, it is expected that the destroy_inode() will also free the inode, and not just the extra allocations done in the creation of the inode. The faulty commit causes a memory leak of the inode data structure when they are deleted. Instead of allocating the proxy_ops (and then having to free it) the checks should be done by the open functions themselves, and not hack into the tracefs directory. First revert the tracefs updates for locked_down and then later we can add the locked_down checks in the kernel/trace files. Link: http://lkml.kernel.org/r/20191011135458.7399da44@gandalf.local.home Fixes: ccbd54ff54e8 ("tracefs: Restrict tracefs when the kernel is locked down") Suggested-by: Linus Torvalds <torvalds@linux-foundation.org> Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org> | 13 October 2019, 00:36:50 UTC |
da94001 | Linus Torvalds | 12 October 2019, 22:47:19 UTC | Merge tag 'char-misc-5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc Pull char/misc driver fixes from Greg KH: "Here are some small char/misc driver fixes for 5.4-rc3. Nothing huge here. Some binder driver fixes (although it is still being discussed if these all fix the reported issues or not, so more might be coming later), some mei device ids and fixes, and a google firmware driver bugfix that fixes a regression, as well as some other tiny fixes. All have been in linux-next with no reported issues" * tag 'char-misc-5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc: firmware: google: increment VPD key_len properly w1: ds250x: Fix build error without CRC16 virt: vbox: fix memory leak in hgcm_call_preprocess_linaddr binder: Fix comment headers on binder_alloc_prepare_to_free() binder: prevent UAF read in print_binder_transaction_log_entry() misc: fastrpc: prevent memory leak in fastrpc_dma_buf_attach mei: avoid FW version request on Ibex Peak and earlier mei: me: add comet point (lake) LP device ids | 12 October 2019, 22:47:19 UTC |
9cbc634 | Linus Torvalds | 12 October 2019, 22:44:46 UTC | Merge tag 'staging-5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging Pull staging/IIO driver fixes from Greg KH: "Here are some staging and IIO driver fixes for 5.4-rc3. The "biggest" thing here is a removal of the fbtft device and flexfb code as they have been abandoned by their authors and are no longer needed for that hardware. Other than that, the usual amount of staging driver and iio driver fixes for reported issues, and some speakup sysfs file documentation, which has been long awaited for. All have been in linux-next with no reported issues" * tag 'staging-5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging: (32 commits) iio: Fix an undefied reference error in noa1305_probe iio: light: opt3001: fix mutex unlock race iio: adc: ad799x: fix probe error handling iio: light: add missing vcnl4040 of_compatible iio: light: fix vcnl4000 devicetree hooks iio: imu: st_lsm6dsx: fix waitime for st_lsm6dsx i2c controller iio: adc: axp288: Override TS pin bias current for some models iio: imu: adis16400: fix memory leak iio: imu: adis16400: release allocated memory on failure iio: adc: stm32-adc: fix a race when using several adcs with dma and irq iio: adc: stm32-adc: move registers definitions iio: accel: adxl372: Perform a reset at start up iio: accel: adxl372: Fix push to buffers lost samples iio: accel: adxl372: Fix/remove limitation for FIFO samples iio: adc: hx711: fix bug in sampling of data staging: vt6655: Fix memory leak in vt6655_probe staging: exfat: Use kvzalloc() instead of kzalloc() for exfat_sb_info Staging: fbtft: fix memory leak in fbtft_framebuffer_alloc staging: speakup: document sysfs attributes staging: rtl8188eu: fix HighestRate check in odm_ARFBRefresh_8188E() ... | 12 October 2019, 22:44:46 UTC |
82c87e7 | Linus Torvalds | 12 October 2019, 22:42:19 UTC | Merge tag 'tty-5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty Pull tty/serial driver fixes from Greg KH: "Here are some small tty and serial driver fixes for 5.4-rc3 that resolve a number of reported issues and regressions. None of these are huge, full details are in the shortlog. There's also a MAINTAINERS update that I think you might have already taken in your tree already, but git should handle that merge easily. All have been in linux-next with no reported issues" * tag 'tty-5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty: MAINTAINERS: kgdb: Add myself as a reviewer for kgdb/kdb tty: serial: imx: Use platform_get_irq_optional() for optional IRQs serial: fix kernel-doc warning in comments serial: 8250_omap: Fix gpio check for auto RTS/CTS serial: mctrl_gpio: Check for NULL pointer tty: serial: fsl_lpuart: Fix lpuart_flush_buffer() tty: serial: Fix PORT_LINFLEXUART definition tty: n_hdlc: fix build on SPARC serial: uartps: Fix uartps_major handling serial: uartlite: fix exit path null pointer tty: serial: linflexuart: Fix magic SysRq handling serial: sh-sci: Use platform_get_irq_optional() for optional interrupts dt-bindings: serial: sh-sci: Document r8a774b1 bindings serial/sifive: select SERIAL_EARLYCON tty: serial: rda: Fix the link time qualifier of 'rda_uart_exit()' tty: serial: owl: Fix the link time qualifier of 'owl_uart_exit()' | 12 October 2019, 22:42:19 UTC |
6c90bbd | Linus Torvalds | 12 October 2019, 22:37:12 UTC | Merge tag 'usb-5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb Pull USB fixes from Greg KH: "Here are a lot of small USB driver fixes for 5.4-rc3. syzbot has stepped up its testing of the USB driver stack, now able to trigger fun race conditions between disconnect and probe functions. Because of that we have a lot of fixes in here from Johan and others fixing these reported issues that have been around since almost all time. We also are just deleting the rio500 driver, making all of the syzbot bugs found in it moot as it turns out no one has been using it for years as there is a userspace version that is being used instead. There are also a number of other small fixes in here, all resolving reported issues or regressions. All have been in linux-next without any reported issues" * tag 'usb-5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb: (65 commits) USB: yurex: fix NULL-derefs on disconnect USB: iowarrior: use pr_err() USB: iowarrior: drop redundant iowarrior mutex USB: iowarrior: drop redundant disconnect mutex USB: iowarrior: fix use-after-free after driver unbind USB: iowarrior: fix use-after-free on release USB: iowarrior: fix use-after-free on disconnect USB: chaoskey: fix use-after-free on release USB: adutux: fix use-after-free on release USB: ldusb: fix NULL-derefs on driver unbind USB: legousbtower: fix use-after-free on release usb: cdns3: Fix for incorrect DMA mask. usb: cdns3: fix cdns3_core_init_role() usb: cdns3: gadget: Fix full-speed mode USB: usb-skeleton: drop redundant in-urb check USB: usb-skeleton: fix use-after-free after driver unbind USB: usb-skeleton: fix NULL-deref on disconnect usb:cdns3: Fix for CV CH9 running with g_zero driver. usb: dwc3: Remove dev_err() on platform_get_irq() failure usb: dwc3: Switch to platform_get_irq_byname_optional() ... | 12 October 2019, 22:37:12 UTC |
328fefa | Linus Torvalds | 12 October 2019, 22:29:54 UTC | Merge branch 'sched-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip Pull scheduler fixes from Ingo Molnar: "Two fixes: a guest-cputime accounting fix, and a cgroup bandwidth quota precision fix" * 'sched-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: sched/vtime: Fix guest/system mis-accounting on task switch sched/fair: Scale bandwidth quota and period without losing quota/period ratio precision | 12 October 2019, 22:29:54 UTC |
465a7e2 | Linus Torvalds | 12 October 2019, 22:15:17 UTC | Merge branch 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip Pull perf fixes from Ingo Molnar: "Mostly tooling fixes, but also a couple of updates for new Intel models (which are technically hw-enablement, but to users it's a fix to perf behavior on those new CPUs - hope this is fine), an AUX inheritance fix, event time-sharing fix, and a fix for lost non-perf NMI events on AMD systems" * 'perf-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (36 commits) perf/x86/cstate: Add Tiger Lake CPU support perf/x86/msr: Add Tiger Lake CPU support perf/x86/intel: Add Tiger Lake CPU support perf/x86/cstate: Update C-state counters for Ice Lake perf/x86/msr: Add new CPU model numbers for Ice Lake perf/x86/cstate: Add Comet Lake CPU support perf/x86/msr: Add Comet Lake CPU support perf/x86/intel: Add Comet Lake CPU support perf/x86/amd: Change/fix NMI latency mitigation to use a timestamp perf/core: Fix corner case in perf_rotate_context() perf/core: Rework memory accounting in perf_mmap() perf/core: Fix inheritance of aux_output groups perf annotate: Don't return -1 for error when doing BPF disassembly perf annotate: Return appropriate error code for allocation failures perf annotate: Fix arch specific ->init() failure errors perf annotate: Propagate the symbol__annotate() error return perf annotate: Fix the signedness of failure returns perf annotate: Propagate perf_env__arch() error perf evsel: Fall back to global 'perf_env' in perf_evsel__env() perf tools: Propagate get_cpuid() error ... | 12 October 2019, 22:15:17 UTC |
9b4e40c | Linus Torvalds | 12 October 2019, 22:08:24 UTC | Merge branch 'efi-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip Pull EFI fixes from Ingo Molnar: "Misc EFI fixes all across the map: CPER error report fixes, fixes to TPM event log parsing, fix for a kexec hang, a Sparse fix and other fixes" * 'efi-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: efi/tpm: Fix sanity check of unsigned tbl_size being less than zero efi/x86: Do not clean dummy variable in kexec path efi: Make unexported efi_rci2_sysfs_init() static efi/tpm: Only set 'efi_tpm_final_log_size' after successful event log parsing efi/tpm: Don't traverse an event log with no events efi/tpm: Don't access event->count when it isn't mapped efivar/ssdt: Don't iterate over EFI vars if no SSDT override was specified efi/cper: Fix endianness of PCIe class code | 12 October 2019, 22:08:24 UTC |
fcb45a2 | Linus Torvalds | 12 October 2019, 21:46:14 UTC | Merge branch 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip Pull x86 fixes from Ingo Molnar: "A handful of fixes: a kexec linking fix, an AMD MWAITX fix, a vmware guest support fix when built under Clang, and new CPU model number definitions" * 'x86-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: x86/cpu: Add Comet Lake to the Intel CPU models header lib/string: Make memzero_explicit() inline instead of external x86/cpu/vmware: Use the full form of INL in VMWARE_PORT x86/asm: Fix MWAITX C-state hint value | 12 October 2019, 21:46:14 UTC |
e9ec358 | Linus Torvalds | 12 October 2019, 21:37:55 UTC | Merge branch 'core-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip Pull x86 license tag fixlets from Ingo Molnar: "Fix a couple of SPDX tags in x86 headers to follow the canonical pattern" * 'core-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: x86: Use the correct SPDX License Identifier in headers | 12 October 2019, 21:37:55 UTC |
48acba9 | Linus Torvalds | 12 October 2019, 21:25:38 UTC | Merge tag 'riscv/for-v5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux Pull RISC-V fixes from Paul Walmsley: - Fix several bugs in the breakpoint trap handler - Drop an unnecessary loop around calls to preempt_schedule_irq() * tag 'riscv/for-v5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux: RISC-V: entry: Remove unneeded need_resched() loop riscv: Correct the handling of unexpected ebreak in do_trap_break() riscv: avoid sending a SIGTRAP to a user thread trapped in WARN() riscv: avoid kernel hangs when trapped in BUG() | 12 October 2019, 21:25:38 UTC |
63f9bff | Linus Torvalds | 12 October 2019, 21:16:51 UTC | Merge tag 'mips_fixes_5.4_2' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux Pull MIPS fixes from Paul Burton: - Build fixes for CONFIG_OPTIMIZE_INLINING=y builds in which the compiler may choose not to inline __xchg() & __cmpxchg(). - A build fix for Loongson configurations with GCC 9.x. - Expose some extra HWCAP bits to indicate support for various instruction set extensions to userland. - Fix bad stack access in firmware handling code for old SNI RM200/300/400 machines. * tag 'mips_fixes_5.4_2' of git://git.kernel.org/pub/scm/linux/kernel/git/mips/linux: MIPS: Disable Loongson MMI instructions for kernel build MIPS: elf_hwcap: Export userspace ASEs MIPS: fw: sni: Fix out of bounds init of o32 stack MIPS: include: Mark __xchg as __always_inline MIPS: include: Mark __cmpxchg as __always_inline | 12 October 2019, 21:16:51 UTC |
db60a5a | Linus Torvalds | 12 October 2019, 21:13:55 UTC | Merge tag 'powerpc-5.4-3' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux Pull powerpc fixes from Michael Ellerman: "Fix a kernel crash in spufs_create_root() on Cell machines, since the new mount API went in. Fix a regression in our KVM code caused by our recent PCR changes. Avoid a warning message about a failing hypervisor API on systems that don't have that API. A couple of minor build fixes. Thanks to: Alexey Kardashevskiy, Alistair Popple, Desnes A. Nunes do Rosario, Emmanuel Nicolet, Jordan Niethe, Laurent Dufour, Stephen Rothwell" * tag 'powerpc-5.4-3' of git://git.kernel.org/pub/scm/linux/kernel/git/powerpc/linux: spufs: fix a crash in spufs_create_root() powerpc/kvm: Fix kvmppc_vcore->in_guest value in kvmhv_switch_to_host selftests/powerpc: Fix compile error on tlbie_test due to newer gcc powerpc/pseries: Remove confusing warning message. powerpc/64s/radix: Fix build failure with RADIX_MMU=n | 12 October 2019, 21:13:55 UTC |
680b5b3 | Linus Torvalds | 12 October 2019, 21:11:21 UTC | Merge tag 'for-linus-5.4-rc3-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip Pull xen fixes from Juergen Gross: - correct panic handling when running as a Xen guest - cleanup the Xen grant driver to remove printing a pointer being always NULL - remove a soon to be wrong call of of_dma_configure() * tag 'for-linus-5.4-rc3-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip: xen: Stop abusing DT of_dma_configure API xen/grant-table: remove unnecessary printing x86/xen: Return from panic notifier | 12 October 2019, 21:11:21 UTC |
f154988 | Linus Torvalds | 12 October 2019, 21:09:31 UTC | Merge tag 's390-5.4-4' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux Pull s390 fixes from Vasily Gorbik: - Fix virtio-ccw DMA regression - Fix compiler warnings in uaccess * tag 's390-5.4-4' of git://git.kernel.org/pub/scm/linux/kernel/git/s390/linux: s390/uaccess: avoid (false positive) compiler warnings s390/cio: fix virtio-ccw DMA without PV | 12 October 2019, 21:09:31 UTC |
52e92f4 | Kan Liang | 08 October 2019, 15:50:10 UTC | perf/x86/cstate: Add Tiger Lake CPU support Tiger Lake is the followon to Ice Lake. From the perspective of Intel cstate residency counters, there is nothing changed compared with Ice Lake. Share icl_cstates with Ice Lake. Update the comments for Tiger Lake. The External Design Specification (EDS) is not published yet. It comes from an authoritative internal source. The patch has been tested on real hardware. Signed-off-by: Kan Liang <kan.liang@linux.intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: https://lkml.kernel.org/r/1570549810-25049-10-git-send-email-kan.liang@linux.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org> | 12 October 2019, 13:13:09 UTC |
0917b95 | Kan Liang | 08 October 2019, 15:50:09 UTC | perf/x86/msr: Add Tiger Lake CPU support Tiger Lake is the followon to Ice Lake. PPERF and SMI_COUNT MSRs are also supported. The External Design Specification (EDS) is not published yet. It comes from an authoritative internal source. The patch has been tested on real hardware. Signed-off-by: Kan Liang <kan.liang@linux.intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: https://lkml.kernel.org/r/1570549810-25049-9-git-send-email-kan.liang@linux.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org> | 12 October 2019, 13:13:09 UTC |
23645a7 | Kan Liang | 08 October 2019, 15:50:08 UTC | perf/x86/intel: Add Tiger Lake CPU support Tiger Lake is the followon to Ice Lake. From the perspective of Intel core PMU, there is little changes compared with Ice Lake, e.g. small changes in event list. But it doesn't impact on core PMU functionality. Share the perf code with Ice Lake. The event list patch will be submitted later separately. The patch has been tested on real hardware. Signed-off-by: Kan Liang <kan.liang@linux.intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: https://lkml.kernel.org/r/1570549810-25049-8-git-send-email-kan.liang@linux.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org> | 12 October 2019, 13:13:09 UTC |
f1857a2 | Kan Liang | 08 October 2019, 15:50:07 UTC | perf/x86/cstate: Update C-state counters for Ice Lake There is no Core C3 C-State counter for Ice Lake. Package C8/C9/C10 C-State counters are added for Ice Lake. Introduce a new event list, icl_cstates, for Ice Lake. Update the comments accordingly. Signed-off-by: Kan Liang <kan.liang@linux.intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Fixes: f08c47d1f86c ("perf/x86/intel/cstate: Add Icelake support") Link: https://lkml.kernel.org/r/1570549810-25049-7-git-send-email-kan.liang@linux.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org> | 12 October 2019, 13:13:09 UTC |
1a5da78 | Kan Liang | 08 October 2019, 15:50:06 UTC | perf/x86/msr: Add new CPU model numbers for Ice Lake PPERF and SMI_COUNT MSRs are also supported by Ice Lake desktop and server. Signed-off-by: Kan Liang <kan.liang@linux.intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: https://lkml.kernel.org/r/1570549810-25049-6-git-send-email-kan.liang@linux.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org> | 12 October 2019, 13:13:09 UTC |
1ffa6c0 | Kan Liang | 08 October 2019, 15:50:05 UTC | perf/x86/cstate: Add Comet Lake CPU support Comet Lake is the new 10th Gen Intel processor. From the perspective of Intel cstate residency counters, there is nothing changed compared with Kaby Lake. Share hswult_cstates with Kaby Lake. Update the comments for Comet Lake. Kaby Lake is missed in the comments for some Residency Counters. Update the comments for Kaby Lake as well. The External Design Specification (EDS) is not published yet. It comes from an authoritative internal source. The patch has been tested on real hardware. Signed-off-by: Kan Liang <kan.liang@linux.intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: https://lkml.kernel.org/r/1570549810-25049-5-git-send-email-kan.liang@linux.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org> | 12 October 2019, 13:13:08 UTC |
9674b1c | Kan Liang | 08 October 2019, 15:50:04 UTC | perf/x86/msr: Add Comet Lake CPU support Comet Lake is the new 10th Gen Intel processor. PPERF and SMI_COUNT MSRs are also supported. The External Design Specification (EDS) is not published yet. It comes from an authoritative internal source. The patch has been tested on real hardware. Signed-off-by: Kan Liang <kan.liang@linux.intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: https://lkml.kernel.org/r/1570549810-25049-4-git-send-email-kan.liang@linux.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org> | 12 October 2019, 13:13:08 UTC |
9066288 | Kan Liang | 08 October 2019, 15:50:03 UTC | perf/x86/intel: Add Comet Lake CPU support Comet Lake is the new 10th Gen Intel processor. From the perspective of Intel PMU, there is nothing changed compared with Sky Lake. Share the perf code with Sky Lake. The patch has been tested on real hardware. Signed-off-by: Kan Liang <kan.liang@linux.intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Link: https://lkml.kernel.org/r/1570549810-25049-3-git-send-email-kan.liang@linux.intel.com Signed-off-by: Ingo Molnar <mingo@kernel.org> | 12 October 2019, 13:13:08 UTC |
7a275fd | Ingo Molnar | 12 October 2019, 13:12:21 UTC | Merge branch 'x86/urgent' into perf/urgent, to pick up new CPU model definitions Signed-off-by: Ingo Molnar <mingo@kernel.org> | 12 October 2019, 13:12:21 UTC |
1c0cc5f | Linus Torvalds | 11 October 2019, 21:28:59 UTC | Merge tag 'nfs-for-5.4-2' of git://git.linux-nfs.org/projects/anna/linux-nfs Pull NFS client bugfixes from Anna Schumaker: "Stable bugfixes: - Fix O_DIRECT accounting of number of bytes read/written # v4.1+ Other fixes: - Fix nfsi->nrequests count error on nfs_inode_remove_request() - Remove redundant mirror tracking in O_DIRECT - Fix leak of clp->cl_acceptor string - Fix race to sk_err after xs_error_report" * tag 'nfs-for-5.4-2' of git://git.linux-nfs.org/projects/anna/linux-nfs: SUNRPC: fix race to sk_err after xs_error_report NFSv4: Fix leak of clp->cl_acceptor string NFS: Remove redundant mirror tracking in O_DIRECT NFS: Fix O_DIRECT accounting of number of bytes read/written nfs: Fix nfsi->nrequests count error on nfs_inode_remove_request | 11 October 2019, 21:28:59 UTC |
c6ad7c3 | Linus Torvalds | 11 October 2019, 21:01:13 UTC | Merge tag '5.4-rc2-smb3' of git://git.samba.org/sfrench/cifs-2.6 Pull cifs fixes from Steve French: "Eight small SMB3 fixes, four for stable, and important fix for the recent regression introduced by filesystem timestamp range patches" * tag '5.4-rc2-smb3' of git://git.samba.org/sfrench/cifs-2.6: CIFS: Force reval dentry if LOOKUP_REVAL flag is set CIFS: Force revalidate inode when dentry is stale smb3: Fix regression in time handling smb3: remove noisy debug message and minor cleanup CIFS: Gracefully handle QueryInfo errors during open cifs: use cifsInodeInfo->open_file_lock while iterating to avoid a panic fs: cifs: mute -Wunused-const-variable message smb3: cleanup some recent endian errors spotted by updated sparse | 11 October 2019, 21:01:13 UTC |
c6f6ebd | Linus Torvalds | 11 October 2019, 17:19:24 UTC | Merge tag 'modules-for-v5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux Pull module fixes from Jessica Yu: "Code cleanups and kbuild/namespace related fixups from Masahiro. Most importantly, it fixes a namespace-related modpost issue for external module builds - Fix broken external module builds due to a modpost bug in read_dump(), where the namespace was not being strdup'd and sym->namespace would be set to bogus data. - Various namespace-related kbuild fixes and cleanups thanks to Masahiro Yamada" * tag 'modules-for-v5.4-rc3' of git://git.kernel.org/pub/scm/linux/kernel/git/jeyu/linux: doc: move namespaces.rst from kbuild/ to core-api/ nsdeps: make generated patches independent of locale nsdeps: fix hashbang of scripts/nsdeps kbuild: fix build error of 'make nsdeps' in clean tree module: rename __kstrtab_ns_* to __kstrtabns_* to avoid symbol conflict modpost: fix broken sym->namespace for external module builds module: swap the order of symbol.namespace scripts: add_namespace: Fix coccicheck failed | 11 October 2019, 17:19:24 UTC |
56c642e | Linus Torvalds | 11 October 2019, 17:12:45 UTC | Merge tag 'hyperv-fixes-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux Pull Hyper-V fixes from Sasha Levin: "Two fixes from Dexuan Cui: - Fix a (harmless) warning when building vmbus without CONFIG_PM_SLEEP - Fix for a memory leak (and optimization) in the hyperv mouse code" * tag 'hyperv-fixes-signed' of git://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux: Drivers: hv: vmbus: Fix harmless building warnings without CONFIG_PM_SLEEP HID: hyperv: Use in-place iterator API in the channel callback | 11 October 2019, 17:12:45 UTC |
b9918bd | Joe Perches | 05 October 2019, 16:46:43 UTC | Documentation/process: Add fallthrough pseudo-keyword Describe the fallthrough pseudo-keyword. Convert the coding-style.rst example to the keyword style. Add description and links to deprecated.rst. Miguel Ojeda comments on the eventual [[fallthrough]] syntax: "Note that C17/C18 does not have [[fallthrough]]. C++17 introduced it, as it is mentioned above. I would keep the __attribute__((fallthrough)) -> [[fallthrough]] change you did, though, since that is indeed the standard syntax (given the paragraph references C++17). I was told by Aaron Ballman (who is proposing them for C) that it is more or less likely that it becomes standardized in C2x. However, it is still not added to the draft (other attributes are already, though). See N2268 and N2269: http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2268.pdf (fallthrough) http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2269.pdf (attributes in general)" Signed-off-by: Joe Perches <joe@perches.com> Acked-by: Nick Desaulniers <ndesaulniers@google.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> | 11 October 2019, 16:26:05 UTC |
294f69e | Joe Perches | 05 October 2019, 16:46:42 UTC | compiler_attributes.h: Add 'fallthrough' pseudo keyword for switch/case use Reserve the pseudo keyword 'fallthrough' for the ability to convert the various case block /* fallthrough */ style comments to appear to be an actual reserved word with the same gcc case block missing fallthrough warning capability. All switch/case blocks now should end in one of: break; fallthrough; goto <label>; return [expression]; continue; In C mode, GCC supports the __fallthrough__ attribute since 7.1, the same time the warning and the comment parsing were introduced. fallthrough devolves to an empty "do {} while (0)" if the compiler version (any version less than gcc 7) does not support the attribute. Signed-off-by: Joe Perches <joe@perches.com> Acked-by: Peter Zijlstra (Intel) <peterz@infradead.org> Suggested-by: Dan Carpenter <dan.carpenter@oracle.com> Cc: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> | 11 October 2019, 16:26:05 UTC |
48f9bcf | Joe Perches | 05 October 2019, 16:46:41 UTC | net: sctp: Rename fallthrough label to unhandled fallthrough will become a pseudo reserved keyword so this only use of fallthrough is better renamed to allow it. Signed-off-by: Joe Perches <joe@perches.com> Reviewed-by: Nick Desaulniers <ndesaulniers@google.com> Reviewed-by: Kees Cook <keescook@chromium.org> Acked-by: Neil Horman <nhorman@tuxdriver.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> | 11 October 2019, 16:26:05 UTC |
9892f9f | Linus Torvalds | 11 October 2019, 16:02:33 UTC | Merge tag 'drm-fixes-2019-10-11' of git://anongit.freedesktop.org/drm/drm Pull drm fixes from Dave Airlie: "The regular fixes pull for rc3. The i915 team found some fixes they (or I) missed for rc1, which is why this is a bit bigger than usual, otherwise there is a single amdgpu fix, some spi panel aliases, and a bridge fix. i915: - execlist access fixes - list deletion fix - CML display fix - HSW workaround extension to GT2 - chicken bit whitelist - GGTT resume issue - SKL GPU hangs for Vulkan compute amdgpu: - memory leak fix panel: - spi aliases tc358767: - bridge artifacts fix" * tag 'drm-fixes-2019-10-11' of git://anongit.freedesktop.org/drm/drm: (22 commits) drm/bridge: tc358767: fix max_tu_symbol value drm/i915/gt: execlists->active is serialised by the tasklet drm/i915/execlists: Protect peeking at execlists->active drm/i915: Fixup preempt-to-busy vs reset of a virtual request drm/i915: Only enqueue already completed requests drm/i915/execlists: Drop redundant list_del_init(&rq->sched.link) drm/i915/cml: Add second PCH ID for CMP drm/amdgpu: fix memory leak drm/panel: tpo-td043mtea1: Fix SPI alias drm/panel: tpo-td028ttec1: Fix SPI alias drm/panel: sony-acx565akm: Fix SPI alias drm/panel: nec-nl8048hl11: Fix SPI alias drm/panel: lg-lb035q02: Fix SPI alias drm/i915: Mark contents as dirty on a write fault drm/i915: Prevent bonded requests from overtaking each other on preemption drm/i915: Bump skl+ max plane width to 5k for linear/x-tiled drm/i915: Verify the engine after acquiring the active.lock drm/i915: Extend Haswell GT1 PSMI workaround to all drm/i915: Don't mix srcu tag and negative error codes drm/i915: Whitelist COMMON_SLICE_CHICKEN2 ... | 11 October 2019, 16:02:33 UTC |
297cbcc | Linus Torvalds | 11 October 2019, 15:45:32 UTC | Merge tag 'for-linus-20191010' of git://git.kernel.dk/linux-block Pull block fixes from Jens Axboe: - Fix wbt performance regression introduced with the blk-rq-qos refactoring (Harshad) - Fix io_uring fileset removal inadvertently killing the workqueue (me) - Fix io_uring typo in linked command nonblock submission (Pavel) - Remove spurious io_uring wakeups on request free (Pavel) - Fix null_blk zoned command error return (Keith) - Don't use freezable workqueues for backing_dev, also means we can revert a previous libata hack (Mika) - Fix nbd sysfs mutex dropped too soon at removal time (Xiubo) * tag 'for-linus-20191010' of git://git.kernel.dk/linux-block: nbd: fix possible sysfs duplicate warning null_blk: Fix zoned command return code io_uring: only flush workqueues on fileset removal io_uring: remove wait loop spurious wakeups blk-wbt: fix performance regression in wbt scale_up/scale_down Revert "libata, freezer: avoid block device removal while system is frozen" bdi: Do not use freezable workqueue io_uring: fix reversed nonblock flag for link submission | 11 October 2019, 15:45:32 UTC |
062795f | Christian Borntraeger | 08 October 2019, 15:02:32 UTC | s390/uaccess: avoid (false positive) compiler warnings Depending on inlining decisions by the compiler, __get/put_user_fn might become out of line. Then the compiler is no longer able to tell that size can only be 1,2,4 or 8 due to the check in __get/put_user resulting in false positives like ./arch/s390/include/asm/uaccess.h: In function ‘__put_user_fn’: ./arch/s390/include/asm/uaccess.h:113:9: warning: ‘rc’ may be used uninitialized in this function [-Wmaybe-uninitialized] 113 | return rc; | ^~ ./arch/s390/include/asm/uaccess.h: In function ‘__get_user_fn’: ./arch/s390/include/asm/uaccess.h:143:9: warning: ‘rc’ may be used uninitialized in this function [-Wmaybe-uninitialized] 143 | return rc; | ^~ These functions are supposed to be always inlined. Mark it as such. Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com> Signed-off-by: Vasily Gorbik <gor@linux.ibm.com> | 11 October 2019, 10:27:25 UTC |
442f1e7 | Brian Norris | 30 September 2019, 21:45:22 UTC | firmware: google: increment VPD key_len properly Commit 4b708b7b1a2c ("firmware: google: check if size is valid when decoding VPD data") adds length checks, but the new vpd_decode_entry() function botched the logic -- it adds the key length twice, instead of adding the key and value lengths separately. On my local system, this means vpd.c's vpd_section_create_attribs() hits an error case after the first attribute it parses, since it's no longer looking at the correct offset. With this patch, I'm back to seeing all the correct attributes in /sys/firmware/vpd/... Fixes: 4b708b7b1a2c ("firmware: google: check if size is valid when decoding VPD data") Cc: <stable@vger.kernel.org> Cc: Hung-Te Lin <hungte@chromium.org> Signed-off-by: Brian Norris <briannorris@chromium.org> Reviewed-by: Stephen Boyd <swboyd@chromium.org> Reviewed-by: Guenter Roeck <groeck@chromium.org> Link: https://lore.kernel.org/r/20190930214522.240680-1-briannorris@chromium.org Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 11 October 2019, 06:41:34 UTC |
10deeac | Douglas Anderson | 20 September 2019, 17:44:47 UTC | MAINTAINERS: kgdb: Add myself as a reviewer for kgdb/kdb I'm interested in kdb / kgdb and have sent various fixes over the years. I'd like to get CCed on patches so I can be aware of them and also help review. Signed-off-by: Douglas Anderson <dianders@chromium.org> Acked-by: Daniel Thompson <daniel.thompson@linaro.org> Link: https://lore.kernel.org/r/20190920104404.1.I237e68e8825e2d6ac26f8e847f521fe2fcc3705a@changeid Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 11 October 2019, 06:40:29 UTC |
2272905 | Emmanuel Nicolet | 08 October 2019, 14:13:42 UTC | spufs: fix a crash in spufs_create_root() The spu_fs_context was not set in fc->fs_private, this caused a crash when accessing ctx->mode in spufs_create_root(). Fixes: d2e0981c3b9a ("vfs: Convert spufs to use the new mount API") Signed-off-by: Emmanuel Nicolet <emmanuel.nicolet@gmail.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Acked-by: Arnd Bergmann <arnd@arndb.de> Link: https://lore.kernel.org/r/20191008141342.GA266797@gmail.com | 11 October 2019, 05:57:41 UTC |
7adf4ea | Jens Axboe | 11 October 2019, 03:42:58 UTC | io_uring: fix sequence logic for timeout requests We have two ways a request can be deferred: 1) It's a regular request that depends on another one 2) It's a timeout that tracks completions We have a shared helper to determine whether to defer, and that attempts to make the right decision based on the request. But we only have some of this information in the caller. Un-share the two timeout/defer helpers so the caller can use the right one. Fixes: 5262f567987d ("io_uring: IORING_OP_TIMEOUT support") Reported-by: yangerkun <yangerkun@huawei.com> Reviewed-by: Jackie Liu <liuyun01@kylinos.cn> Signed-off-by: Jens Axboe <axboe@kernel.dk> | 11 October 2019, 03:42:58 UTC |
4adbcff | Dave Airlie | 11 October 2019, 00:09:01 UTC | Merge tag 'drm-intel-fixes-2019-10-10' of git://anongit.freedesktop.org/drm/drm-intel into drm-fixes - Fix CML display by adding a missing ID. - Drop redundant list_del_init - Only enqueue already completed requests to avoid races - Fixup preempt-to-busy vs reset of a virtual request - Protect peeking at execlists->active - execlists->active is serialised by the tasklet drm-intel-next-fixes-2019-09-19: - Extend old HSW workaround to fix some GPU hangs on Haswell GT2 - Fix return error code on GEM mmap. - White list a chicken bit register for push constants legacy mode on Mesa - Fix resume issue related to GGTT restore - Remove incorrect BUG_ON on execlist's schedule-out - Fix unrecoverable GPU hangs with Vulkan compute workloads on SKL drm-intel-next-fixes-2019-09-26: - Fix concurrence on cases where requests where getting retired at same time as resubmitted to HW - Fix gen9 display resolutions by setting the right max plane width - Fix GPU hang on preemption - Mark contents as dirty on a write fault. This was breaking cursor sprite with dumb buffers. Signed-off-by: Dave Airlie <airlied@redhat.com> From: Rodrigo Vivi <rodrigo.vivi@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20191010143039.GA15313@intel.com | 11 October 2019, 00:09:15 UTC |
46fe219 | Dave Airlie | 11 October 2019, 00:08:32 UTC | Merge tag 'drm-fixes-5.4-2019-10-09' of git://people.freedesktop.org/~agd5f/linux into drm-fixes drm-fixes-5.4-2019-10-09: amdgpu: - fix memory leak in bo_list ioctl error path Signed-off-by: Dave Airlie <airlied@redhat.com> From: Alex Deucher <alexdeucher@gmail.com> Link: https://patchwork.freedesktop.org/patch/msgid/20191010031023.23359-1-alexander.deucher@amd.com | 11 October 2019, 00:08:33 UTC |
437c5a1 | Dave Airlie | 11 October 2019, 00:08:02 UTC | Merge tag 'drm-misc-fixes-2019-10-10' of git://anongit.freedesktop.org/drm/drm-misc into drm-fixes Short summary of fixes pull (less than what git shortlog provides): - SPI Aliases fixes for panels - One fix for the tc358767 bridge dealing with visual artifacts Signed-off-by: Dave Airlie <airlied@redhat.com> From: Maxime Ripard <mripard@kernel.org> Link: https://patchwork.freedesktop.org/patch/msgid/20191010105137.j6juxht5dsobgxph@gilmour | 11 October 2019, 00:08:14 UTC |
af84537 | Benjamin Coddington | 02 October 2019, 14:40:55 UTC | SUNRPC: fix race to sk_err after xs_error_report Since commit 4f8943f80883 ("SUNRPC: Replace direct task wakeups from softirq context") there has been a race to the value of the sk_err if both XPRT_SOCK_WAKE_ERROR and XPRT_SOCK_WAKE_DISCONNECT are set. In that case, we may end up losing the sk_err value that existed when xs_error_report was called. Fix this by reverting to the previous behavior: instead of using SO_ERROR to retrieve the value at a later time (which might also return sk_err_soft), copy the sk_err value onto struct sock_xprt, and use that value to wake pending tasks. Signed-off-by: Benjamin Coddington <bcodding@redhat.com> Fixes: 4f8943f80883 ("SUNRPC: Replace direct task wakeups from softirq context") Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com> | 10 October 2019, 20:14:28 UTC |
1047ec8 | Chuck Lever | 04 October 2019, 13:58:54 UTC | NFSv4: Fix leak of clp->cl_acceptor string Our client can issue multiple SETCLIENTID operations to the same server in some circumstances. Ensure that calls to nfs4_proc_setclientid() after the first one do not overwrite the previously allocated cl_acceptor string. unreferenced object 0xffff888461031800 (size 32): comm "mount.nfs", pid 2227, jiffies 4294822467 (age 1407.749s) hex dump (first 32 bytes): 6e 66 73 40 6b 6c 69 6d 74 2e 69 62 2e 31 30 31 nfs@klimt.ib.101 35 67 72 61 6e 67 65 72 2e 6e 65 74 00 00 00 00 5granger.net.... backtrace: [<00000000ab820188>] __kmalloc+0x128/0x176 [<00000000eeaf4ec8>] gss_stringify_acceptor+0xbd/0x1a7 [auth_rpcgss] [<00000000e85e3382>] nfs4_proc_setclientid+0x34e/0x46c [nfsv4] [<000000003d9cf1fa>] nfs40_discover_server_trunking+0x7a/0xed [nfsv4] [<00000000b81c3787>] nfs4_discover_server_trunking+0x81/0x244 [nfsv4] [<000000000801b55f>] nfs4_init_client+0x1b0/0x238 [nfsv4] [<00000000977daf7f>] nfs4_set_client+0xfe/0x14d [nfsv4] [<0000000053a68a2a>] nfs4_create_server+0x107/0x1db [nfsv4] [<0000000088262019>] nfs4_remote_mount+0x2c/0x59 [nfsv4] [<00000000e84a2fd0>] legacy_get_tree+0x2d/0x4c [<00000000797e947c>] vfs_get_tree+0x20/0xc7 [<00000000ecabaaa8>] fc_mount+0xe/0x36 [<00000000f15fafc2>] vfs_kern_mount+0x74/0x8d [<00000000a3ff4e26>] nfs_do_root_mount+0x8a/0xa3 [nfsv4] [<00000000d1c2b337>] nfs4_try_mount+0x58/0xad [nfsv4] [<000000004c9bddee>] nfs_fs_mount+0x820/0x869 [nfs] Fixes: f11b2a1cfbf5 ("nfs4: copy acceptor name from context ... ") Signed-off-by: Chuck Lever <chuck.lever@oracle.com> Signed-off-by: Anna Schumaker <Anna.Schumaker@Netapp.com> | 10 October 2019, 20:14:02 UTC |
2f2b4fd | Paul Burton | 10 October 2019, 18:54:03 UTC | MIPS: Disable Loongson MMI instructions for kernel build GCC 9.x automatically enables support for Loongson MMI instructions when using some -march= flags, and then errors out when -msoft-float is specified with: cc1: error: ‘-mloongson-mmi’ must be used with ‘-mhard-float’ The kernel shouldn't be using these MMI instructions anyway, just as it doesn't use floating point instructions. Explicitly disable them in order to fix the build with GCC 9.x. Signed-off-by: Paul Burton <paul.burton@mips.com> Fixes: 3702bba5eb4f ("MIPS: Loongson: Add GCC 4.4 support for Loongson2E") Fixes: 6f7a251a259e ("MIPS: Loongson: Add basic Loongson 2F support") Fixes: 5188129b8c9f ("MIPS: Loongson-3: Improve -march option and move it to Platform") Cc: Huacai Chen <chenhc@lemote.com> Cc: Jiaxun Yang <jiaxun.yang@flygoat.com> Cc: stable@vger.kernel.org # v2.6.32+ Cc: linux-mips@vger.kernel.org | 10 October 2019, 18:58:52 UTC |
38dffe1 | Jiaxun Yang | 10 October 2019, 15:01:57 UTC | MIPS: elf_hwcap: Export userspace ASEs A Golang developer reported MIPS hwcap isn't reflecting instructions that the processor actually supported so programs can't apply optimized code at runtime. Thus we export the ASEs that can be used in userspace programs. Reported-by: Meng Zhuo <mengzhuo1203@gmail.com> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com> Cc: linux-mips@vger.kernel.org Cc: Paul Burton <paul.burton@mips.com> Cc: <stable@vger.kernel.org> # 4.14+ Signed-off-by: Paul Burton <paul.burton@mips.com> | 10 October 2019, 18:57:36 UTC |
9e208aa | Linus Torvalds | 10 October 2019, 18:47:16 UTC | Merge tag 'xfs-5.4-fixes-3' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux Pull xfs fixes from Darrick Wong: "A couple of small code cleanups and bug fixes for rounding errors, metadata logging errors, and an extra layer of safeguards against leaking memory contents. - Fix a rounding error in the fallocate code - Minor code cleanups - Make sure to zero memory buffers before formatting metadata blocks - Fix a few places where we forgot to log an inode metadata update - Remove broken error handling that tried to clean up after a failure but still got it wrong" * tag 'xfs-5.4-fixes-3' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux: xfs: move local to extent inode logging into bmap helper xfs: remove broken error handling on failed attr sf to leaf change xfs: log the inode on directory sf to block format change xfs: assure zeroed memory buffers for certain kmem allocations xfs: removed unused error variable from xchk_refcountbt_rec xfs: remove unused flags arg from xfs_get_aghdr_buf() xfs: Fix tail rounding in xfs_alloc_file_space() | 10 October 2019, 18:47:16 UTC |
8624881 | Xiubo Li | 19 September 2019, 06:14:27 UTC | nbd: fix possible sysfs duplicate warning 1. nbd_put takes the mutex and drops nbd->ref to 0. It then does idr_remove and drops the mutex. 2. nbd_genl_connect takes the mutex. idr_find/idr_for_each fails to find an existing device, so it does nbd_dev_add. 3. just before the nbd_put could call nbd_dev_remove or not finished totally, but if nbd_dev_add try to add_disk, we can hit: debugfs: Directory 'nbd1' with parent 'block' already present! This patch will make sure all the disk add/remove stuff are done by holding the nbd_index_mutex lock. Reported-by: Mike Christie <mchristi@redhat.com> Reviewed-by: Josef Bacik <josef@toxicpanda.com> Signed-off-by: Xiubo Li <xiubli@redhat.com> Signed-off-by: Jens Axboe <axboe@kernel.dk> | 10 October 2019, 15:44:56 UTC |
ee7f522 | Rob Herring | 08 October 2019, 19:41:55 UTC | xen: Stop abusing DT of_dma_configure API As the removed comments say, these aren't DT based devices. of_dma_configure() is going to stop allowing a NULL DT node and calling it will no longer work. The comment is also now out of date as of commit 9ab91e7c5c51 ("arm64: default to the direct mapping in get_arch_dma_ops"). Direct mapping is now the default rather than dma_dummy_ops. According to Stefano and Oleksandr, the only other part needed is setting the DMA masks and there's no reason to restrict the masks to 32-bits. So set the masks to 64 bits. Cc: Robin Murphy <robin.murphy@arm.com> Cc: Julien Grall <julien.grall@arm.com> Cc: Nicolas Saenz Julienne <nsaenzjulienne@suse.de> Cc: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com> Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com> Cc: Juergen Gross <jgross@suse.com> Cc: Stefano Stabellini <sstabellini@kernel.org> Cc: Christoph Hellwig <hch@lst.de> Cc: xen-devel@lists.xenproject.org Signed-off-by: Rob Herring <robh@kernel.org> Acked-by: Oleksandr Andrushchenko <oleksandr_andrushchenko@epam.com> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com> | 10 October 2019, 15:43:35 UTC |
fb20da6 | Linus Torvalds | 10 October 2019, 15:39:00 UTC | Merge branch 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6 Pull crypto fixes from Herbert Xu: "Fix build issues in arm/aes-ce" * 'linus' of git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6: crypto: arm/aes-ce - add dependency on AES library crypto: arm/aes-ce - build for v8 architecture explicitly | 10 October 2019, 15:39:00 UTC |
f877987 | Linus Torvalds | 10 October 2019, 15:30:51 UTC | Merge tag 'for-5.4-rc2-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux Pull btrfs fixes from David Sterba: "A few more stabitly fixes, one build warning fix. - fix inode allocation under NOFS context - fix leak in fiemap due to concurrent append writes - fix log-root tree updates - fix balance convert of single profile on 32bit architectures - silence false positive warning on old GCCs (code moved in rc1)" * tag 'for-5.4-rc2-tag' of git://git.kernel.org/pub/scm/linux/kernel/git/kdave/linux: btrfs: silence maybe-uninitialized warning in clone_range btrfs: fix uninitialized ret in ref-verify btrfs: allocate new inode in NOFS context btrfs: fix balance convert to single on 32-bit host CPUs btrfs: fix incorrect updating of log root tree Btrfs: fix memory leak due to concurrent append writes with fiemap | 10 October 2019, 15:30:51 UTC |
ad338d0 | Linus Torvalds | 10 October 2019, 15:26:58 UTC | Merge branch 'work.dcache' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs Pull dcache_readdir() fixes from Al Viro: "The couple of patches you'd been OK with; no hlist conversion yet, and cursors are still in the list of children" [ Al is referring to future work to avoid some nasty O(n**2) behavior with the readdir cursors when you have lots of concurrent readdirs. This is just a fix for a race with a trivial cleanup - Linus ] * 'work.dcache' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs: libfs: take cursors out of list when moving past the end of directory Fix the locking in dcache_readdir() and friends | 10 October 2019, 15:26:58 UTC |
015c21b | Linus Torvalds | 10 October 2019, 15:16:44 UTC | Merge branch 'work.mount3' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs Pull mount fixes from Al Viro: "A couple of regressions from the mount series" * 'work.mount3' of git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs: vfs: add missing blkdev_put() in get_tree_bdev() shmem: fix LSM options parsing | 10 October 2019, 15:16:44 UTC |
5e48e55 | Geert Uytterhoeven | 10 October 2019, 12:30:46 UTC | MAINTAINERS: Remove Simon as Renesas SoC Co-Maintainer At the end of the v5.3 upstream kernel development cycle, Simon stepped down from his role as Renesas SoC maintainer. Remove his maintainership, git repository, and branch from the MAINTAINERS file, and add an entry to the CREDITS file to honor his work. Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org> | 10 October 2019, 15:12:51 UTC |