[tip:perf/core] perf stat: Handle partially bad results with merging

Commit-ID: b4229e9d4cac2295f8f04ec26acd571a391c6c37 Gitweb: http://git.kernel.org/tip/b4229e9d4cac2295f8f04ec26acd571a391c6c37 Author: Andi Kleen AuthorDate: Mon, 20 Mar 2017 13:17:01 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 21

[tip:perf/core] perf stat: Handle partially bad results with merging

Commit-ID: b4229e9d4cac2295f8f04ec26acd571a391c6c37 Gitweb: http://git.kernel.org/tip/b4229e9d4cac2295f8f04ec26acd571a391c6c37 Author: Andi Kleen AuthorDate: Mon, 20 Mar 2017 13:17:01 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 21 Mar 2017 16:07:00 -0300 perf stat:

[tip:perf/core] perf probe: Add sdt probes arguments into the uprobe cmd string

Commit-ID: 3b1f8311f6963cd11a7d1efbcd2fd900d472ba5c Gitweb: http://git.kernel.org/tip/3b1f8311f6963cd11a7d1efbcd2fd900d472ba5c Author: Alexis Berlemont AuthorDate: Wed, 14 Dec 2016 01:07:32 +0100 Committer: Arnaldo Carvalho de Melo

[tip:perf/core] perf probe: Add sdt probes arguments into the uprobe cmd string

Commit-ID: 3b1f8311f6963cd11a7d1efbcd2fd900d472ba5c Gitweb: http://git.kernel.org/tip/3b1f8311f6963cd11a7d1efbcd2fd900d472ba5c Author: Alexis Berlemont AuthorDate: Wed, 14 Dec 2016 01:07:32 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 21 Mar 2017 10:59:01 -0300 perf

[tip:perf/core] perf annotate: Add comment clarifying how the source code line is parsed

Commit-ID: ed7b339fb570749042332169e62541b208fc4296 Gitweb: http://git.kernel.org/tip/ed7b339fb570749042332169e62541b208fc4296 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 21 Mar 2017 16:00:50 -0300 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf annotate: Add comment clarifying how the source code line is parsed

Commit-ID: ed7b339fb570749042332169e62541b208fc4296 Gitweb: http://git.kernel.org/tip/ed7b339fb570749042332169e62541b208fc4296 Author: Arnaldo Carvalho de Melo AuthorDate: Tue, 21 Mar 2017 16:00:50 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 21 Mar 2017 16:00:50 -0300

[tip:perf/core] perf stat: Factor out callback for collecting event values

Commit-ID: fbe51fba82901fd15d3e0a068388fcd7d02dc047 Gitweb: http://git.kernel.org/tip/fbe51fba82901fd15d3e0a068388fcd7d02dc047 Author: Andi Kleen AuthorDate: Mon, 20 Mar 2017 13:16:59 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 21

[tip:perf/core] perf stat: Factor out callback for collecting event values

Commit-ID: fbe51fba82901fd15d3e0a068388fcd7d02dc047 Gitweb: http://git.kernel.org/tip/fbe51fba82901fd15d3e0a068388fcd7d02dc047 Author: Andi Kleen AuthorDate: Mon, 20 Mar 2017 13:16:59 -0700 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 21 Mar 2017 16:03:39 -0300 perf stat:

[tip:perf/core] perf sdt: Add scanning of sdt probes arguments

Commit-ID: be88184b1c7054719296387c6063748fb48fa645 Gitweb: http://git.kernel.org/tip/be88184b1c7054719296387c6063748fb48fa645 Author: Alexis Berlemont AuthorDate: Wed, 14 Dec 2016 01:07:31 +0100 Committer: Arnaldo Carvalho de Melo

[tip:perf/core] perf sdt: Add scanning of sdt probes arguments

Commit-ID: be88184b1c7054719296387c6063748fb48fa645 Gitweb: http://git.kernel.org/tip/be88184b1c7054719296387c6063748fb48fa645 Author: Alexis Berlemont AuthorDate: Wed, 14 Dec 2016 01:07:31 +0100 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 21 Mar 2017 10:56:28 -0300 perf sdt:

[tip:perf/core] perf probe: Change MAX_CMDLEN

Commit-ID: 2e1f8f7895731a8592d483a7364a23855843af17 Gitweb: http://git.kernel.org/tip/2e1f8f7895731a8592d483a7364a23855843af17 Author: Ravi Bangoria AuthorDate: Tue, 7 Feb 2017 11:15:47 +0530 Committer: Arnaldo Carvalho de Melo

