[PATCH 4.9 61/61] serial: pl011: add console matching function

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Aleksey Makarov commit 10879ae5f12e9cab3c4e8e9504c1aaa8a033bde7 upstream. This patch adds function pl011_console_match() that implements method match of struct console. It allows to match cons

[PATCH 4.9 49/61] MIPS: ptrace: Fix PTRACE_PEEKUSR requests for 64-bit FGRs

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit c7e814628df65f424fe197dde73bfc67e4a244d7 upstream. Use 64-bit accesses for 64-bit floating-point general registers with PTRACE_PEEKUSR, removing the truncation of their

[PATCH 4.9 54/61] IB/core: Fix error code for invalid GID entry

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Parav Pandit commit a840c93ca7582bb6c88df2345a33f979b7a67874 upstream. When a GID entry is invalid EAGAIN is returned. This is an incorrect error code, there is nothing that will make this GID

[PATCH 4.9 51/61] scsi: scsi_transport_srp: Fix shost to rport translation

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit c9ddf73476ff4fffb7a87bd5107a0705bf2cf64b upstream. Since an SRP remote port is attached as a child to shost->shost_gendev and as the only child, the translation from the

[PATCH 4.9 47/61] net/mlx4_en: fix potential use-after-free with dma_unmap_page

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sarah Newman [ Not relevant upstream, therefore no upstream commit. ] To fix, unmap the page as soon as possible. When swiotlb is in use, calling dma_unmap_page means that the original page ma

Re: [PATCH v2 2/3] ACPI / PPTT: fix build when CONFIG_ACPI_PPTT is not enabled

On Tue, Jun 05, 2018 at 03:35:03PM +0100, Sudeep Holla wrote: > Though CONFIG_ACPI_PPTT is selected by platforms and nor user visible, > it may be useful to support the build with CONFIG_ACPI_PPTT disabled. > > This patch adds the missing dummy/boiler plate implementation to fix > the build. > >

[PATCH 4.9 50/61] MIPS: prctl: Disallow FRE without FR with PR_SET_FP_MODE requests

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit 28e4213dd331e944e7fca1954a946829162ed9d4 upstream. Having PR_FP_MODE_FRE (i.e. Config5.FRE) set without PR_FP_MODE_FR (i.e. Status.FR) is not supported as the lone purp

[PATCH 4.9 53/61] hwtracing: stm: fix build error on some arches

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman commit 806e30873f0e74d9d41b0ef761bd4d3e55c7d510 upstream. Commit b5e2ced9bf81 ("stm class: Use vmalloc for the master map") caused a build error on some arches as vmalloc.h w

[PATCH 4.4 05/37] xfs: detect agfl count corruption and reset agfl

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Brian Foster commit a27ba2607e60312554cbcd43fc660b2c7f29dc9c upstream. The struct xfs_agfl v5 header was originally introduced with unexpected padding that caused the AGFL to operate with one l

[PATCH 4.9 60/61] sparc64: Dont clibber fixed registers in __multi4.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David S. Miller commit 79db795833bf5c3e798bcd7a5a3fb0505927 upstream. %g4 and %g5 are fixed registers used by the kernel for the thread pointer and the per-cpu offset. Use %o4 and %g7 inst

Re: linux-next: manual merge of the kvm tree with the arm64 tree

On 04/06/2018 09:33, Dave Martin wrote: > On Mon, Jun 04, 2018 at 04:57:54PM +1000, Stephen Rothwell wrote: >> Hi all, >> >> Today's linux-next merge of the kvm tree got a conflict in: >> >> arch/arm64/include/asm/processor.h >> >> between commit: >> >> 94b07c1f8c39 ("arm64: signal: Report sign

[PATCH 4.9 03/61] USB: serial: cp210x: use tcflag_t to fix incompatible pointer type

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit 009615ab7fd4e43b82a38e4e6adc5e23c1ee567f upstream. On sparc32, tcflag_t is unsigned long, unlike all other architectures: drivers/usb/serial/cp210x.c: In function

[PATCH 4.4 33/37] fix io_destroy()/aio_complete() race

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 4faa99965e027cc057c5145ce45fa772caa04e8d upstream. If io_destroy() gets to cancelling everything that can be cancelled and gets to kiocb_cancel() calling the function driver has

