Re: [PATCH v3 1/2] doc: Add bindings document for Xilinx LogiCore PR Decoupler

On Fri, Mar 24, 2017 at 12:25:25PM -0500, Alan Tull wrote: > On Fri, Mar 24, 2017 at 10:23 AM, Moritz Fischer > wrote: > > On Fri, Mar 24, 2017 at 09:59:08AM -0500, Rob Herring wrote: > >> On Fri, Mar 17, 2017 at 01:11:12PM -0700, Moritz Fischer wrote: > >> > This adds the binding documentation

[PATCH 4.10 08/27] perf/core: Fix event inheritance on fork()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit e7cc4865f0f31698ef2f7aac01a50e78968985b7 upstream. While hunting for clues to a use-after-free, Oleg spotted that perf_event_init_context() can loose an error value with

[PATCH 4.10 17/27] md/raid1/10: fix potential deadlock

4.10-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.10 17/27] md/raid1/10: fix potential deadlock

4.10-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

[PATCH 4.4 27/30] isdn/gigaset: fix NULL-deref at probe

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 68c32f9c2a36d410aa242e661506e5b2c2764179 upstream. Make sure to check the number of endpoints to avoid dereferencing a NULL-pointer should a malicious

[PATCH 4.4 25/30] scsi: libiscsi: add lock around task lists to fix list corruption regression

4.4-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.4 27/30] isdn/gigaset: fix NULL-deref at probe

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 68c32f9c2a36d410aa242e661506e5b2c2764179 upstream. Make sure to check the number of endpoints to avoid dereferencing a NULL-pointer should a malicious device lack

[PATCH 4.4 25/30] scsi: libiscsi: add lock around task lists to fix list corruption regression

4.4-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

[PATCH 4.4 29/30] percpu: acquire pcpu_lock when updating pcpu_nr_empty_pop_pages

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tahsin Erdogan commit 320661b08dd6f1746d5c7ab4eb435ec64b97cd45 upstream. Update to pcpu_nr_empty_pop_pages in pcpu_alloc() is currently done without holding pcpu_lock. This

[PATCH 4.4 26/30] target: Fix VERIFY_16 handling in sbc_parse_cdb

4.4-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.4 29/30] percpu: acquire pcpu_lock when updating pcpu_nr_empty_pop_pages

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Tahsin Erdogan commit 320661b08dd6f1746d5c7ab4eb435ec64b97cd45 upstream. Update to pcpu_nr_empty_pop_pages in pcpu_alloc() is currently done without holding pcpu_lock. This can lead to bad

[PATCH 4.4 26/30] target: Fix VERIFY_16 handling in sbc_parse_cdb

4.4-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.4 03/30] crypto: ghash-clmulni - Fix load failure

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wang, Rui Y commit 3a020a723c65eb8ffa7c237faca26521a024e582 upstream. ghash_clmulni_intel fails to load on Linux 4.3+ with the following message: "modprobe: ERROR: could

[PATCH 4.4 03/30] crypto: ghash-clmulni - Fix load failure

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wang, Rui Y commit 3a020a723c65eb8ffa7c237faca26521a024e582 upstream. ghash_clmulni_intel fails to load on Linux 4.3+ with the following message: "modprobe: ERROR: could not insert

[PATCH 4.4 28/30] gfs2: Avoid alignment hole in struct lm_lockname

4.4-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.4 28/30] gfs2: Avoid alignment hole in struct lm_lockname

4.4-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.4 30/30] ext4: fix fencepost in s_first_meta_bg validation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Theodore Ts'o commit 2ba3e6e8afc9b6188b471f27cf2b5e3cf34e7af2 upstream. It is OK for s_first_meta_bg to be equal to the number of block group descriptor blocks. (It rarely

[PATCH 4.4 30/30] ext4: fix fencepost in s_first_meta_bg validation

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Theodore Ts'o commit 2ba3e6e8afc9b6188b471f27cf2b5e3cf34e7af2 upstream. It is OK for s_first_meta_bg to be equal to the number of block group descriptor blocks. (It rarely happens, but it

[PATCH 4.4 09/30] Drivers: hv: balloon: dont crash when memory is added in non-sorted order

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Kuznetsov commit 77c0c9735bc0ba5898e637a3a20d6bcb50e3f67d upstream. When we iterate through all HA regions in handle_pg_range() we have an assumption that all these

