Re: [PATCH 4.10 000/129] 4.10.16-stable review

On 05/11/2017 08:10 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.10.16 release. > There are 129 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

Re: [PATCH 4.10 000/129] 4.10.16-stable review

On 05/11/2017 08:10 AM, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.10.16 release. > There are 129 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

[PATCH 4.11 28/28] block: get rid of blk_integrity_revalidate()

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit 19b7ccf8651df09d274671b53039c672a52ad84d upstream. Commit 25520d55cdb6 ("block: Inline blk_integrity in struct gendisk") introduced

[PATCH 4.11 28/28] block: get rid of blk_integrity_revalidate()

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Ilya Dryomov commit 19b7ccf8651df09d274671b53039c672a52ad84d upstream. Commit 25520d55cdb6 ("block: Inline blk_integrity in struct gendisk") introduced blk_integrity_revalidate(), which seems

[PATCH 4.10 001/129] 9p: fix a potential acl leak

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang commit b5c66bab72a6a65edb15beb60b90d3cb84c5763b upstream. posix_acl_update_mode() could possibly clear 'acl', if so we leak the memory pointed by 'acl'.

[PATCH 4.11 11/28] bpf: enhance verifier to understand stack pointer arithmetic

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ Upstream commit 332270fdc8b6fba07d059a9ad44df9e1a2ad4529 ] llvm 4.0 and above generates the code like below: 440: (b7) r1 = 15 441: (05) goto pc+73 515:

[PATCH 4.10 001/129] 9p: fix a potential acl leak

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang commit b5c66bab72a6a65edb15beb60b90d3cb84c5763b upstream. posix_acl_update_mode() could possibly clear 'acl', if so we leak the memory pointed by 'acl'. Save this pointer before