[tip:perf/core] perf probe: Change MAX_CMDLEN

Commit-ID: 2e1f8f7895731a8592d483a7364a23855843af17 Gitweb: http://git.kernel.org/tip/2e1f8f7895731a8592d483a7364a23855843af17 Author: Ravi Bangoria AuthorDate: Tue, 7 Feb 2017 11:15:47 +0530 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 21 Mar 2017 10:34:59 -0300 perf probe:

Re: [RFC PATCH v0.2] PCI: Add support for tango PCIe host bridge

On 23/03/17 17:03, Mason wrote: > On 23/03/2017 15:22, Marc Zyngier wrote: > >> On 23/03/17 13:05, Mason wrote: >> >>> +#define MSI_COUNT 32 >> >> Is this something that is hardcoded? Unlikely to ever change? > > The host bridge actually supports 256 MSIs. > > IIUC, what you suggested on IRC is

Re: [RFC PATCH v0.2] PCI: Add support for tango PCIe host bridge

On 23/03/17 17:03, Mason wrote: > On 23/03/2017 15:22, Marc Zyngier wrote: > >> On 23/03/17 13:05, Mason wrote: >> >>> +#define MSI_COUNT 32 >> >> Is this something that is hardcoded? Unlikely to ever change? > > The host bridge actually supports 256 MSIs. > > IIUC, what you suggested on IRC is

[tip:perf/core] perf probe: Return errno when not hitting any event

Commit-ID: 70946723eeb859466f026274b29c6196e39149c4 Gitweb: http://git.kernel.org/tip/70946723eeb859466f026274b29c6196e39149c4 Author: Kefeng Wang AuthorDate: Fri, 17 Mar 2017 16:16:32 +0800 Committer: Arnaldo Carvalho de Melo CommitDate:

[tip:perf/core] perf probe: Return errno when not hitting any event

Commit-ID: 70946723eeb859466f026274b29c6196e39149c4 Gitweb: http://git.kernel.org/tip/70946723eeb859466f026274b29c6196e39149c4 Author: Kefeng Wang AuthorDate: Fri, 17 Mar 2017 16:16:32 +0800 Committer: Arnaldo Carvalho de Melo CommitDate: Tue, 21 Mar 2017 10:45:02 -0300 perf probe:

Re: locking/atomic: Introduce atomic_try_cmpxchg()

On Fri, Mar 24, 2017 at 10:23 AM, Peter Zijlstra wrote: > On Fri, Mar 24, 2017 at 09:54:46AM -0700, Andy Lutomirski wrote: >> > So the first snipped I tested regressed like so: >> > >> > >> > : >> > : >> >0:

Re: locking/atomic: Introduce atomic_try_cmpxchg()

On Fri, Mar 24, 2017 at 10:23 AM, Peter Zijlstra wrote: > On Fri, Mar 24, 2017 at 09:54:46AM -0700, Andy Lutomirski wrote: >> > So the first snipped I tested regressed like so: >> > >> > >> > : >> > : >> >0: 8b 07

Re: [PATCH v6 2/4] mm: Add functions to support extra actions on swap in/out

On 02/28/2017 10:35 AM, Khalid Aziz wrote: > diff --git a/mm/memory.c b/mm/memory.c > index 6bf2b47..b086c76 100644 > --- a/mm/memory.c > +++ b/mm/memory.c > @@ -2658,6 +2658,7 @@ int do_swap_page(struct vm_fault *vmf) > if (pte_swp_soft_dirty(vmf->orig_pte)) > pte =

Re: [PATCH v6 2/4] mm: Add functions to support extra actions on swap in/out

On 02/28/2017 10:35 AM, Khalid Aziz wrote: > diff --git a/mm/memory.c b/mm/memory.c > index 6bf2b47..b086c76 100644 > --- a/mm/memory.c > +++ b/mm/memory.c > @@ -2658,6 +2658,7 @@ int do_swap_page(struct vm_fault *vmf) > if (pte_swp_soft_dirty(vmf->orig_pte)) > pte =

Re: [PATCH v2 1/2] regulator: core: add regulator_has_continuous_voltage_range()

On Thu, Mar 23, 2017 at 02:40:16PM -0700, Matthias Kaehlcke wrote: > El Mon, Mar 20, 2017 at 12:06:15PM + Mark Brown ha dit: > > On Fri, Mar 17, 2017 at 05:03:30PM -0700, Matthias Kaehlcke wrote: > > > You are right that my case is very specialist, however I think it is > > > a general

Re: [PATCH v2 1/2] regulator: core: add regulator_has_continuous_voltage_range()