[PATCH 4.9 58/61] fix io_destroy()/aio_complete() race

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Al Viro commit 4faa99965e027cc057c5145ce45fa772caa04e8d upstream. If io_destroy() gets to cancelling everything that can be cancelled and gets to kiocb_cancel() calling the function driver has

[PATCH 4.9 24/61] powerpc/rfi-flush: Move out of HARDLOCKUP_DETECTOR #ifdef

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman The backport of the RFI flush support, done by me, has a minor bug in that the code is inside an #ifdef CONFIG_HARDLOCKUP_DETECTOR, which is incorrect. This doesn't matter with

[PATCH 4.9 25/61] powerpc/pseries: Support firmware disable of RFI flush

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 582605a429e20ae68fd0b041b2e840af296edd08 upstream. Some versions of firmware will have a setting that can be configured to disable the RFI flush, add support for it. Fi

[PATCH 4.9 23/61] arm64/cpufeature: dont use mutex in bringup path

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mark Rutland commit 63a1e1c95e60e798fa09ab3c536fb555aa5bbf2b upstream. Currently, cpus_set_cap() calls static_branch_enable_cpuslocked(), which must take the jump_label mutex. We call cpus_set

[PATCH 4.9 22/61] arm64: Add hypervisor safe helper for checking constant capabilities

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Suzuki K Poulose commit a4023f682739439b434165b54af7cb3676a4766e upstream. The hypervisor may not have full access to the kernel data structures and hence cannot safely use cpus_have_cap() help

[PATCH 1/2] drm/mxsfb: Fix runtime PM for unpowering lcdif block

Adding imx6sl/sx lcdif nodes in a power domain currently does work, it results in black/corrupted screens or hangs. While the driver does enable runtime pm it does not deal correctly with the block being unpowered. Fix by adding pm_runtime_get/put_sync to mxsfb_pipe_enable/disable. The mxsfb_plan

[PATCH 4.9 20/61] scsi: ufs: refactor device descriptor reading

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tomas Winkler commit 93fdd5ac64bbe80dac6416f048405362d7ef0945 upstream. Pull device descriptor reading out of ufs quirk so it can be used also for other purposes. Revamp the fixup setup: 1. R

[PATCH 4.9 21/61] scsi: ufs: Factor out ufshcd_read_desc_param

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Potomski, MichalX commit a4b0e8a4e92b1baa860e744847fbdb84a50a5071 upstream. Since in UFS 2.1 specification some of the descriptor lengths differs from 2.0 specification and some devices, which

[PATCH 4.9 45/61] powerpc/64s: Fix section mismatch warnings from setup_rfi_flush()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 501a78cbc17c329fabf8e9750a1e9ab810c88a0e upstream. The recent LPM changes to setup_rfi_flush() are causing some section mismatch warnings because we removed the __init a