[PATCH 4.11 11/28] bpf: enhance verifier to understand stack pointer arithmetic

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Yonghong Song [ Upstream commit 332270fdc8b6fba07d059a9ad44df9e1a2ad4529 ] llvm 4.0 and above generates the code like below: 440: (b7) r1 = 15 441: (05) goto pc+73 515: (79) r6 = *(u64

[PATCH 4.10 010/129] cpupower: Fix turbo frequency reporting for pre-Sandy Bridge cores

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 4cca0457686e4ee1677d69469e4ddfd94d389a80 upstream. The switch that conditionally sets CPUPOWER_CAP_HAS_TURBO_RATIO and CPUPOWER_CAP_IS_SNB flags is

[PATCH 4.10 010/129] cpupower: Fix turbo frequency reporting for pre-Sandy Bridge cores

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit 4cca0457686e4ee1677d69469e4ddfd94d389a80 upstream. The switch that conditionally sets CPUPOWER_CAP_HAS_TURBO_RATIO and CPUPOWER_CAP_IS_SNB flags is missing a break, so

Re: [PATCH 2/2] of: reserved_mem: fix 'const' annotation

On Thu, May 11, 2017 at 4:50 PM, Rob Herring wrote: > On Thu, May 11, 2017 at 7:24 AM, Arnd Bergmann wrote: >> It's the pointer that is supposed to be const, not the return >> type of the function. >> >> drivers/of/of_reserved_mem.c: In function

Re: [PATCH 2/2] of: reserved_mem: fix 'const' annotation

On Thu, May 11, 2017 at 4:50 PM, Rob Herring wrote: > On Thu, May 11, 2017 at 7:24 AM, Arnd Bergmann wrote: >> It's the pointer that is supposed to be const, not the return >> type of the function. >> >> drivers/of/of_reserved_mem.c: In function '__reserved_mem_init_node': >>

[PATCH 4.11 01/28] dm ioctl: prevent stack leak in dm ioctl call

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Salido commit 4617f564c06117c7d1b611be49521a4430042287 upstream. When calling a dm ioctl that doesn't process any data (IOCTL_FLAGS_NO_PARAMS), the contents of the

[PATCH 4.11 10/28] geneve: fix incorrect setting of UDP checksum flag

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Girish Moodalbail [ Upstream commit 5e0740c445e6ae4026f5e52456ff8d0be9725183 ] Creating a geneve link with 'udpcsum' set results in a creation of link for which

[PATCH 4.11 01/28] dm ioctl: prevent stack leak in dm ioctl call

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Salido commit 4617f564c06117c7d1b611be49521a4430042287 upstream. When calling a dm ioctl that doesn't process any data (IOCTL_FLAGS_NO_PARAMS), the contents of the data field in struct

[PATCH 4.11 10/28] geneve: fix incorrect setting of UDP checksum flag

4.11-stable review patch. If anyone has any objections, please let me know. -- From: Girish Moodalbail [ Upstream commit 5e0740c445e6ae4026f5e52456ff8d0be9725183 ] Creating a geneve link with 'udpcsum' set results in a creation of link for which UDP checksum will NOT be

[PATCH 4.10 011/129] powerpc/perf: Fix perf_get_data_addr() for power9 DD1

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Madhavan Srinivasan commit f04d108029063a8a67528a88449c412aecf4d3d8 upstream. Power9 DD1 do not support PMU_HAS_SIER flag and sdsync in perf_get_data_addr() defaults

[PATCH 4.10 011/129] powerpc/perf: Fix perf_get_data_addr() for power9 DD1

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Madhavan Srinivasan commit f04d108029063a8a67528a88449c412aecf4d3d8 upstream. Power9 DD1 do not support PMU_HAS_SIER flag and sdsync in perf_get_data_addr() defaults to MMCRA_SDSYNC which is

[PATCH 4.10 014/129] powerpc/mm: Fixup wrong LPCR_VRMASD value

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Aneesh Kumar K.V commit 4ab2537c4204b976e4ca350bbdc193b4649cad28 upstream. In commit a4b349540a26af ("powerpc/mm: Cleanup LPCR defines") we updated

[PATCH 4.10 013/129] powerpc/perf: Avoid FAB_*_MATCH checks for power9

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Madhavan Srinivasan commit 78a16d9fc1206e1a484b6ac96348756f3846bfea upstream. Since power9 does not support FAB_*_MATCH bits in MMCR1, avoid these checks for power9.

[PATCH 4.10 014/129] powerpc/mm: Fixup wrong LPCR_VRMASD value

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Aneesh Kumar K.V commit 4ab2537c4204b976e4ca350bbdc193b4649cad28 upstream. In commit a4b349540a26af ("powerpc/mm: Cleanup LPCR defines") we updated LPCR_VRMASD wrongly as below. -#define

[PATCH 4.10 013/129] powerpc/perf: Avoid FAB_*_MATCH checks for power9

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Madhavan Srinivasan commit 78a16d9fc1206e1a484b6ac96348756f3846bfea upstream. Since power9 does not support FAB_*_MATCH bits in MMCR1, avoid these checks for power9. For this, patch factor

[PATCH 4.10 015/129] powerpc/powernv: Fix opal_exit tracepoint opcode

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit a7e0fb6c2029a780444d09560f739e020d54fe4d upstream. Currently the opal_exit tracepoint usually shows the opcode as 0: -0 [047] d.h.

[PATCH 4.10 017/129] powerpc/ftrace: Fix confusing help text for DISABLE_MPROFILE_KERNEL

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Anton Blanchard commit 496e9cb5b2aa2ba303d2bbd08518f9be2219ab4b upstream. The final paragraph of the help text is reversed. We want to enable this option by default, and

[PATCH 4.10 015/129] powerpc/powernv: Fix opal_exit tracepoint opcode

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Michael Ellerman commit a7e0fb6c2029a780444d09560f739e020d54fe4d upstream. Currently the opal_exit tracepoint usually shows the opcode as 0: -0 [047] d.h. 635.654292: opal_entry:

[PATCH 4.10 017/129] powerpc/ftrace: Fix confusing help text for DISABLE_MPROFILE_KERNEL

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Anton Blanchard commit 496e9cb5b2aa2ba303d2bbd08518f9be2219ab4b upstream. The final paragraph of the help text is reversed. We want to enable this option by default, and disable it if the

[PATCH 4.10 020/129] power: supply: bq24190_charger: Fix irq trigger to IRQF_TRIGGER_FALLING

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit 767eee362fd72bb2ca44cc80419ca4b38c6d8369 upstream. The interrupt signal is TRIGGER_FALLING. This is is specified in the data sheet PIN FUNCTIONS:

[PATCH 4.10 020/129] power: supply: bq24190_charger: Fix irq trigger to IRQF_TRIGGER_FALLING

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit 767eee362fd72bb2ca44cc80419ca4b38c6d8369 upstream. The interrupt signal is TRIGGER_FALLING. This is is specified in the data sheet PIN FUNCTIONS: "The INT pin sends active

Re: [PATCH v3 1/2] selinux: add brief info to policydb

On 5/11/2017 5:59 AM, Sebastien Buisson wrote: > Add policybrief field to struct policydb. It holds a brief info > of the policydb, in the following form: > <0 or 1 for enforce>:<0 or 1 for checkreqprot>:= > Policy brief is computed every time the policy is loaded, and when > enforce or

Re: [PATCH v3 1/2] selinux: add brief info to policydb

On 5/11/2017 5:59 AM, Sebastien Buisson wrote: > Add policybrief field to struct policydb. It holds a brief info > of the policydb, in the following form: > <0 or 1 for enforce>:<0 or 1 for checkreqprot>:= > Policy brief is computed every time the policy is loaded, and when > enforce or

[PATCH 4.10 021/129] power: supply: bq24190_charger: Call set_mode_host() on pm_resume()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit e05ad7e0741ce0505e1df157c62b22b95172bb97 upstream. pm_resume() does a register_reset() which clears charger host mode. Fix by calling

[PATCH 4.10 021/129] power: supply: bq24190_charger: Call set_mode_host() on pm_resume()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit e05ad7e0741ce0505e1df157c62b22b95172bb97 upstream. pm_resume() does a register_reset() which clears charger host mode. Fix by calling set_mode_host() after the reset.

[PATCH 4.10 023/129] power: supply: bq24190_charger: Call power_supply_changed() for relevant component

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit 2d9fee6a42ea170e4378b3363a7ad385d0e67281 upstream. We wrongly get uevents for bq24190-charger and bq24190-battery on every register change. Fix by

[PATCH 4.10 023/129] power: supply: bq24190_charger: Call power_supply_changed() for relevant component

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit 2d9fee6a42ea170e4378b3363a7ad385d0e67281 upstream. We wrongly get uevents for bq24190-charger and bq24190-battery on every register change. Fix by checking the association

[PATCH 4.10 024/129] power: supply: bq24190_charger: Dont read fault register outside irq_handle_thread()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit 68abfb8015832ddf728b911769659468efaf8bd9 upstream. Caching the fault register after a single I2C read may not keep an accurate value. Fix by doing

[PATCH 4.10 024/129] power: supply: bq24190_charger: Dont read fault register outside irq_handle_thread()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit 68abfb8015832ddf728b911769659468efaf8bd9 upstream. Caching the fault register after a single I2C read may not keep an accurate value. Fix by doing two reads in

[PATCH 4.10 027/129] arm: dts: qcom: Fix ipq board clock rates

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit 06dbf468a2c42bf6c327a8eaf11ecb3ea96196f9 upstream. The ipq board has these rates as 25MHz, and not 19.2 and 27. I copy/pasted from other boards that

[PATCH 4.10 028/129] arm64: remove wrong CONFIG_PROC_SYSCTL ifdef

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Juri Lelli commit fe0a7ef74d1f65b86820a54636323df2b31e0c3f upstream. The sysfs cpu_capacity entry for each CPU has nothing to do with PROC_FS, nor it's in /proc/sys path.

[PATCH 4.10 027/129] arm: dts: qcom: Fix ipq board clock rates

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit 06dbf468a2c42bf6c327a8eaf11ecb3ea96196f9 upstream. The ipq board has these rates as 25MHz, and not 19.2 and 27. I copy/pasted from other boards that have those rates but

[PATCH 4.10 028/129] arm64: remove wrong CONFIG_PROC_SYSCTL ifdef

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Juri Lelli commit fe0a7ef74d1f65b86820a54636323df2b31e0c3f upstream. The sysfs cpu_capacity entry for each CPU has nothing to do with PROC_FS, nor it's in /proc/sys path. Remove such ifdef.

[PATCH 4.10 026/129] arm64: dts: r8a7795: Mark EthernetAVB device node disabled

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit 0d1390ff283f6c38595288e7f74da6829896b8b7 upstream. Device nodes representing I/O devices should be marked disabled in the SoC-specific DTS,

[PATCH 4.10 026/129] arm64: dts: r8a7795: Mark EthernetAVB device node disabled

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Geert Uytterhoeven commit 0d1390ff283f6c38595288e7f74da6829896b8b7 upstream. Device nodes representing I/O devices should be marked disabled in the SoC-specific DTS, and overridden by

[PATCH 4.10 004/129] mtd: nand: Add OX820 NAND hardware dependency

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Jean Delvare commit de0b34455afd1204a3644c9eb25b0b3b0aeb2fe9 upstream. The oxnas NAND driver is only needed for a specific platform, do not propose it on other platforms

[PATCH 4.10 004/129] mtd: nand: Add OX820 NAND hardware dependency

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Jean Delvare commit de0b34455afd1204a3644c9eb25b0b3b0aeb2fe9 upstream. The oxnas NAND driver is only needed for a specific platform, do not propose it on other platforms unless build-testing.

Re: [PATCHv2] arm64/cpufeature: don't use mutex in bringup path

On 11/05/17 16:37, Mark Rutland wrote: On Thu, May 11, 2017 at 04:15:38PM +0100, Suzuki K Poulose wrote: On 11/05/17 16:01, Mark Rutland wrote: +static inline bool cpus_have_const_cap(int num) +{ + if (static_branch_likely(_const_caps_ready)) + return

Re: [PATCHv2] arm64/cpufeature: don't use mutex in bringup path

On 11/05/17 16:37, Mark Rutland wrote: On Thu, May 11, 2017 at 04:15:38PM +0100, Suzuki K Poulose wrote: On 11/05/17 16:01, Mark Rutland wrote: +static inline bool cpus_have_const_cap(int num) +{ + if (static_branch_likely(_const_caps_ready)) + return

[PATCH 4.10 000/129] 4.10.16-stable review

This is the start of the stable review cycle for the 4.10.16 release. There are 129 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 Sat May 13 14:11:48 UTC 2017. Anything

[PATCH 4.10 000/129] 4.10.16-stable review

This is the start of the stable review cycle for the 4.10.16 release. There are 129 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 Sat May 13 14:11:48 UTC 2017. Anything

[PATCH 4.10 030/129] spi: armada-3700: Remove spi_master_put in a3700_spi_remove()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit e92f0051c0c65d7bee989884a233cfcd80303bdf upstream. The call to spi_master_put() in a3700_spi_remove() is redundant since the master is registered

[PATCH 4.10 030/129] spi: armada-3700: Remove spi_master_put in a3700_spi_remove()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit e92f0051c0c65d7bee989884a233cfcd80303bdf upstream. The call to spi_master_put() in a3700_spi_remove() is redundant since the master is registered using

[PATCH 4.10 039/129] mwifiex: debugfs: Fix (sometimes) off-by-1 SSID print

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit 6183468a23fc6b6903f8597982017ad2c7fdefcf upstream. Similar to commit fcd2042e8d36 ("mwifiex: printk() overflow with 32-byte SSIDs"), we failed to

[PATCH 4.10 039/129] mwifiex: debugfs: Fix (sometimes) off-by-1 SSID print

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit 6183468a23fc6b6903f8597982017ad2c7fdefcf upstream. Similar to commit fcd2042e8d36 ("mwifiex: printk() overflow with 32-byte SSIDs"), we failed to account for the existence

[PATCH 4.10 041/129] mwifiex: Avoid skipping WEP key deletion for AP

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Ganapathi Bhat commit a5b60de6972decc6b50a39abb376077c3c3621c8 upstream. This patch fixes the issue specific to AP. AP is started with WEP security and external station is

[PATCH 4.10 041/129] mwifiex: Avoid skipping WEP key deletion for AP

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Ganapathi Bhat commit a5b60de6972decc6b50a39abb376077c3c3621c8 upstream. This patch fixes the issue specific to AP. AP is started with WEP security and external station is connected to it.

[PATCH 4.10 043/129] mwifiex: set adapter->dev before starting to use mwifiex_dbg()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit ba1c7e45ec224cc8d2df33ecaee1946d48e79231 upstream. The mwifiex_dbg() log handler utilizes the struct device in adapter->dev. Without it, it

[PATCH 4.10 043/129] mwifiex: set adapter->dev before starting to use mwifiex_dbg()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit ba1c7e45ec224cc8d2df33ecaee1946d48e79231 upstream. The mwifiex_dbg() log handler utilizes the struct device in adapter->dev. Without it, it decides not to print anything.

[RFC 11/11] ima: appraise mode per namespace with new enforce_ns appraise mode

Global ima_appraise renamed to ima_appraise_mode and it saves the initial appraise mode. It is used to initialize the ima_appraise ima_ns_policy field when the policy is defined by user the first time for a namespace. New 'enforce_ns' appraise mode created. On this new appraise mode, the initial

[RFC 11/11] ima: appraise mode per namespace with new enforce_ns appraise mode

Global ima_appraise renamed to ima_appraise_mode and it saves the initial appraise mode. It is used to initialize the ima_appraise ima_ns_policy field when the policy is defined by user the first time for a namespace. New 'enforce_ns' appraise mode created. On this new appraise mode, the initial

[PATCH 4.10 048/129] iwlwifi: pcie: dont increment / decrement a bool

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit 04fa3e680b4dd2fdd11d0152fb9b6067e7aac140 upstream. David reported that the code I added uses the decrement and increment operator on a

[PATCH 4.10 044/129] iwlwifi: mvm: properly check for transport data in dump

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit c2e27e16f2411155b906db201b7e478144034ffe upstream. When copying from vmalloc'ed memory to the SG list, don't crash if the transport didn't

[PATCH 4.10 044/129] iwlwifi: mvm: properly check for transport data in dump

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit c2e27e16f2411155b906db201b7e478144034ffe upstream. When copying from vmalloc'ed memory to the SG list, don't crash if the transport didn't provide any data. Fixes:

[PATCH 4.10 048/129] iwlwifi: pcie: dont increment / decrement a bool

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Emmanuel Grumbach commit 04fa3e680b4dd2fdd11d0152fb9b6067e7aac140 upstream. David reported that the code I added uses the decrement and increment operator on a boolean variable. Fix that.

[PATCH 4.10 051/129] iwlwifi: mvm: fix reorder timer re-arming

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit 5351f9ab254c30d41659924265f1ecd7b4758d9e upstream. When NSSN is behind the reorder buffer due to timeout the reorder timer isn't getting re-armed

[PATCH 4.10 051/129] iwlwifi: mvm: fix reorder timer re-arming

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit 5351f9ab254c30d41659924265f1ecd7b4758d9e upstream. When NSSN is behind the reorder buffer due to timeout the reorder timer isn't getting re-armed until NSSN catches up. Fix

[PATCH 4.10 031/129] leds: ktd2692: avoid harmless maybe-uninitialized warning

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit cbe99c538d1776009e8710755bb6e726f7fffa9b upstream. gcc gets confused about the control flow in ktd2692_parse_dt(), causing it to warn about what seems like

[PATCH 4.10 053/129] iwlwifi: mvm/pcie: adjust A-MSDU tx_cmd length in PCIe

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit 05e5a7e58d3f8f597ebe6f78aaa13a2656b78239 upstream. Instead of setting the tx_cmd length in the mvm code, which is complicated by the fact that

[PATCH 4.10 031/129] leds: ktd2692: avoid harmless maybe-uninitialized warning

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit cbe99c538d1776009e8710755bb6e726f7fffa9b upstream. gcc gets confused about the control flow in ktd2692_parse_dt(), causing it to warn about what seems like a potential

[PATCH 4.10 053/129] iwlwifi: mvm/pcie: adjust A-MSDU tx_cmd length in PCIe

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit 05e5a7e58d3f8f597ebe6f78aaa13a2656b78239 upstream. Instead of setting the tx_cmd length in the mvm code, which is complicated by the fact that DQA may want to temporarily

[PATCH 4.10 057/129] iwlwifi: mvm: writing zero bytes to debugfs causes a crash

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 251fe09f13bfb54c1ede66ee8bf8ddd0061c4f7c upstream. This is a static analysis fix. The warning is:

[PATCH 4.10 054/129] iwlwifi: mvm: fix pending frame counter calculation

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit 94c3e614df2117626fccfac8f821c66e30556384 upstream. In DQA mode the check whether to decrement the pending frames counter relies on the tid status and

[PATCH 4.10 050/129] iwlwifi: pcie: fix the set of DMA memory mask

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit 2c6262b754f3c3338cb40b23880a3ac1f4693b25 upstream. Our 9000 device supports 64 bit DMA address for RX only, and not for TX. Setting DMA mask to 64

[PATCH 4.10 057/129] iwlwifi: mvm: writing zero bytes to debugfs causes a crash

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 251fe09f13bfb54c1ede66ee8bf8ddd0061c4f7c upstream. This is a static analysis fix. The warning is: drivers/net/wireless/intel/iwlwifi/mvm/fw-dbg.c:912

[PATCH 4.10 054/129] iwlwifi: mvm: fix pending frame counter calculation

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit 94c3e614df2117626fccfac8f821c66e30556384 upstream. In DQA mode the check whether to decrement the pending frames counter relies on the tid status and not on the txq id.

[PATCH 4.10 050/129] iwlwifi: pcie: fix the set of DMA memory mask

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit 2c6262b754f3c3338cb40b23880a3ac1f4693b25 upstream. Our 9000 device supports 64 bit DMA address for RX only, and not for TX. Setting DMA mask to 64 for the whole device is

[PATCH 4.10 055/129] iwlwifi: mvm: fix references to first_agg_queue in DQA mode

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit c56108b58ab870892277940a1def0d6b153f3e26 upstream. In DQA mode, first_agg_queue is initialized to IWL_MVM_DQA_MIN_DATA_QUEUE. This causes two bugs in

[PATCH 4.10 055/129] iwlwifi: mvm: fix references to first_agg_queue in DQA mode

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit c56108b58ab870892277940a1def0d6b153f3e26 upstream. In DQA mode, first_agg_queue is initialized to IWL_MVM_DQA_MIN_DATA_QUEUE. This causes two bugs in the tx response flow:

[PATCH 4.10 058/129] iwlwifi: mvm: fix accessing fw_id_to_mac_id

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit a95600294157ca7527ee7c70249fb53e09d8c566 upstream. Access should be by rcu_dereference. Issue was found by sparse. Fixes: 65e254821cee ("iwlwifi:

[PATCH 4.10 032/129] ARM: pxa: ezx: fix a910 camera data

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 67af5ebde1a4cd10e7bb663440de0773b7597c70 upstream. The camera_supply_dummy_device definition is shared between a780 and a910, but only provided when the

[PATCH 4.10 058/129] iwlwifi: mvm: fix accessing fw_id_to_mac_id

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit a95600294157ca7527ee7c70249fb53e09d8c566 upstream. Access should be by rcu_dereference. Issue was found by sparse. Fixes: 65e254821cee ("iwlwifi: mvm: use firmware station

[PATCH 4.10 032/129] ARM: pxa: ezx: fix a910 camera data

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 67af5ebde1a4cd10e7bb663440de0773b7597c70 upstream. The camera_supply_dummy_device definition is shared between a780 and a910, but only provided when the first is enabled

[PATCH 4.10 064/129] kprobes/x86: Fix kernel panic when certain exception-handling addresses are probed

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 75013fb16f8484898eaa8d0b08fed942d790f029 upstream. Fix to the exception table entry check by using probed address instead of the address of copied

[PATCH 4.10 064/129] kprobes/x86: Fix kernel panic when certain exception-handling addresses are probed

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit 75013fb16f8484898eaa8d0b08fed942d790f029 upstream. Fix to the exception table entry check by using probed address instead of the address of copied instruction. This

[PATCH 4.10 062/129] clk: Make x86/ conditional on CONFIG_COMMON_CLK

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Pierre-Louis Bossart commit f35b6542c3ac3f28056d298348a81f7d56d3a041 upstream. Fix Makefile for x86 support, dependency on CONFIG_COMMON_CLK was not

[PATCH 4.10 063/129] platform/x86: intel_pmc_core: fix out-of-bounds accesses on stack

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit 4f24ecff0153047a4a8b53c31d8001ee79e1cab7 upstream. pmc_core_mtpmc_link_status() an pmc_core_check_read_lock_bit() use test_bit() on local

[PATCH 4.10 062/129] clk: Make x86/ conditional on CONFIG_COMMON_CLK

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Pierre-Louis Bossart commit f35b6542c3ac3f28056d298348a81f7d56d3a041 upstream. Fix Makefile for x86 support, dependency on CONFIG_COMMON_CLK was not explicit Fixes: 701190fd7419 ('clk: x86:

[PATCH 4.10 063/129] platform/x86: intel_pmc_core: fix out-of-bounds accesses on stack

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Andrey Ryabinin commit 4f24ecff0153047a4a8b53c31d8001ee79e1cab7 upstream. pmc_core_mtpmc_link_status() an pmc_core_check_read_lock_bit() use test_bit() on local 32-bit variable. This causes

[PATCH 4.10 066/129] KVM: PPC: Book3S HV: Dont try to signal cpu -1

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 3deda5e50c893be38c1b6b3a73f8f8fb5560baa4 upstream. If the target vcpu for kvmppc_fast_vcpu_kick_hv() is not running on any CPU, then we will have

[PATCH 4.10 066/129] KVM: PPC: Book3S HV: Dont try to signal cpu -1

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Paul Mackerras commit 3deda5e50c893be38c1b6b3a73f8f8fb5560baa4 upstream. If the target vcpu for kvmppc_fast_vcpu_kick_hv() is not running on any CPU, then we will have vcpu->arch.thread_cpu

[PATCH 4.10 033/129] ARM: dts: NSP: GPIO reboot open-source

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Jon Mason commit acfa28b3649ec07775efaac0c00de2db39d71634 upstream. The libgpio code pre-sets the GPIO values for the gpio-reset in the device tree. This results in

[PATCH 4.10 033/129] ARM: dts: NSP: GPIO reboot open-source

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Jon Mason commit acfa28b3649ec07775efaac0c00de2db39d71634 upstream. The libgpio code pre-sets the GPIO values for the gpio-reset in the device tree. This results in the device being reset

[PATCH 4.10 034/129] ARM: dts: imx6sx-udoo-neo: Fix reboot hang

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Fabio Estevam commit 12aff99723901bcc0e2a6a34343a4f62c371fdd9 upstream. After issuing a 'reboot' command the imx6sx-udoo-neo board does not reboot as expected and it

[PATCH 4.10 037/129] ARM: dts: am57xx-idk: tpic2810 is on I2C bus, not SPI

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sekhar Nori commit f5432f01240ef69a391940d623b6a51768aefd65 upstream. commit 50e95b6b854c ("ARM: dts: am57xx-idk: Add Industrial output support") added the TPIC2810

[PATCH 4.10 034/129] ARM: dts: imx6sx-udoo-neo: Fix reboot hang

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Fabio Estevam commit 12aff99723901bcc0e2a6a34343a4f62c371fdd9 upstream. After issuing a 'reboot' command the imx6sx-udoo-neo board does not reboot as expected and it just hangs instead. In

[PATCH 4.10 037/129] ARM: dts: am57xx-idk: tpic2810 is on I2C bus, not SPI

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sekhar Nori commit f5432f01240ef69a391940d623b6a51768aefd65 upstream. commit 50e95b6b854c ("ARM: dts: am57xx-idk: Add Industrial output support") added the TPIC2810 device-tree node under SPI

[PATCH 4.10 071/129] usb: host: ehci-exynos: Decrese node refcount on exynos_ehci_get_phy() error paths

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit 3f6026b1dcb3c8ee71198c485a72ac674c6890dd upstream. Returning from for_each_available_child_of_node() loop requires cleaning up node refcount.

[PATCH 4.10 071/129] usb: host: ehci-exynos: Decrese node refcount on exynos_ehci_get_phy() error paths

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Krzysztof Kozlowski commit 3f6026b1dcb3c8ee71198c485a72ac674c6890dd upstream. Returning from for_each_available_child_of_node() loop requires cleaning up node refcount. Error paths lacked it

[PATCH 4.10 038/129] ARM: dts: sun7i: lamobo-r1: Fix CPU port RGMII settings

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli commit 0cdefd5b5485ee6eb3512a75739d09a4090176ed upstream. The CPU port of the BCM53125 is configured with RGMII (no delays) but this should actually be

[PATCH 4.10 038/129] ARM: dts: sun7i: lamobo-r1: Fix CPU port RGMII settings

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Florian Fainelli commit 0cdefd5b5485ee6eb3512a75739d09a4090176ed upstream. The CPU port of the BCM53125 is configured with RGMII (no delays) but this should actually be RGMII with transmit

[PATCH 4.10 084/129] USB: serial: ch341: fix modem-status handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit a0467a967f347842b30739aae636c44980265265 upstream. The modem-status register was read as part of device configuration at port_probe and then again at

[PATCH 4.10 084/129] USB: serial: ch341: fix modem-status handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit a0467a967f347842b30739aae636c44980265265 upstream. The modem-status register was read as part of device configuration at port_probe and then again at open (and

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