On Thu, Mar 23, 2017 at 02:40:16PM -0700, Matthias Kaehlcke wrote: > El Mon, Mar 20, 2017 at 12:06:15PM + Mark Brown ha dit: > > On Fri, Mar 17, 2017 at 05:03:30PM -0700, Matthias Kaehlcke wrote: > > > You are right that my case is very specialist, however I think it is > > > a general

Re: [PATCH v2 4/7] efi/capsule: Adjust return type of efi_capsule_setup_info

On 24 March 2017 at 17:34, Jan Kiszka wrote: > We actually expect int at the caller and never return any size > information. > > Signed-off-by: Jan Kiszka Reviewed-by: Ard Biesheuvel > --- >

Re: [PATCH v2 4/7] efi/capsule: Adjust return type of efi_capsule_setup_info

On 24 March 2017 at 17:34, Jan Kiszka wrote: > We actually expect int at the caller and never return any size > information. > > Signed-off-by: Jan Kiszka Reviewed-by: Ard Biesheuvel > --- > drivers/firmware/efi/capsule-loader.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > >

Re: [PATCH] acpi: fix incompatibility with mcount-based function graph tracing

On Fri, 24 Mar 2017 13:12:54 -0500 Josh Poimboeuf wrote: > Instead I was able to "fix" it by ignoring ftrace calls in real mode: > > - > index 8f3d9cf..5c0d0c6 100644 > --- a/arch/x86/kernel/ftrace.c > +++ b/arch/x86/kernel/ftrace.c > @@ -983,6 +983,9 @@ void

Re: [PATCH] acpi: fix incompatibility with mcount-based function graph tracing

On Fri, 24 Mar 2017 13:12:54 -0500 Josh Poimboeuf wrote: > Instead I was able to "fix" it by ignoring ftrace calls in real mode: > > - > index 8f3d9cf..5c0d0c6 100644 > --- a/arch/x86/kernel/ftrace.c > +++ b/arch/x86/kernel/ftrace.c > @@ -983,6 +983,9 @@ void prepare_ftrace_return(unsigned

Re: [GIT PULL 00/20] perf/core improvements and fixes

; Merge tag 'perf-core-for-mingo-4.12-20170320' of > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core > (2017-03-21 07:41:29 +0100) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git >

Re: [GIT PULL 00/20] perf/core improvements and fixes

perf-core-for-mingo-4.12-20170320' of > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux into perf/core > (2017-03-21 07:41:29 +0100) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-core-fo

Re: [PATCH] virtio_balloon: prevent uninitialized variable use

On 23.03.2017 16:17, Arnd Bergmann wrote: > The latest gcc-7.0.1 snapshot reports a new warning: > > virtio/virtio_balloon.c: In function 'update_balloon_stats': > virtio/virtio_balloon.c:258:26: error: 'events[2]' is used uninitialized in > this function [-Werror=uninitialized] >

Re: [PATCH] virtio_balloon: prevent uninitialized variable use

On 23.03.2017 16:17, Arnd Bergmann wrote: > The latest gcc-7.0.1 snapshot reports a new warning: > > virtio/virtio_balloon.c: In function 'update_balloon_stats': > virtio/virtio_balloon.c:258:26: error: 'events[2]' is used uninitialized in > this function [-Werror=uninitialized] >

Re: [PATCH v5 2/5] perf report: Find the inline stack for a given address

Em Fri, Mar 17, 2017 at 05:42:24AM +0800, Jin Yao escreveu: > It would be useful for perf to support a mode to query the > inline stack for a given callgraph address. This would simplify > finding the right code in code that does a lot of inlining. > > The srcline.c has contained the code which

Re: [PATCH v5 2/5] perf report: Find the inline stack for a given address

Em Fri, Mar 17, 2017 at 05:42:24AM +0800, Jin Yao escreveu: > It would be useful for perf to support a mode to query the > inline stack for a given callgraph address. This would simplify > finding the right code in code that does a lot of inlining. > > The srcline.c has contained the code which

[PATCH v2 3/3] ARM: multi_v7_defconfig: Enable Exynos RNG and user-space crypto API

Enable the new Exynos pseudo random number generator driver and user-space API to access crypto algorithms and devices (not only RNG). Signed-off-by: Krzysztof Kozlowski --- arch/arm/configs/multi_v7_defconfig | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH v2 3/3] ARM: multi_v7_defconfig: Enable Exynos RNG and user-space crypto API