[PATCH 4.9 44/61] powerpc/pseries: Restore default security feature flags on setup

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mauricio Faria de Oliveira commit 6232774f1599028a15418179d17f7df47ede770a upstream. After migration the security feature flags might have changed (e.g., destination system with unpatched firmw

[PATCH] mremap: Avoid TLB flushing anonymous pages that are not in swap cache

Commit 5d1904204c99 ("mremap: fix race between mremap() and page cleanning") fixed races between mremap and other operations for both file-backed and anonymous mappings. The file-backed was the most critical as it allowed the possibility that data could be changed on a physical page after page_mkcl

Re: [GIT PULL] fscrypt updates for 4.18

Am Dienstag, 5. Juni 2018, 19:02:08 CEST schrieb Theodore Y. Ts'o: > On Tue, Jun 05, 2018 at 06:10:24PM +0200, Richard Weinberger wrote: > > That's the question. I understand the use case, but I fear attack scenarios > > where someone manages to downgrade the crypto of my phone. > > This is why I w

[PATCH 4.9 41/61] powerpc/64s: Wire up cpu_show_spectre_v2()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit d6fbe1c55c55c6937cbea3531af7da84ab7473c3 upstream. Add a definition for cpu_show_spectre_v2() to override the generic version. This has several permuations, though in pr

[PATCH 4.9 35/61] powerpc/powernv: Set or clear security feature flags

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 77addf6e95c8689e478d607176b399a6242a777e upstream. Now that we have feature flags for security related things, set or clear them based on what we see in the device tree

[PATCH 4.9 37/61] powerpc/64s: Enhance the information in cpu_show_meltdown()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit ff348355e9c72493947be337bb4fae4fc1a41eba upstream. Now that we have the security feature flags we can make the information displayed in the "meltdown" file more informat

[PATCH 4.9 38/61] powerpc/powernv: Use the security flags in pnv_setup_rfi_flush()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 37c0bdd00d3ae83369ab60a6712c28e11e6458d5 upstream. Now that we have the security flags we can significantly simplify the code in pnv_setup_rfi_flush(), because we can us

[PATCH 4.9 36/61] powerpc/64s: Move cpu_show_meltdown()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 8ad33041563a10b34988800c682ada14b2612533 upstream. This landed in setup_64.c for no good reason other than we had nowhere else to put it. Now that we have a security-rel

[PATCH 4.9 18/61] tcp: avoid integer overflows in tcp_rcv_space_adjust()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 607065bad9931e72207b0cac365d7d4abc06bd99 upstream. When using large tcp_rmem[2] values (I did tests with 500 MB), I noticed overflows while computing rcvwin. Lets fix this

RE: [PATCH v3 03/10] mfd: da9063: Rename PMIC_DA9063 to PMIC_CHIP_ID_DA9063

On 04 June 2018 19:32, Marek Vasut wrote, > Subject: Re: [PATCH v3 03/10] mfd: da9063: Rename PMIC_DA9063 to > PMIC_CHIP_ID_DA9063 > > On 06/04/2018 02:26 PM, Lee Jones wrote: > > On Sat, 02 Jun 2018, Marek Vasut wrote: > > > >> The PMIC_DA9063 is a complete misnomer, it denotes the value of th

[RFC/PATCH] Input: make input_report_slot_state() return boolean

Let's make input_report_slot_state() return boolean representing whether the contact is active or not. This will allow writing code like: if (input_mt_report_slot_state(input, obj->mt_tool, obj->type != RMI_2D_OBJECT_NONE) { input_ev

[PATCH v2 1/2] compiler-gcc.h: add gnu_inline to all inline declarations

Functions marked extern inline do not emit an externally visible function when the gnu89 C standard is used. Some KBUILD Makefiles overwrite KBUILD_CFLAGS. This is an issue for GCC 5.1+ users as without an explicit C standard specified, the default is gnu11. Since c99, the semantics of extern inlin

[PATCH 4.9 33/61] powerpc: Add security feature flags for Spectre/Meltdown

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 9a868f634349e62922c226834aa23e3d1329ae7f upstream. This commit adds security feature flags to reflect the settings we receive from firmware regarding Spectre/Meltdown mi

[PATCH 4.9 31/61] powerpc/rfi-flush: Call setup_rfi_flush() after LPM migration

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 921bc6cf807ceb2ab8005319cf39f33494d6b100 upstream. We might have migrated to a machine that uses a different flush type, or doesn't need flushing at all. Signed-off-by:

[PATCH 4.9 30/61] powerpc/rfi-flush: Differentiate enabled and patched flush types

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mauricio Faria de Oliveira commit 0063d61ccfc011f379a31acaeba6de7c926fed2c upstream. Currently the rfi-flush messages print 'Using flush' for all enabled_flush_types, but that is not necessari

[PATCH v2 0/2] extern inline native_save_fl for paravirt

paravirt depends on a custom calling convention (callee saved), but expects this from a static inline function that it then forces to be outlined. This is problematic because different compilers or flags can then add a stack guard that violates the calling conventions. Uses extern inline with the

[PATCH 4.9 28/61] powerpc/rfi-flush: Make it possible to call setup_rfi_flush() again

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit abf110f3e1cea40f5ea15e85f5d67c39c14568a7 upstream. For PowerVM migration we want to be able to call setup_rfi_flush() again after we've migrated the partition. To suppo

[PATCH 4.9 26/61] powerpc/powernv: Support firmware disable of RFI flush

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit eb0a2d2620ae431c543963c8c7f08f597366fc60 upstream. Some versions of firmware will have a setting that can be configured to disable the RFI flush, add support for it. Fi

[PATCH 4.9 00/61] 4.9.107-stable review

This is the start of the stable review cycle for the 4.9.107 release. There are 61 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Thu Jun 7 17:00:59 UTC 2018. Anything receiv

[PATCH 4.9 07/61] Input: elan_i2c_smbus - fix corrupted stack

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Tissoires commit 40f7090bb1b4ec327ea1e1402ff5783af5b35195 upstream. New ICs (like the one on the Lenovo T480s) answer to ETP_SMBUS_IAP_VERSION_CMD 4 bytes instead of 3. This corrupts t

[PATCH 4.9 04/61] Revert "pinctrl: msm: Use dynamic GPIO numbering"

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit 0bd77073e693e8f93ff6ddba65a9f426153221cb which is commit a7aa75a2a7dba32594291a71c3704000a2fd7089 upstream. There's been too many complaints about this.

[PATCH 4.9 09/61] selinux: KASAN: slab-out-of-bounds in xattr_getsecurity

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sachin Grover commit efe3de79e0b52ca281ef6691480c8c68c82a4657 upstream. Call trace: [] dump_backtrace+0x0/0x428 [] show_stack+0x28/0x38 [] dump_stack+0xd4/0x124 [] print_address_description

Re: [PATCH 1/2] HID: multitouch: report MT_TOOL_PALM for non-confident touches

On Tue, Jun 05, 2018 at 03:50:15PM +0200, Benjamin Tissoires wrote: > On Tue, Jun 5, 2018 at 12:55 AM, Peter Hutterer > wrote: > > On Mon, Jun 04, 2018 at 02:19:44PM -0700, Dmitry Torokhov wrote: > >> On Mon, Jun 04, 2018 at 10:42:31PM +0200, Benjamin Tissoires wrote: > >> > On Mon, Jun 4, 2018 at

[PATCH 4.9 06/61] Revert "ima: limit file hash setting by user to fix and log modes"

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mimi Zohar commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b upstream. Userspace applications have been modified to write security xattrs, but they are not context aware. In the case of security

[PATCH 4.9 02/61] powerpc/64s: Clear PCR on boot

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Neuling commit faf37c44a105f3608115785f17cbbf3500f8bc71 upstream. Clear the PCR (Processor Compatibility Register) on boot to ensure we are not running in a compatibility mode. We've s

[PATCH 4.9 14/61] platform/chrome: cros_ec_lpc: remove redundant pointer request

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit d3b56c566d4ba8cae688baf3cca94425d57ea783 upstream. Pointer request is being assigned but never used, so remove it. Cleans up the clang warning: drivers/platform/chrome/cr

[PATCH 4.9 11/61] dma-buf: remove redundant initialization of sg_table

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit 531beb067c6185aceabfdee0965234c6a8fd133b upstream. sg_table is being initialized and is never read before it is updated again later on, hence making the initialization red

[PATCH 4.9 13/61] ASoC: Intel: sst: remove redundant variable dma_dev_name

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit 271ef65b5882425d500e969e875c98e47a6b0c86 upstream. The pointer dma_dev_name is assigned but never read, it is redundant and can therefore be removed. Cleans up clang warn

[PATCH 4.9 10/61] cfg80211: further limit wiphy names to 64 bytes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 814596495dd2b9d4aab92d8f89cf19060d25d2ea upstream. wiphy names were recently limited to 128 bytes by commit a7cfebcb7594 ("cfg80211: limit wiphy names to 128 bytes"). As it

[PATCH 4.9 12/61] rtlwifi: rtl8192cu: Remove variable self-assignment in rf.c

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Matthias Kaehlcke commit fb239c1209bb0f0b4830cc72507cc2f2d63fadbd upstream. In _rtl92c_get_txpower_writeval_by_regulatory() the variable writeVal is assigned to itself in an if ... else stateme

[PATCH 4.4 30/37] hwtracing: stm: fix build error on some arches

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman commit 806e30873f0e74d9d41b0ef761bd4d3e55c7d510 upstream. Commit b5e2ced9bf81 ("stm class: Use vmalloc for the master map") caused a build error on some arches as vmalloc.h w

Re: x86/asm: __clear_user() micro-optimization (was: "Re: [GIT PULL] x86/asm changes for v4.18")

On Tue, Jun 05, 2018 at 05:05:14PM +0200, Ingo Molnar wrote: > > * Linus Torvalds wrote: > > > On Mon, Jun 4, 2018 at 5:21 AM Ingo Molnar wrote: > > > > > > - __clear_user() micro-optimization (Alexey Dobriyan) > > > > Was this actually tested? > > I'm not sure - Alexey? > > > I think one r

[PATCH 4.9 01/61] arm64: lse: Add early clobbers to some input/output asm operands

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Will Deacon commit 32c3fa7cdf0c4a3eb8405fc3e13398de019e828b upstream. For LSE atomics that read and write a register operand, we need to ensure that these operands are annotated as "early clobb

[PATCH 4.4 35/37] sparc64: Add __multi3 for gcc 7.x and later.

4.4-stable review patch. If anyone has any objections, please let me know. -- From: David S. Miller commit 1b4af13ff2cc6897557bb0b8d9e2fad4fa4d67aa upstream. Reported-by: Waldemar Brodkorb Signed-off-by: David S. Miller Cc: Guenter Roeck Signed-off-by: Greg Kroah-Hartman

Re: [PATCH] slab: Clean up the code comment in slab kmem_cache struct

On Sun, 3 Jun 2018, Baoquan He wrote: > diff --git a/include/linux/slab_def.h b/include/linux/slab_def.h > index d9228e4d0320..3485c58cfd1c 100644 > --- a/include/linux/slab_def.h > +++ b/include/linux/slab_def.h > @@ -67,9 +67,10 @@ struct kmem_cache { > > /* >* If debugging is enab

[PATCH 4.4 08/37] tracing: Fix crash when freeing instances with event triggers

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Steven Rostedt (VMware) commit 86b389ff22bd6ad8fd3cb98e41cd271886c6d023 upstream. If a instance has an event trigger enabled when it is freed, it could cause an access of free memory. Here's th

[PATCH 4.4 06/37] Revert "ima: limit file hash setting by user to fix and log modes"

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mimi Zohar commit f5acb3dcba1ffb7f0b8cbb9dba61500eea5d610b upstream. Userspace applications have been modified to write security xattrs, but they are not context aware. In the case of security

[PATCH 4.4 07/37] Input: elan_i2c_smbus - fix corrupted stack

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Benjamin Tissoires commit 40f7090bb1b4ec327ea1e1402ff5783af5b35195 upstream. New ICs (like the one on the Lenovo T480s) answer to ETP_SMBUS_IAP_VERSION_CMD 4 bytes instead of 3. This corrupts t

[PATCH 4.4 04/37] sh: New gcc support

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yoshinori Sato commit 940d4113f3306e07a1f86541489b686d1a979d54 upstream. New gcc (4.8 or later) used new shift helper functions. So we need added new helper to private libgcc. Signed-off-by: Y

[PATCH 4.4 26/37] MIPS: ptrace: Fix PTRACE_PEEKUSR requests for 64-bit FGRs

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit c7e814628df65f424fe197dde73bfc67e4a244d7 upstream. Use 64-bit accesses for 64-bit floating-point general registers with PTRACE_PEEKUSR, removing the truncation of their

[PATCH 4.4 27/37] MIPS: prctl: Disallow FRE without FR with PR_SET_FP_MODE requests

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Maciej W. Rozycki commit 28e4213dd331e944e7fca1954a946829162ed9d4 upstream. Having PR_FP_MODE_FRE (i.e. Config5.FRE) set without PR_FP_MODE_FR (i.e. Status.FR) is not supported as the lone purp

[PATCH 4.4 29/37] stm class: Use vmalloc for the master map

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Shishkin commit b5e2ced9bf81393034072dd4d372f6b430bc1f0a upstream. Fengguang is running into a warning from the buddy allocator: > swapper/0: page allocation failure: order:9, > mod

[PATCH 4.4 25/37] iio:kfifo_buf: check for uint overflow

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Martin Kelly commit 3d13de4b027d5f6276c0f9d3a264f518747d83f2 upstream. Currently, the following causes a kernel OOPS in memcpy: echo 1073741825 > buffer/length echo 1 > buffer/enable Note tha

Re: [PATCH v10 0/5] Kernel parameter parser cleanup/enhancement

On Tue, 5 Jun 2018 20:05:50 +0300 Andy Shevchenko wrote: > On Tue, Jun 5, 2018 at 7:43 PM, Michal Suchanek > wrote: > > Hello, > > > > due to work on the fadump_extra_args I looked at the kernel > > parameter parser and found its grammar rather curious. > > > > It supports double quotes but not

[PATCH 4.4 24/37] dmaengine: usb-dmac: fix endless loop in usb_dmac_chan_terminate_all()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Yoshihiro Shimoda commit d9f5efade2cfd729138a7cafb46d01044da40f5e upstream. This patch fixes an issue that list_for_each_entry() in usb_dmac_chan_terminate_all() is possible to cause endless lo

[PATCH 4.4 23/37] i2c: rcar: revoke START request early

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wolfram Sang commit 52df445f29b79006d8b2dcd129152987c0d3bd64 upstream. If we don't clear START generation as soon as possible, it may cause another message to be generated, e.g. when receiving

[PATCH 4.4 20/37] i2c: rcar: init new messages in irq

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wolfram Sang commit cc21d0b4b62e41e5013d763adade5ea4462c33a4 upstream. Setting up new messages was done in process context while handling a message was in interrupt context. Because of the HW d

[PATCH 4.4 17/37] i2c: rcar: remove unused IOERROR state

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wolfram Sang commit 90f779e565bdc18dd4f79d81cf11f43a7266010b upstream. Signed-off-by: Wolfram Sang Signed-off-by: Wolfram Sang Signed-off-by: Fabrizio Castro Reviewed-by: Chris Paterson Sig

[PATCH 4.4 18/37] i2c: rcar: remove spinlock

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wolfram Sang commit ff2316b87a336bff940939cd9fc56287ed48e578 upstream. After making sure to reinit the HW and clear interrupts in the timeout case, we know that interrupts are always disabled i

Re: [PATCH v6 0/7] vfio/type1: Add support for valid iova list management

[Cc +dwmw2] On Fri, 25 May 2018 14:54:08 -0600 Alex Williamson wrote: > On Fri, 25 May 2018 08:45:36 + > Shameerali Kolothum Thodi wrote: > > > Yes, the above changes related to list empty cases looks fine to me. > > Thanks Shameer, applied to my next branch with the discussed fixes fo

[PATCH 4.4 19/37] i2c: rcar: refactor setup of a msg

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wolfram Sang commit b9d0684c79c4b9d30ce0d47d3270493dd0e76e59 upstream. We want to reuse this function later. Signed-off-by: Wolfram Sang Signed-off-by: Wolfram Sang Signed-off-by: Fabrizio C

[PATCH 4.4 16/37] i2c: rcar: rework hw init

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wolfram Sang commit 2c78cdc1c06308a59d6ed4145cdba73fdeff8c0d upstream. We don't need to init HW before every transfer since we know the HW state then. HW init at probe time is enough. While her

[PATCH 4.4 15/37] i2c: rcar: make sure clocks are on when doing clock calculation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wolfram Sang commit e43e0df13f8528ca55ed79f469c4b2af897fa796 upstream. When calculating the bus speed, the clock should be on, of course. Most bootloaders left them on, so this went unnoticed s

[PATCH 4.4 14/37] tcp: avoid integer overflows in tcp_rcv_space_adjust()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit 607065bad9931e72207b0cac365d7d4abc06bd99 upstream. When using large tcp_rmem[2] values (I did tests with 500 MB), I noticed overflows while computing rcvwin. Lets fix this

[PATCH 4.4 13/37] irda: fix overly long udelay()

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit c9bd28233b6d0d82ac3ba0215723be0a8262c39c upstream. irda_get_mtt() returns a hardcoded '1' in some cases, and with gcc-7, we get a build error because this triggers a co

[PATCH 4.4 00/37] 4.4.136-stable review

This is the start of the stable review cycle for the 4.4.136 release. There are 37 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Thu Jun 7 17:00:49 UTC 2018. Anything receiv

Re: [GIT PULL] Device properties framework update for v4.18-rc1

On Mon, Jun 4, 2018 at 4:31 AM Rafael J. Wysocki wrote: > > device property: Get rid of union aliasing Honestly, this looks questionable to me. I'm not talking about the changes themselves - I can live with them. But the _rationale_ is pure and utter garbage, and dangerously so. The fact is, u

Re: x86/asm: __clear_user() micro-optimization (was: "Re: [GIT PULL] x86/asm changes for v4.18")

On Tue, Jun 5, 2018 at 10:22 AM Alexey Dobriyan wrote: > > Tested? :^) I had P4 maybe ~15(?) years ago. Did you EVEN test it on what you have today? Do you have any numbers at all, in other words? Micro-optimizations need numbers. Otherwise they aren't micro-optimizations, they are just "change

Re: [GIT PULL] Device properties framework update for v4.18-rc1

On Tue, Jun 5, 2018 at 10:30 AM Linus Torvalds wrote: > > Honestly, this looks questionable to me. > > I'm not talking about the changes themselves - I can live with them. > But the _rationale_ is pure and utter garbage, and dangerously so. Side note: I've merged it, and it's going through my bui

Re: How to print stack uses of IRQ in ARM64

Hi Vishun, (CC: +linux-arm-kernel list) On 05/06/18 14:12, Andy Shevchenko wrote: > On Thu, May 31, 2018 at 1:01 PM, Vishnu Motghare > wrote: >> My understanding is each CPU getting its own IRQ stack. So is it >> possible to print the stack uses of each IRQ handler? The stacks are per-cpu not

Re: [CFT][PATCH] kernfs: Correct kernfs directory seeks.

"'t...@kernel.org'" writes: > Hello, > > On Tue, Jun 05, 2018 at 10:31:36AM -0500, Eric W. Biederman wrote: >> What I have above is not the clearest, and in fact the logic could be >> better. >> >> The fundamental challenge is because hash collisions are possible a file >> offset does not hold c

[PATCH 01/46] perf tools: Remove dead quote.[ch] code

From: Arnaldo Carvalho de Melo In c68677014bac ("perf tools: Remove support for command aliases") we removed the only remaining use of a function provided by these files, so ditch it. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: https://lkml.kernel.org

[PATCH 02/46] perf probe: Use return of map__get() to make code more compact

From: Arnaldo Carvalho de Melo The __get() idiom returns a reference count for the object passed, i.e. all functions of this type return the object passed, so take advantage of that to make the code more compact. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Masami Hiramatsu Cc: Namhyu

[PATCH 04/46] perf tools: No need to check if the argument to __get() function is NULL

From: Arnaldo Carvalho de Melo Those functions always check if the argument is NULL before trying to grab a reference count, and also will return the received object, so, to make code more compact, no need to check for NULL. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Krister Johansen

[PATCH 05/46] perf annotate: Pass perf_evsel instead of just evsel->idx

From: Arnaldo Carvalho de Melo The code gets shorter and we'll be able to use evsel->evlist in a followup patch. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: https://lkml.kernel.org/n/tip-t0s7vy19wq5kak74kavm8...@git.kernel.org Signed-off-by: Arnaldo C

[PATCH 08/46] perf annotate: Introduce constructor/destructor for annotated_source

From: Arnaldo Carvalho de Melo More stuff will go in there, all the parts that are not needed when a symbol had no samples and that were mistakenly added to 'struct annotation'. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: https://lkml.kernel.org/n/tip

[PATCH 15/46] perf tools: Ditch the symbol_conf.nr_events global

From: Arnaldo Carvalho de Melo Since over time the places where we need to pass this got reduced because we can obtain it from evsel->evlist->nr_entries, no need to have this global anymore. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: https://lkml.ker

[PATCH 11/46] perf annotate: Introduce symbol__hists()

From: Arnaldo Carvalho de Melo In this case we're wanting just notes->src->histograms, allocating it if needed. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: https://lkml.kernel.org/n/tip-4iatualjskia7sojmdb65...@git.kernel.org Signed-off-by: Arnaldo Ca

[PATCH 14/46] perf annotate: Replace symbol__alloc_hists() with symbol__hists()

From: Arnaldo Carvalho de Melo Its a bit shorter, so ditch the old symbol__alloc_hists() function. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: https://lkml.kernel.org/n/tip-m7tienxk7dijh5ln62yln...@git.kernel.org Signed-off-by: Arnaldo Carvalho de Mel

[PATCH 23/46] perf annotate: Move disassembler_style global to annotation_options

From: Arnaldo Carvalho de Melo Continuing to group annotation specific stuff into a struct. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: https://lkml.kernel.org/n/tip-p3cdhltj58jt0byjzg3g7...@git.kernel.org Signed-off-by: Arnaldo Carvalho de Melo ---

[PATCH 30/46] perf sched: Use sched->show_callchain where appropriate

From: Arnaldo Carvalho de Melo Instead of using symbol_conf.use_callchain, reducing its usage a bit more. Cc: Adrian Hunter Cc: David Ahern Cc: Jiri Olsa Cc: Namhyung Kim Cc: Wang Nan Link: https://lkml.kernel.org/n/tip-edgwb1b2mpbrdeg0w64wp...@git.kernel.org Signed-off-by: Arnaldo Carvalho

[PATCH 35/46] perf tools: Fix symbol and object code resolution for vdso32 and vdsox32

From: Adrian Hunter Fix __kmod_path__parse() so that perf tools does not treat vdso32 and vdsox32 as kernel modules and fail to find the object. Signed-off-by: Adrian Hunter Cc: Jiri Olsa Cc: Wang Nan Cc: sta...@vger.kernel.org Fixes: 1f121b03d058 ("perf tools: Deal with kernel module names i

[PATCH 36/46] perf record: Enable arbitrary event names thru name= modifier

From: Alexey Budankov Enable complex event names containing [.:=,] symbols to be encoded into Perf trace using name= modifier e.g. like this: perf record -e cpu/name=\'OFFCORE_RESPONSE:request=DEMAND_RFO:response=L3_HIT.SNOOP_HITM\',\ period=0x3567e0,event=0x3c,cmask=0x1/Duk

[PATCH 44/46] perf intel-pt: Fix decoding to accept CBR between FUP and corresponding TIP

From: Adrian Hunter It is possible to have a CBR packet between a FUP packet and corresponding TIP packet. Stop treating it as an error. Signed-off-by: Adrian Hunter Cc: sta...@vger.kernel.org Link: http://lkml.kernel.org/r/1527762225-26024-3-git-send-email-adrian.hun...@intel.com Signed-off-b

[PATCH 46/46] perf intel-pt: Fix "Unexpected indirect branch" error

From: Adrian Hunter Some Atom CPUs can produce FUP packets that contain NLIP (next linear instruction pointer) instead of CLIP (current linear instruction pointer). That will result in "Unexpected indirect branch" errors. Fix by comparing IP to NLIP in that case. Signed-off-by: Adrian Hunter C

[PATCH 45/46] perf intel-pt: Fix MTC timing after overflow

From: Adrian Hunter On some platforms, overflows will clear before MTC wraparound, and there is no following TSC/TMA packet. In that case the previous TMA is valid. Since there will be a valid TMA either way, stop setting 'have_tma' to false upon overflow. Signed-off-by: Adrian Hunter Cc: sta..

[PATCH 42/46] perf script powerpc: Python script for hypervisor call statistics

From: Ravi Bangoria Add python script to show hypervisor call statistics. Ex, # perf record -a -e "{powerpc:hcall_entry,powerpc:hcall_exit}" # perf script -s scripts/python/powerpc-hcalls.py hcallcount min(ns) max(ns) avg(ns)

[PATCH 43/46] perf intel-pt: Fix sync_switch INTEL_PT_SS_NOT_TRACING

From: Adrian Hunter sync_switch is a facility to synchronize decoding more closely with the point in the kernel when the context actually switched. In one case, INTEL_PT_SS_NOT_TRACING state was not correctly transitioning to INTEL_PT_SS_TRACING state due to a missing case clause. Add it. Signe

<    1   2   3   4   5   6   7   8   >