[PATCH 4.4 09/30] Drivers: hv: balloon: dont crash when memory is added in non-sorted order

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Kuznetsov commit 77c0c9735bc0ba5898e637a3a20d6bcb50e3f67d upstream. When we iterate through all HA regions in handle_pg_range() we have an assumption that all these regions are sorted

[PATCH 4.4 07/30] ACPI / video: skip evaluating _DOD when it does not exist

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Hung commit e34fbbac669de0b7fb7803929d0477f35f6e2833 upstream. Some system supports hybrid graphics and its discrete VGA does not have any connectors and

[PATCH 4.4 06/30] cxlflash: Increase cmd_per_lun for better throughput

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Manoj N. Kumar commit 83430833b4d4a9c9b23964babbeb1f36450f8136 upstream. With the current value of cmd_per_lun at 16, the throughput over a single adapter is limited

Re: locking/atomic: Introduce atomic_try_cmpxchg()

On Fri, Mar 24, 2017 at 07:00:25PM +0100, Peter Zijlstra wrote: > static inline bool try_cmpxchg2(unsigned int *ptr, unsigned int *val, > unsigned int new) > { > unsigned int old = *val; > bool success; > > asm volatile goto("lock cmpxchgl %[new], %[ptr]; " >

[PATCH 4.4 07/30] ACPI / video: skip evaluating _DOD when it does not exist

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Alex Hung commit e34fbbac669de0b7fb7803929d0477f35f6e2833 upstream. Some system supports hybrid graphics and its discrete VGA does not have any connectors and therefore has no _DOD method.

[PATCH 4.4 06/30] cxlflash: Increase cmd_per_lun for better throughput

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Manoj N. Kumar commit 83430833b4d4a9c9b23964babbeb1f36450f8136 upstream. With the current value of cmd_per_lun at 16, the throughput over a single adapter is limited to around 150kIOPS.

Re: locking/atomic: Introduce atomic_try_cmpxchg()

On Fri, Mar 24, 2017 at 07:00:25PM +0100, Peter Zijlstra wrote: > static inline bool try_cmpxchg2(unsigned int *ptr, unsigned int *val, > unsigned int new) > { > unsigned int old = *val; > bool success; > > asm volatile goto("lock cmpxchgl %[new], %[ptr]; " >

[PATCH 4.4 08/30] pinctrl: cherryview: Do not mask all interrupts in probe

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mika Westerberg commit bcb48cca23ec9852739e4a464307fa29515bbe48 upstream. The Cherryview GPIO controller has 8 or 16 wires connected to the I/O-APIC which can

[PATCH 4.4 08/30] pinctrl: cherryview: Do not mask all interrupts in probe

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Mika Westerberg commit bcb48cca23ec9852739e4a464307fa29515bbe48 upstream. The Cherryview GPIO controller has 8 or 16 wires connected to the I/O-APIC which can be used directly by the

[PATCH 4.4 10/30] Drivers: hv: avoid vfree() on crash

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Kuznetsov commit a9f61ca793becabdefab03b77568d6c6f8c1bc79 upstream. When we crash from NMI context (e.g. after NMI injection from host when 'sysctl -w

[PATCH 4.4 10/30] Drivers: hv: avoid vfree() on crash

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Vitaly Kuznetsov commit a9f61ca793becabdefab03b77568d6c6f8c1bc79 upstream. When we crash from NMI context (e.g. after NMI injection from host when 'sysctl -w kernel.unknown_nmi_panic=1' is

[PATCH 4.4 04/30] crypto: cryptd - Assign statesize properly

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wang, Rui Y commit 1a07834024dfca5c4bed5de8f8714306e0a11836 upstream. cryptd_create_hash() fails by returning -EINVAL. It is because after 8996eafdc ("crypto: ahash -

[PATCH 4.4 00/30] 4.4.57-stable review

This is the start of the stable review cycle for the 4.4.57 release. There are 30 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 Sun Mar 26 15:12:02 UTC 2017. Anything

[PATCH 4.4 04/30] crypto: cryptd - Assign statesize properly

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wang, Rui Y commit 1a07834024dfca5c4bed5de8f8714306e0a11836 upstream. cryptd_create_hash() fails by returning -EINVAL. It is because after 8996eafdc ("crypto: ahash - ensure statesize is

[PATCH 4.4 00/30] 4.4.57-stable review

This is the start of the stable review cycle for the 4.4.57 release. There are 30 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 Sun Mar 26 15:12:02 UTC 2017. Anything

[PATCH 4.4 05/30] crypto: mcryptd - Fix load failure

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wang, Rui Y commit ddef482420b1ba8ec45e6123a7e8d3f67b21e5e3 upstream. mcryptd_create_hash() fails by returning -EINVAL, causing any driver using mcryptd to fail to load.

[PATCH 4.4 11/30] xen/qspinlock: Dont kick CPU if IRQ is not initialized

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ross Lagerwall commit 707e59ba494372a90d245f18b0c78982caa88e48 upstream. The following commit: 1fb3a8b2cfb2 ("xen/spinlock: Fix locking path engaging too soon

[PATCH 4.4 05/30] crypto: mcryptd - Fix load failure

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Wang, Rui Y commit ddef482420b1ba8ec45e6123a7e8d3f67b21e5e3 upstream. mcryptd_create_hash() fails by returning -EINVAL, causing any driver using mcryptd to fail to load. It is because it needs

[PATCH 4.4 11/30] xen/qspinlock: Dont kick CPU if IRQ is not initialized

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Ross Lagerwall commit 707e59ba494372a90d245f18b0c78982caa88e48 upstream. The following commit: 1fb3a8b2cfb2 ("xen/spinlock: Fix locking path engaging too soon under PVHVM.") ... moved the

[PATCH 4.4 18/30] give up on gcc ilog2() constant optimizations

4.4-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.4 18/30] give up on gcc ilog2() constant optimizations

4.4-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.4 14/30] drm/amdgpu: add missing irq.h include

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dave Airlie commit e9c5e7402dad6f4f04c2430db6f283512bcd4392 upstream. this fixes the build on arm. Signed-off-by: Dave Airlie Cc: Sumit Semwal

[PATCH 4.4 14/30] drm/amdgpu: add missing irq.h include

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Dave Airlie commit e9c5e7402dad6f4f04c2430db6f283512bcd4392 upstream. this fixes the build on arm. Signed-off-by: Dave Airlie Cc: Sumit Semwal Signed-off-by: Greg Kroah-Hartman ---

[PATCH 4.10 25/27] percpu: acquire pcpu_lock when updating pcpu_nr_empty_pop_pages

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tahsin Erdogan commit 320661b08dd6f1746d5c7ab4eb435ec64b97cd45 upstream. Update to pcpu_nr_empty_pop_pages in pcpu_alloc() is currently done without holding pcpu_lock. This

Re: [PATCH 5/5] firmware: google memconsole: Add ARM/ARM64 support

On Fri, Mar 24, 2017 at 12:28:59PM +, Mark Rutland wrote: > On Thu, Mar 23, 2017 at 10:04:29PM +0100, Thierry Escande wrote: > > +static const struct of_device_id coreboot_of_match[] = { > > + { .compatible = "coreboot" }, > > + {}, > > +}; > > + > > +static struct platform_driver

[PATCH 4.10 25/27] percpu: acquire pcpu_lock when updating pcpu_nr_empty_pop_pages

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tahsin Erdogan commit 320661b08dd6f1746d5c7ab4eb435ec64b97cd45 upstream. Update to pcpu_nr_empty_pop_pages in pcpu_alloc() is currently done without holding pcpu_lock. This can lead to bad

Re: [PATCH 5/5] firmware: google memconsole: Add ARM/ARM64 support

On Fri, Mar 24, 2017 at 12:28:59PM +, Mark Rutland wrote: > On Thu, Mar 23, 2017 at 10:04:29PM +0100, Thierry Escande wrote: > > +static const struct of_device_id coreboot_of_match[] = { > > + { .compatible = "coreboot" }, > > + {}, > > +}; > > + > > +static struct platform_driver

[PATCH 4.9 09/24] perf/core: Fix event inheritance on fork()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit e7cc4865f0f31698ef2f7aac01a50e78968985b7 upstream. While hunting for clues to a use-after-free, Oleg spotted that perf_event_init_context() can

[PATCH 4.9 09/24] perf/core: Fix event inheritance on fork()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Peter Zijlstra commit e7cc4865f0f31698ef2f7aac01a50e78968985b7 upstream. While hunting for clues to a use-after-free, Oleg spotted that perf_event_init_context() can loose an error value with

[PATCH 4.9 04/24] qla2xxx: Fix memory leak for abts processing

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit ae940f2c472a62904dc18234de5cf3ed28f195ee upstream. Signed-off-by: Quinn Tran Signed-off-by: Himanshu Madhani

[PATCH 4.10 23/27] isdn/gigaset: fix NULL-deref at probe

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 68c32f9c2a36d410aa242e661506e5b2c2764179 upstream. Make sure to check the number of endpoints to avoid dereferencing a NULL-pointer should a malicious

[PATCH 4.9 04/24] qla2xxx: Fix memory leak for abts processing

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit ae940f2c472a62904dc18234de5cf3ed28f195ee upstream. Signed-off-by: Quinn Tran Signed-off-by: Himanshu Madhani Signed-off-by: Nicholas Bellinger Signed-off-by: Greg

[PATCH 4.10 23/27] isdn/gigaset: fix NULL-deref at probe

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 68c32f9c2a36d410aa242e661506e5b2c2764179 upstream. Make sure to check the number of endpoints to avoid dereferencing a NULL-pointer should a malicious device lack

[PATCH 4.10 12/27] cpufreq: Fix and clean up show_cpuinfo_cur_freq()

4.10-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.10 12/27] cpufreq: Fix and clean up show_cpuinfo_cur_freq()

4.10-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 16/27] hwrng: omap - Do not access INTMASK_REG on EIP76

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit b985735be7afea3a5e0570ce2ea0b662c0e12e19 upstream. The INTMASK_REG register does not exist on EIP76. Due to this, the call:

[PATCH 4.10 16/27] hwrng: omap - Do not access INTMASK_REG on EIP76

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit b985735be7afea3a5e0570ce2ea0b662c0e12e19 upstream. The INTMASK_REG register does not exist on EIP76. Due to this, the call: omap_rng_write(priv, RNG_INTMASK_REG,

[PATCH 4.10 02/27] qla2xxx: Fix memory leak for abts processing

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit ae940f2c472a62904dc18234de5cf3ed28f195ee upstream. Signed-off-by: Quinn Tran Signed-off-by: Himanshu Madhani

[PATCH 4.10 04/27] parisc: Optimize flush_kernel_vmap_range and invalidate_kernel_vmap_range

4.10-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

[PATCH 4.10 14/27] hwrng: omap - write registers after enabling the clock

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit 45c2fdde01299b02a6e3225e848598a3c1e55539 upstream. Commit 383212425c926 ("hwrng: omap - Add device variant for SafeXcel IP-76

[PATCH 4.10 02/27] qla2xxx: Fix memory leak for abts processing

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Quinn Tran commit ae940f2c472a62904dc18234de5cf3ed28f195ee upstream. Signed-off-by: Quinn Tran Signed-off-by: Himanshu Madhani Signed-off-by: Nicholas Bellinger Signed-off-by: Greg

[PATCH 4.10 04/27] parisc: Optimize flush_kernel_vmap_range and invalidate_kernel_vmap_range

4.10-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 phantom buildd

[PATCH 4.10 14/27] hwrng: omap - write registers after enabling the clock

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit 45c2fdde01299b02a6e3225e848598a3c1e55539 upstream. Commit 383212425c926 ("hwrng: omap - Add device variant for SafeXcel IP-76 found in Armada 8K") added support for

[PATCH 4.10 01/27] give up on gcc ilog2() constant optimizations

4.10-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.10 01/27] give up on gcc ilog2() constant optimizations

4.10-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.10 13/27] powerpc/boot: Fix zImage TOC alignment

4.10-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

[PATCH 4.10 15/27] hwrng: omap - use devm_clk_get() instead of of_clk_get()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit 761c2510283066324cab7859930777ee34cbca78 upstream. The omap-rng driver currently uses of_clk_get() to get a reference to the

[PATCH 4.10 13/27] powerpc/boot: Fix zImage TOC alignment

4.10-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.10 15/27] hwrng: omap - use devm_clk_get() instead of of_clk_get()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Petazzoni commit 761c2510283066324cab7859930777ee34cbca78 upstream. The omap-rng driver currently uses of_clk_get() to get a reference to the clock, but never releases that reference.

[PATCH 4.10 10/27] xprtrdma: Squelch kbuild sparse complaint

4.10-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.10 11/27] NFS prevent double free in async nfs4_exchange_id

4.10-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,

[PATCH 4.10 10/27] xprtrdma: Squelch kbuild sparse complaint

4.10-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.10 11/27] NFS prevent double free in async nfs4_exchange_id

4.10-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.

[PATCH 4.10 00/27] 4.10.6-stable review

This is the start of the stable review cycle for the 4.10.6 release. There are 27 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 Sun Mar 26 15:12:13 UTC 2017. Anything

[PATCH 4.10 00/27] 4.10.6-stable review

This is the start of the stable review cycle for the 4.10.6 release. There are 27 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 Sun Mar 26 15:12:13 UTC 2017. Anything

Re: [PATCH 4/5] firmware: Add coreboot device tree binding documentation

Hi Mark, Julius can correct me if I'm wrong on any of this, but a quick note that probably should have prefaced this: These bindings were submitted years go https://patchwork.ozlabs.org/patch/359672/ [PATCH] firmware: Add device tree binding for coreboot discussed, and resubmitted seemingly

Re: [PATCH 4/5] firmware: Add coreboot device tree binding documentation

Hi Mark, Julius can correct me if I'm wrong on any of this, but a quick note that probably should have prefaced this: These bindings were submitted years go https://patchwork.ozlabs.org/patch/359672/ [PATCH] firmware: Add device tree binding for coreboot discussed, and resubmitted seemingly

Re: [PATCH v12 09/10] perf/amd/iommu: Introduce amd_iommu-specific struct in struct hw_perf_event

On Wed, Mar 22, 2017 at 02:02:41AM -0500, Suravee Suthikulpanit wrote: > From: Suravee Suthikulpanit > > Current AMD IOMMU Perf PMU inappropriately uses hardware struct > inside the union inside the struct hw_perf_event, mainly the use of > extra_reg. > > Instead,

Re: [PATCH v12 09/10] perf/amd/iommu: Introduce amd_iommu-specific struct in struct hw_perf_event

On Wed, Mar 22, 2017 at 02:02:41AM -0500, Suravee Suthikulpanit wrote: > From: Suravee Suthikulpanit > > Current AMD IOMMU Perf PMU inappropriately uses hardware struct > inside the union inside the struct hw_perf_event, mainly the use of > extra_reg. > > Instead, introduce amd_iommu-specific

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

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 wrote: > >> If you would consider an alternative implementation where we scrap >> the

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

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 wrote: > >> If you would consider an alternative implementation where we scrap >> the

[PATCH] x86/intel_rdt: Implement "update" mode when writing schemata file

From: Tony Luck The schemata file can have multiple lines and it is cumbersome to update from shell scripts. Remove code that requires that the user provide values for every resource (in the right order). If the user provides values for just a few resources, update them

[PATCH] x86/intel_rdt: Implement "update" mode when writing schemata file

From: Tony Luck The schemata file can have multiple lines and it is cumbersome to update from shell scripts. Remove code that requires that the user provide values for every resource (in the right order). If the user provides values for just a few resources, update them and leave the rest

[PATCH v2] lkdtm: add bad USER_DS test

This adds CORRUPT_USER_DS to check that the get_fs() test on syscall return (via __VERIFY_PRE_USERMODE_STATE) still sees USER_DS. Since trying to deal with values other than USER_DS and KERNEL_DS across all architectures in a safe way is not sensible, this sets KERNEL_DS, but since that could be

[PATCH v2] lkdtm: add bad USER_DS test

This adds CORRUPT_USER_DS to check that the get_fs() test on syscall return (via __VERIFY_PRE_USERMODE_STATE) still sees USER_DS. Since trying to deal with values other than USER_DS and KERNEL_DS across all architectures in a safe way is not sensible, this sets KERNEL_DS, but since that could be

Re: locking/atomic: Introduce atomic_try_cmpxchg()

On Fri, Mar 24, 2017 at 6:23 PM, 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 6:23 PM, 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 0/3] minitty: a minimal TTY layer alternative for embedded systems

On Fri, 24 Mar 2017, Greg Kroah-Hartman wrote: > On Fri, Mar 24, 2017 at 08:31:45AM -0400, Nicolas Pitre wrote: > > That's the crux of the argument: touching the current TTY layer is NOT > > going to help keeping it stable. Here, not only I did remove features, > > but the ones I kept were

Re: [PATCH 0/3] minitty: a minimal TTY layer alternative for embedded systems

On Fri, 24 Mar 2017, Greg Kroah-Hartman wrote: > On Fri, Mar 24, 2017 at 08:31:45AM -0400, Nicolas Pitre wrote: > > That's the crux of the argument: touching the current TTY layer is NOT > > going to help keeping it stable. Here, not only I did remove features, > > but the ones I kept were

Re: [PATCH v2 06/18] arm64: arch_timer: Add infrastructure for multiple erratum detection methods

On Mon, Mar 20, 2017 at 11:48 AM, Marc Zyngier wrote: > We're currently stuck with DT when it comes to handling errata, which > is pretty restrictive. In order to make things more flexible, let's > introduce an infrastructure that could support alternative discovery >

Re: [PATCH v2 06/18] arm64: arch_timer: Add infrastructure for multiple erratum detection methods

On Mon, Mar 20, 2017 at 11:48 AM, Marc Zyngier wrote: > We're currently stuck with DT when it comes to handling errata, which > is pretty restrictive. In order to make things more flexible, let's > introduce an infrastructure that could support alternative discovery > methods. No change in

Re: [PATCH v2] ASoC: imx-wm8960: Let codec driver enable/disable its MCLK

On Fri, Mar 24, 2017 at 11:14:48AM +0200, Daniel Baluta wrote: > From: Daniel Baluta > > WM8962 needs its MCLK when powerup in wm8962_resume(). Thus it's better > to control the MCLK in codec driver. Thus remove the clock enable in > machine driver accordingly. > > While

Re: [PATCH v2] ASoC: imx-wm8960: Let codec driver enable/disable its MCLK

On Fri, Mar 24, 2017 at 11:14:48AM +0200, Daniel Baluta wrote: > From: Daniel Baluta > > WM8962 needs its MCLK when powerup in wm8962_resume(). Thus it's better > to control the MCLK in codec driver. Thus remove the clock enable in > machine driver accordingly. > > While at it, get rid of

Re: [PATCH] lkdtm: add bad USER_DS test

On Fri, Mar 24, 2017 at 8:24 AM, Christian Borntraeger wrote: > On 03/24/2017 04:17 PM, Thomas Garnier wrote: >> On Fri, Mar 24, 2017 at 1:14 AM, Heiko Carstens >> wrote: >>> On Thu, Mar 23, 2017 at 01:34:19PM -0700, Kees Cook wrote: This

Re: [PATCH] lkdtm: add bad USER_DS test

On Fri, Mar 24, 2017 at 8:24 AM, Christian Borntraeger wrote: > On 03/24/2017 04:17 PM, Thomas Garnier wrote: >> On Fri, Mar 24, 2017 at 1:14 AM, Heiko Carstens >> wrote: >>> On Thu, Mar 23, 2017 at 01:34:19PM -0700, Kees Cook wrote: This adds CORRUPT_USER_DS to check that the get_fs() test

[PATCH v3] HV: properly delay KVP packets when negotiation is in progress

From: Long Li The host may send multiple negotiation packets (due to timeout) before the KVP user-mode daemon is connected. We need to defer processing those packets until the daemon is negotiated and connected. It's okay for guest to respond to all negotiation packets.

[PATCH v3] HV: properly delay KVP packets when negotiation is in progress

From: Long Li The host may send multiple negotiation packets (due to timeout) before the KVP user-mode daemon is connected. We need to defer processing those packets until the daemon is negotiated and connected. It's okay for guest to respond to all negotiation packets. In addition, the host

Re: deadlock in synchronize_srcu() in debugfs?

On Fri, Mar 24, 2017 at 10:24:46AM +0100, Johannes Berg wrote: > Hi, > > On Fri, 2017-03-24 at 09:56 +0100, Johannes Berg wrote: > > On Thu, 2017-03-23 at 16:29 +0100, Johannes Berg wrote: > > > Isn't it possible for the following to happen? > > > > > > CPU1

Re: deadlock in synchronize_srcu() in debugfs?

On Fri, Mar 24, 2017 at 10:24:46AM +0100, Johannes Berg wrote: > Hi, > > On Fri, 2017-03-24 at 09:56 +0100, Johannes Berg wrote: > > On Thu, 2017-03-23 at 16:29 +0100, Johannes Berg wrote: > > > Isn't it possible for the following to happen? > > > > > > CPU1

[PATCH 4/7] mfd: cros_ec: Get rid of cros_ec_check_features from cros_ec_dev.

The cros_ec_dev driver should be used only to expose the Chrome OS Embedded Controller to user-space and should not be used to add MFD devices by calling mfd_add_devices. This patch moves this logic to the MFD cros_ec driver and removes the MFD bits from the character device driver. Also makes

[PATCH 0/7] mfd: cros-ec: Some fixes and improvements.

Dear all, This is another patch series to fix and improve some cros-ec mfd related things. * 1/7 mfd: cros-ec: Fix host command buffer size This patch is a FIX, and I think that would be interesting see it merged in this release cycle. This should go through the MFD tree and can be picked

<    3   4   5   6   7   8   9   10   11   12   >