Enable the new Exynos pseudo random number generator driver and user-space API to access crypto algorithms and devices (not only RNG). Signed-off-by: Krzysztof Kozlowski --- arch/arm/configs/multi_v7_defconfig | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH] tty: serial: fsl_lpuart: lock port on console write

The console write code is not entirely race free (e.g. the operations to disabling the UART interrupts are not atomic) hence locking is required. This has been become apparent with the PREEMPT RT patchset applied: With the fully preemptible kernel configuration the system often ended up in a

[PATCH] tty: serial: fsl_lpuart: lock port on console write

The console write code is not entirely race free (e.g. the operations to disabling the UART interrupts are not atomic) hence locking is required. This has been become apparent with the PREEMPT RT patchset applied: With the fully preemptible kernel configuration the system often ended up in a

Re: [PATCH 3/9] arm64: mm: install SError abort handler

Hi Florian, On Fri, Mar 24, 2017 at 10:53:48AM -0700, Florian Fainelli wrote: > On 03/24/2017 10:35 AM, Mark Rutland wrote: > > On Fri, Mar 24, 2017 at 09:48:40AM -0700, Doug Berger wrote: > >> On 03/24/2017 08:16 AM, Mark Rutland wrote: > >>> On Fri, Mar 24, 2017 at 07:46:26AM -0700, Doug Berger

Re: [PATCH 3/9] arm64: mm: install SError abort handler

Hi Florian, On Fri, Mar 24, 2017 at 10:53:48AM -0700, Florian Fainelli wrote: > On 03/24/2017 10:35 AM, Mark Rutland wrote: > > On Fri, Mar 24, 2017 at 09:48:40AM -0700, Doug Berger wrote: > >> On 03/24/2017 08:16 AM, Mark Rutland wrote: > >>> On Fri, Mar 24, 2017 at 07:46:26AM -0700, Doug Berger

Re: [PATCH] serdev: Replace serdev_device_write_buf with serdev_device_write

On Mon, Mar 20, 2017 at 11:56 AM, Andrey Smirnov wrote: > Convert serdev_device_write_buf's code to be able to transfer amount of > data potentially exceeding "write room" at the moment of invocation. > > To support that, also add serdev_device_write_wakeup. > > Drivers

Re: [PATCH] serdev: Replace serdev_device_write_buf with serdev_device_write

On Mon, Mar 20, 2017 at 11:56 AM, Andrey Smirnov wrote: > Convert serdev_device_write_buf's code to be able to transfer amount of > data potentially exceeding "write room" at the moment of invocation. > > To support that, also add serdev_device_write_wakeup. > > Drivers wanting to use full extent

Re: [PATCH v4 01/11] mm: x86: move _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1

Tim Chen wrote: > On Mon, 2017-03-13 at 11:44 -0400, Zi Yan wrote: >> From: Naoya Horiguchi >> >> pmd_present() checks _PAGE_PSE along with _PAGE_PRESENT to avoid >> false negative return when it races with thp spilt >> (during which _PAGE_PRESENT is temporary

Re: [PATCH v4 01/11] mm: x86: move _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1

Tim Chen wrote: > On Mon, 2017-03-13 at 11:44 -0400, Zi Yan wrote: >> From: Naoya Horiguchi >> >> pmd_present() checks _PAGE_PSE along with _PAGE_PRESENT to avoid >> false negative return when it races with thp spilt >> (during which _PAGE_PRESENT is temporary cleared.) I don't think that >>

Re: [PATCH] usb: musb: cppi_dma.c: use DIV_ROUND_UP macro in cppi_next_(r|t)x_segment()

On Wed, Feb 15, 2017 at 11:12:36AM +0300, Ivan Safonov wrote: > DIV_ROUND_UP is bit useful than series of "/" and "%" operations. > Replace "/%" sequence with DIV_ROUND_UP macro. > > Signed-off-by: Ivan Safonov > --- > drivers/usb/musb/cppi_dma.c | 10 -- > 1 file

Re: [PATCH] usb: musb: cppi_dma.c: use DIV_ROUND_UP macro in cppi_next_(r|t)x_segment()

On Wed, Feb 15, 2017 at 11:12:36AM +0300, Ivan Safonov wrote: > DIV_ROUND_UP is bit useful than series of "/" and "%" operations. > Replace "/%" sequence with DIV_ROUND_UP macro. > > Signed-off-by: Ivan Safonov > --- > drivers/usb/musb/cppi_dma.c | 10 -- > 1 file changed, 4

Re: [PATCH v4 2/4] dt-bindings: add the grf clock for dw-mipi-dsi

On Wed, Mar 22, 2017 at 09:54:49AM +0800, Chris Zhong wrote: > For RK3399, the grf clock should be controlled by dw-mipi-dsi driver, > add the description for this clock. > > Signed-off-by: Chris Zhong > Reviewed-by: Sean Paul > --- > > Changes in

Re: [PATCH v4 2/4] dt-bindings: add the grf clock for dw-mipi-dsi

On Wed, Mar 22, 2017 at 09:54:49AM +0800, Chris Zhong wrote: > For RK3399, the grf clock should be controlled by dw-mipi-dsi driver, > add the description for this clock. > > Signed-off-by: Chris Zhong > Reviewed-by: Sean Paul > --- > > Changes in v4: > - remove "additional" > > Changes in

[PATCH v2 1/3] crypto: hw_random - Add new Exynos RNG driver

Replace existing hw_ranndom/exynos-rng driver with a new, reworked one. This is a driver for pseudo random number generator block which on Exynos4 chipsets must be seeded with some value. On newer Exynos5420 chipsets it might seed itself from true random number generator block but this is not

[PATCH v2 1/3] crypto: hw_random - Add new Exynos RNG driver

Replace existing hw_ranndom/exynos-rng driver with a new, reworked one. This is a driver for pseudo random number generator block which on Exynos4 chipsets must be seeded with some value. On newer Exynos5420 chipsets it might seed itself from true random number generator block but this is not

[PATCH v2 2/3] ARM: exynos_defconfig: Enable Exynos RNG and user-space crypto API

Enable the new Exynos pseudo random number generator driver and user-space API to access crypto algorithms and devices (not only RNG). Signed-off-by: Krzysztof Kozlowski --- arch/arm/configs/exynos_defconfig | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH v2 2/3] ARM: exynos_defconfig: Enable Exynos RNG and user-space crypto API

Enable the new Exynos pseudo random number generator driver and user-space API to access crypto algorithms and devices (not only RNG). Signed-off-by: Krzysztof Kozlowski --- arch/arm/configs/exynos_defconfig | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH v2 0/3] crypto: hw_random - Add new Exynos RNG driver

Hi, This is a follow up of my questions around exynos-rng [1]. Changes since v1: = 1. Re-work the code for seeding after system resume, following suggestions and review by Stephan Müller. The resume path was not tested. 2. Re-seed itself from time to time (every 100 ms),

[PATCH v2 0/3] crypto: hw_random - Add new Exynos RNG driver

Hi, This is a follow up of my questions around exynos-rng [1]. Changes since v1: = 1. Re-work the code for seeding after system resume, following suggestions and review by Stephan Müller. The resume path was not tested. 2. Re-seed itself from time to time (every 100 ms),

Re: [PATCH v4] tpm_crb: request and relinquish locality 0

Jarkko Sakkinen @ 2017-03-24 10:10 GMT: > This commit adds support for requesting and relinquishing locality 0 in > tpm_crb for the course of command transmission. > > In order to achieve this, two new callbacks are added to struct > tpm_class_ops: > > - request_locality > - relinquish_locality

Re: [PATCH v4] tpm_crb: request and relinquish locality 0

Jarkko Sakkinen @ 2017-03-24 10:10 GMT: > This commit adds support for requesting and relinquishing locality 0 in > tpm_crb for the course of command transmission. > > In order to achieve this, two new callbacks are added to struct > tpm_class_ops: > > - request_locality > - relinquish_locality

[PATCH 4.9 17/24] scsi: libiscsi: add lock around task lists to fix list corruption regression

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chris Leech commit 6f8830f5bbab16e54f261de187f3df4644a5b977 upstream. There's a rather long standing regression from the commit "libiscsi: Reduce locking contention in fast

[PATCH 4.9 17/24] scsi: libiscsi: add lock around task lists to fix list corruption regression

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chris Leech commit 6f8830f5bbab16e54f261de187f3df4644a5b977 upstream. There's a rather long standing regression from the commit "libiscsi: Reduce locking contention in fast path" Depending on

Re: [RFC PATCH v0.2] PCI: Add support for tango PCIe host bridge

On 23/03/17 23:40, Mason wrote: > On 23/03/2017 18:03, Mason wrote: > >> The host bridge actually supports 256 MSIs. >> >> IIUC, what you suggested on IRC is that I support 256 in the driver, >> and only read the status for *enabled* MSIs. >> >> Pseudo-code: >> >> for every 32-bit blob in the

Re: [RFC PATCH v0.2] PCI: Add support for tango PCIe host bridge

On 23/03/17 23:40, Mason wrote: > On 23/03/2017 18:03, Mason wrote: > >> The host bridge actually supports 256 MSIs. >> >> IIUC, what you suggested on IRC is that I support 256 in the driver, >> and only read the status for *enabled* MSIs. >> >> Pseudo-code: >> >> for every 32-bit blob in the

[PATCH v2] UBI: add debugfs file for tracking PEB state

From: Ben Shelton Add a file under debugfs to allow easy access to the erase count for each physical erase block on an UBI device. This is useful when debugging data integrity issues with UBIFS on NAND flash devices. Signed-off-by: Ben Shelton

[PATCH v2] UBI: add debugfs file for tracking PEB state

From: Ben Shelton Add a file under debugfs to allow easy access to the erase count for each physical erase block on an UBI device. This is useful when debugging data integrity issues with UBIFS on NAND flash devices. Signed-off-by: Ben Shelton Signed-off-by: Zach Brown v2: * If

Re: [PATCH v4 01/11] mm: x86: move _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1

On Mon, 2017-03-13 at 11:44 -0400, Zi Yan wrote: > From: Naoya Horiguchi > > pmd_present() checks _PAGE_PSE along with _PAGE_PRESENT to avoid > false negative return when it races with thp spilt > (during which _PAGE_PRESENT is temporary cleared.) I don't think that >

Re: [PATCH v4 01/11] mm: x86: move _PAGE_SWP_SOFT_DIRTY from bit 7 to bit 1

On Mon, 2017-03-13 at 11:44 -0400, Zi Yan wrote: > From: Naoya Horiguchi > > pmd_present() checks _PAGE_PSE along with _PAGE_PRESENT to avoid > false negative return when it races with thp spilt > (during which _PAGE_PRESENT is temporary cleared.) I don't think that > dropping _PAGE_PSE check in

[PATCH 4.10 24/27] gfs2: Avoid alignment hole in struct lm_lockname

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Gruenbacher commit 28ea06c46fbcab63fd9a55531387b7928a18a590 upstream. Commit 88ffbf3e03 switches to using rhashtables for glocks, hashing over the entire struct

[PATCH 4.10 22/27] target: Fix VERIFY_16 handling in sbc_parse_cdb

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Max Lohrmann commit 13603685c1f12c67a7a2427f00b63f39a2b6f7c9 upstream. As reported by Max, the Windows 2008 R2 chkdsk utility expects VERIFY_16 to be supported, and does

[PATCH 4.10 22/27] target: Fix VERIFY_16 handling in sbc_parse_cdb

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Max Lohrmann commit 13603685c1f12c67a7a2427f00b63f39a2b6f7c9 upstream. As reported by Max, the Windows 2008 R2 chkdsk utility expects VERIFY_16 to be supported, and does not handle the

[PATCH 4.10 24/27] gfs2: Avoid alignment hole in struct lm_lockname

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Gruenbacher commit 28ea06c46fbcab63fd9a55531387b7928a18a590 upstream. Commit 88ffbf3e03 switches to using rhashtables for glocks, hashing over the entire struct lm_lockname instead of

[PATCH 4.9 10/24] xprtrdma: Squelch kbuild sparse complaint

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chuck Lever commit eed50879d64ab1b9f76445dbab822e43a098b309 upstream. New complaint from kbuild for 4.9.y: net/sunrpc/xprtrdma/verbs.c:489:19: sparse: incompatible

[PATCH 4.9 10/24] xprtrdma: Squelch kbuild sparse complaint

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Chuck Lever commit eed50879d64ab1b9f76445dbab822e43a098b309 upstream. New complaint from kbuild for 4.9.y: net/sunrpc/xprtrdma/verbs.c:489:19: sparse: incompatible types in comparison

[PATCH 4.9 01/24] drm/vc4: Fix termination of the initial scan for branch targets.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Anholt commit 457e67a728696c4f8e6423c64e93def50530db9a upstream. The loop is scanning until the original max_ip (size of the BO), but we want to not examine any code

[PATCH 4.9 01/24] drm/vc4: Fix termination of the initial scan for branch targets.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Anholt commit 457e67a728696c4f8e6423c64e93def50530db9a upstream. The loop is scanning until the original max_ip (size of the BO), but we want to not examine any code after the PROG_END's

[PATCH 4.9 11/24] NFS prevent double free in async nfs4_exchange_id

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Olga Kornievskaia commit 63513232f8cd219dcaa5eafae028740ed3067d83 upstream. Since rpc_task is async, the release function should be called which will free the impl_id, scope,

[PATCH 4.10 18/27] target/pscsi: Fix TYPE_TAPE + TYPE_MEDIMUM_CHANGER export

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Bellinger commit a04e54f2c35823ca32d56afcd5cea5b783e2f51a upstream. The following fixes a divide by zero OOPs with TYPE_TAPE due to pscsi_tape_read_blocksize()

[PATCH 4.9 11/24] NFS prevent double free in async nfs4_exchange_id

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Olga Kornievskaia commit 63513232f8cd219dcaa5eafae028740ed3067d83 upstream. Since rpc_task is async, the release function should be called which will free the impl_id, scope, and owner. Trond

[PATCH 4.10 18/27] target/pscsi: Fix TYPE_TAPE + TYPE_MEDIMUM_CHANGER export

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Bellinger commit a04e54f2c35823ca32d56afcd5cea5b783e2f51a upstream. The following fixes a divide by zero OOPs with TYPE_TAPE due to pscsi_tape_read_blocksize() failing causing a zero

[PATCH 4.10 20/27] scsi: libiscsi: add lock around task lists to fix list corruption regression

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Chris Leech commit 6f8830f5bbab16e54f261de187f3df4644a5b977 upstream. There's a rather long standing regression from the commit "libiscsi: Reduce locking contention in fast

[PATCH 4.10 20/27] scsi: libiscsi: add lock around task lists to fix list corruption regression

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Chris Leech commit 6f8830f5bbab16e54f261de187f3df4644a5b977 upstream. There's a rather long standing regression from the commit "libiscsi: Reduce locking contention in fast path" Depending

[PATCH 4.9 12/24] cpufreq: Fix and clean up show_cpuinfo_cur_freq()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit 9b4f603e7a9f4282aec451063ffbbb8bb410dcd9 upstream. There is a missing newline in show_cpuinfo_cur_freq(), so add it, but while at it clean

[PATCH 4.9 12/24] cpufreq: Fix and clean up show_cpuinfo_cur_freq()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Rafael J. Wysocki commit 9b4f603e7a9f4282aec451063ffbbb8bb410dcd9 upstream. There is a missing newline in show_cpuinfo_cur_freq(), so add it, but while at it clean that function up somewhat

[PATCH 4.10 21/27] scsi: mpt3sas: Avoid sleeping in interrupt context

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 8893cf6cb1cf56334c05120e23092dbfc9423ebb upstream. Commit 669f044170d8 ("scsi: srp_transport: Move queuecommand() wait code to SCSI core")

[PATCH 4.10 26/27] cgroup/pids: remove spurious suspicious RCU usage warning

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 1d18c2747f937f1b5ec65ce6bf4ccb9ca1aea9e8 upstream. pids_can_fork() is special in that the css association is guaranteed to be stable throughout the function

[PATCH 4.10 21/27] scsi: mpt3sas: Avoid sleeping in interrupt context

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Bart Van Assche commit 8893cf6cb1cf56334c05120e23092dbfc9423ebb upstream. Commit 669f044170d8 ("scsi: srp_transport: Move queuecommand() wait code to SCSI core") can make

[PATCH 4.10 26/27] cgroup/pids: remove spurious suspicious RCU usage warning

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 1d18c2747f937f1b5ec65ce6bf4ccb9ca1aea9e8 upstream. pids_can_fork() is special in that the css association is guaranteed to be stable throughout the function and thus doesn't

[PATCH 4.9 14/24] md/raid1/10: fix potential deadlock

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shaohua Li commit 61eb2b43b99ebdc9bc6bc83d9792257b243e7cb3 upstream. Neil Brown pointed out a potential deadlock in raid 10 code with bio_split/chain. The raid1 code could have

[PATCH 4.9 14/24] md/raid1/10: fix potential deadlock

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Shaohua Li commit 61eb2b43b99ebdc9bc6bc83d9792257b243e7cb3 upstream. Neil Brown pointed out a potential deadlock in raid 10 code with bio_split/chain. The raid1 code could have the same issue,

[PATCH 4.9 18/24] target: Fix VERIFY_16 handling in sbc_parse_cdb

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Max Lohrmann commit 13603685c1f12c67a7a2427f00b63f39a2b6f7c9 upstream. As reported by Max, the Windows 2008 R2 chkdsk utility expects VERIFY_16 to be supported, and does

[PATCH 4.9 13/24] powerpc/boot: Fix zImage TOC alignment

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 97ee351b50a49717543533cfb85b4bf9d88c9680 upstream. Recent toolchains force the TOC to be 256 byte aligned. We need to enforce this alignment in the

[PATCH 4.9 18/24] target: Fix VERIFY_16 handling in sbc_parse_cdb

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Max Lohrmann commit 13603685c1f12c67a7a2427f00b63f39a2b6f7c9 upstream. As reported by Max, the Windows 2008 R2 chkdsk utility expects VERIFY_16 to be supported, and does not handle the

[PATCH 4.9 13/24] powerpc/boot: Fix zImage TOC alignment

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit 97ee351b50a49717543533cfb85b4bf9d88c9680 upstream. Recent toolchains force the TOC to be 256 byte aligned. We need to enforce this alignment in the zImage linker

[PATCH 4.9 20/24] gfs2: Avoid alignment hole in struct lm_lockname

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Gruenbacher commit 28ea06c46fbcab63fd9a55531387b7928a18a590 upstream. Commit 88ffbf3e03 switches to using rhashtables for glocks, hashing over the entire struct

Re: [PATCH v7 5/9] media: venus: vdec: add video decoder files

Le vendredi 24 mars 2017 à 15:41 +0100, Hans Verkuil a écrit : > > +static const struct venus_format vdec_formats[] = { > > + { > > + .pixfmt = V4L2_PIX_FMT_NV12, > > + .num_planes = 1, > > + .type = V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE, > > Just curious: is

[PATCH 4.9 20/24] gfs2: Avoid alignment hole in struct lm_lockname

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andreas Gruenbacher commit 28ea06c46fbcab63fd9a55531387b7928a18a590 upstream. Commit 88ffbf3e03 switches to using rhashtables for glocks, hashing over the entire struct lm_lockname instead of

Re: [PATCH v7 5/9] media: venus: vdec: add video decoder files

Le vendredi 24 mars 2017 à 15:41 +0100, Hans Verkuil a écrit : > > +static const struct venus_format vdec_formats[] = { > > + { > > + .pixfmt = V4L2_PIX_FMT_NV12, > > + .num_planes = 1, > > + .type = V4L2_BUF_TYPE_VIDEO_CAPTURE_MPLANE, > > Just curious: is

[PATCH 4.9 22/24] cgroup/pids: remove spurious suspicious RCU usage warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 1d18c2747f937f1b5ec65ce6bf4ccb9ca1aea9e8 upstream. pids_can_fork() is special in that the css association is guaranteed to be stable throughout the function

[PATCH 4.9 22/24] cgroup/pids: remove spurious suspicious RCU usage warning

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tejun Heo commit 1d18c2747f937f1b5ec65ce6bf4ccb9ca1aea9e8 upstream. pids_can_fork() is special in that the css association is guaranteed to be stable throughout the function and thus doesn't

[PATCH 4.9 03/24] give up on gcc ilog2() constant optimizations

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 474c90156c8dcc2fa815e6716cc9394d7930cb9c upstream. gcc-7 has an "optimization" pass that completely screws up, and generates the code

[PATCH 4.9 15/24] target/pscsi: Fix TYPE_TAPE + TYPE_MEDIMUM_CHANGER export

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Bellinger commit a04e54f2c35823ca32d56afcd5cea5b783e2f51a upstream. The following fixes a divide by zero OOPs with TYPE_TAPE due to pscsi_tape_read_blocksize()

[PATCH 4.9 03/24] give up on gcc ilog2() constant optimizations

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 474c90156c8dcc2fa815e6716cc9394d7930cb9c upstream. gcc-7 has an "optimization" pass that completely screws up, and generates the code expansion for the (impossible) case

[PATCH 4.9 15/24] target/pscsi: Fix TYPE_TAPE + TYPE_MEDIMUM_CHANGER export

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Nicholas Bellinger commit a04e54f2c35823ca32d56afcd5cea5b783e2f51a upstream. The following fixes a divide by zero OOPs with TYPE_TAPE due to pscsi_tape_read_blocksize() failing causing a zero

[PATCH 4.9 16/24] scsi: lpfc: Add shutdown method for kexec

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Anton Blanchard commit 85e8a23936ab3442de0c42da97d53b29f004ece1 upstream. We see lpfc devices regularly fail during kexec. Fix this by adding a shutdown method which mirrors

[PATCH 4.9 06/24] parisc: Optimize flush_kernel_vmap_range and invalidate_kernel_vmap_range

4.9-stable review patch. If anyone has any objections, please let me know. -- From: John David Anglin commit 316ec0624f951166daedbe446988ef92ae72b59f upstream. The previously submitted patch did not resolve the random segmentation faults observed on the

<    1   2   3   4   5   6   7   8   9   10   >