[PATCH 4.4 161/193] x86/microcode/AMD: Change load_microcode_amd()s param to bool to fix preemptibility bug

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Borislav Petkov commit dac6ca243c4c49a9ca7507d3d66140ebfac8b04b upstream. With CONFIG_DEBUG_PREEMPT enabled, I get: BUG: using smp_processor_id() in preemptible [] code: swapper/0/1

[PATCH 4.4 158/193] netlink: fix nla_put_{u8,u16,u32} for KASAN

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit b4391db42308c9940944b5d7be5ca4b78fb88dd0 upstream. When CONFIG_KASAN is enabled, the "--param asan-stack=1" causes rather large stack frames in some functions. This goes

[PATCH 4.4 162/193] drm/gma500: remove helper function

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sudip Mukherjee commit db9b60400f9253c25ae639797df2d0ff7a35d9d8 upstream. We were getting build warning about: drivers/gpu/drm/gma500/mdfld_dsi_output.c:407:2:

[PATCH 4.4 162/193] drm/gma500: remove helper function

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Sudip Mukherjee commit db9b60400f9253c25ae639797df2d0ff7a35d9d8 upstream. We were getting build warning about: drivers/gpu/drm/gma500/mdfld_dsi_output.c:407:2: warning: initialization

[PATCH 4.4 193/193] crypto: s5p-sss - Fix kernel Oops in AES-ECB mode

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kamil Konieczny commit c927b080c67e3e97193c81fc1d27f4251bf4e036 upstream. In AES-ECB mode crypt is done with key only, so any use of IV can cause kernel Oops.

[PATCH 4.4 193/193] crypto: s5p-sss - Fix kernel Oops in AES-ECB mode

4.4-stable review patch. If anyone has any objections, please let me know. -- From: Kamil Konieczny commit c927b080c67e3e97193c81fc1d27f4251bf4e036 upstream. In AES-ECB mode crypt is done with key only, so any use of IV can cause kernel Oops. Use IV only in AES-CBC and

[PATCH 4.9 003/145] kcm: Only allow TCP sockets to be attached to a KCM mux

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tom Herbert commit 581e7226a5d43f629eb6399a121f85f6a15f81be upstream. TCP sockets for IPv4 and IPv6 that are not listeners or in closed stated are allowed to be attached

[PATCH 4.9 003/145] kcm: Only allow TCP sockets to be attached to a KCM mux

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tom Herbert commit 581e7226a5d43f629eb6399a121f85f6a15f81be upstream. TCP sockets for IPv4 and IPv6 that are not listeners or in closed stated are allowed to be attached to a KCM mux. Fixes:

[PATCH 4.9 013/145] Provide a function to create a NUL-terminated string from unterminated data

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Howells commit f35157417215ec138c920320c746fdb3e04ef1d5 upstream. Provide a function, kmemdup_nul(), that will create a NUL-terminated string from an unterminated

[PATCH 4.9 013/145] Provide a function to create a NUL-terminated string from unterminated data

4.9-stable review patch. If anyone has any objections, please let me know. -- From: David Howells commit f35157417215ec138c920320c746fdb3e04ef1d5 upstream. Provide a function, kmemdup_nul(), that will create a NUL-terminated string from an unterminated character array where

Re: [PATCH] fs: proc: use down_read_killable in proc_pid_cmdline_read()

On 2/23/18 11:45 AM, Alexey Dobriyan wrote: On Fri, Feb 23, 2018 at 11:42:34AM -0800, Yang Shi wrote: On 2/23/18 11:33 AM, Alexey Dobriyan wrote: On Wed, Feb 21, 2018 at 03:13:10PM -0800, Yang Shi wrote: 2) access_remote_vm() et al will do the same ->mmap_sem, and Yes, it does. But,

[PATCH 4.9 014/145] selinux: ensure the context is NUL terminated in security_context_to_sid_core()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paul Moore commit ef28df55ac27e1e5cd122e19fa311d886d47a756 upstream. The syzbot/syzkaller automated tests found a problem in security_context_to_sid_core() during early

Re: [PATCH] fs: proc: use down_read_killable in proc_pid_cmdline_read()

On 2/23/18 11:45 AM, Alexey Dobriyan wrote: On Fri, Feb 23, 2018 at 11:42:34AM -0800, Yang Shi wrote: On 2/23/18 11:33 AM, Alexey Dobriyan wrote: On Wed, Feb 21, 2018 at 03:13:10PM -0800, Yang Shi wrote: 2) access_remote_vm() et al will do the same ->mmap_sem, and Yes, it does. But,

[PATCH 4.9 014/145] selinux: ensure the context is NUL terminated in security_context_to_sid_core()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paul Moore commit ef28df55ac27e1e5cd122e19fa311d886d47a756 upstream. The syzbot/syzkaller automated tests found a problem in security_context_to_sid_core() during early boot (before we load

[PATCH 4.9 015/145] selinux: skip bounded transition processing if the policy isnt loaded

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paul Moore commit 4b14752ec4e0d87126e636384cf37c8dd9df157c upstream. We can't do anything reasonable in security_bounded_transition() if we don't have a policy loaded, and

[PATCH 4.9 017/145] staging: android: ion: Add __GFP_NOWARN for system contig heap

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Laura Abbott commit 0c75f10312a35b149b2cebb1832316b35c2337ca upstream. syzbot reported a warning from Ion: WARNING: CPU: 1 PID: 3485 at mm/page_alloc.c:3926 ...

[PATCH 4.9 004/145] cfg80211: check dev_set_name() return value

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit 59b179b48ce2a6076448a44531242ac2b3f6cef2 upstream. syzbot reported a warning from rfkill_alloc(), and after a while I think that the reason is

[PATCH 4.9 015/145] selinux: skip bounded transition processing if the policy isnt loaded

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paul Moore commit 4b14752ec4e0d87126e636384cf37c8dd9df157c upstream. We can't do anything reasonable in security_bounded_transition() if we don't have a policy loaded, and in fact we could run

[PATCH 4.9 017/145] staging: android: ion: Add __GFP_NOWARN for system contig heap

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Laura Abbott commit 0c75f10312a35b149b2cebb1832316b35c2337ca upstream. syzbot reported a warning from Ion: WARNING: CPU: 1 PID: 3485 at mm/page_alloc.c:3926 ...

[PATCH 4.9 004/145] cfg80211: check dev_set_name() return value

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Berg commit 59b179b48ce2a6076448a44531242ac2b3f6cef2 upstream. syzbot reported a warning from rfkill_alloc(), and after a while I think that the reason is that it was doing fault

[PATCH 4.9 016/145] crypto: x86/twofish-3way - Fix %rbp usage

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit d8c7fe9f2a486a6e5f0d5229ca43807af5ab22c6 upstream. Using %rbp as a temporary register breaks frame pointer convention and breaks stack traces when

[PATCH 4.9 016/145] crypto: x86/twofish-3way - Fix %rbp usage

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit d8c7fe9f2a486a6e5f0d5229ca43807af5ab22c6 upstream. Using %rbp as a temporary register breaks frame pointer convention and breaks stack traces when unwinding from an

[PATCH 4.9 018/145] staging: android: ion: Switch from WARN to pr_warn

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Laura Abbott commit e4e179a844f52e907e550f887d0a2171f1508af1 upstream. Syzbot reported a warning with Ion: WARNING: CPU: 0 PID: 3502 at

[PATCH 4.9 018/145] staging: android: ion: Switch from WARN to pr_warn

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Laura Abbott commit e4e179a844f52e907e550f887d0a2171f1508af1 upstream. Syzbot reported a warning with Ion: WARNING: CPU: 0 PID: 3502 at drivers/staging/android/ion/ion-ioctl.c:73

[PATCHv5 2/5] ASoC: codec: cpcap: new codec

Motorola CPCAP is a PMIC with audio functionality, that can be found on Motorola Droid 4 and probably a few other phones from Motorola's Droid series. The driver has been written from scratch using Motorola's Android driver, register dumps from running Android and datasheet for NXP MC13783UG

[PATCHv5 2/5] ASoC: codec: cpcap: new codec

Motorola CPCAP is a PMIC with audio functionality, that can be found on Motorola Droid 4 and probably a few other phones from Motorola's Droid series. The driver has been written from scratch using Motorola's Android driver, register dumps from running Android and datasheet for NXP MC13783UG

[PATCH 2/8] efi: Decode IA32/X64 Processor Error Section

From: Yazen Ghannam Recognize the IA32/X64 Processor Error Section. Do the section decoding in a new "cper-x86.c" file and add this to the Makefile depending on a new "UEFI_CPER_X86" config option. Print the Local APIC ID and CPUID info from the Processor Error Record.

[PATCH 2/8] efi: Decode IA32/X64 Processor Error Section

From: Yazen Ghannam Recognize the IA32/X64 Processor Error Section. Do the section decoding in a new "cper-x86.c" file and add this to the Makefile depending on a new "UEFI_CPER_X86" config option. Print the Local APIC ID and CPUID info from the Processor Error Record. The "Processor Error

[PATCH 3/8] efi: Decode IA32/X64 Processor Error Info Structure

From: Yazen Ghannam Print the fields in the IA32/X64 Processor Error Info Structure. Based on UEFI 2.7 Table 256. IA32/X64 Processor Error Information Structure. Cc: # 4.16.x Signed-off-by: Yazen Ghannam ---

[PATCH 6/8] efi: Decode additional IA32/X64 Bus Check fields

From: Yazen Ghannam The "Participation Type", "Time Out", and "Address Space" fields are unique to the IA32/X64 Bus Check structure. Print these fields. Based on UEFI 2.7 Table 259. IA32/X64 Bus Check Structure Cc: # 4.16.x Signed-off-by: Yazen

[PATCH 3/8] efi: Decode IA32/X64 Processor Error Info Structure

From: Yazen Ghannam Print the fields in the IA32/X64 Processor Error Info Structure. Based on UEFI 2.7 Table 256. IA32/X64 Processor Error Information Structure. Cc: # 4.16.x Signed-off-by: Yazen Ghannam --- drivers/firmware/efi/cper-x86.c | 53 + 1

[PATCH 6/8] efi: Decode additional IA32/X64 Bus Check fields

From: Yazen Ghannam The "Participation Type", "Time Out", and "Address Space" fields are unique to the IA32/X64 Bus Check structure. Print these fields. Based on UEFI 2.7 Table 259. IA32/X64 Bus Check Structure Cc: # 4.16.x Signed-off-by: Yazen Ghannam --- drivers/firmware/efi/cper-x86.c |

[PATCH 0/8] Decode IA32/X64 CPER

From: Yazen Ghannam This series adds decoding for the IA32/X64 Common Platform Error Record. Patch 1 fixes the IA32/X64 Processor Error Section definition to match the UEFI spec. Patches 2-8 add the new decoding. The patches incrementally add the decoding starting from

[PATCH 0/8] Decode IA32/X64 CPER

From: Yazen Ghannam This series adds decoding for the IA32/X64 Common Platform Error Record. Patch 1 fixes the IA32/X64 Processor Error Section definition to match the UEFI spec. Patches 2-8 add the new decoding. The patches incrementally add the decoding starting from the top-level "Error

[PATCH 7/8] efi: Decode IA32/X64 MS Check structure

From: Yazen Ghannam The IA32/X64 MS Check structure varies from the other Check structures in the the bit positions of its fields, and it includes an additional "Error Type" field. Decode the MS Check structure in a separate function. Based on UEFI 2.7 Table 260.

[PATCH 7/8] efi: Decode IA32/X64 MS Check structure

From: Yazen Ghannam The IA32/X64 MS Check structure varies from the other Check structures in the the bit positions of its fields, and it includes an additional "Error Type" field. Decode the MS Check structure in a separate function. Based on UEFI 2.7 Table 260. IA32/X64 MS Check Field

[PATCH 4/8] efi: Decode UEFI-defined IA32/X64 Error Structure GUIDs

From: Yazen Ghannam For easier handling, match the known IA32/X64 error structure GUIDs to enums. Also, print out the name of the matching Error Structure Type. GUIDs taken from UEFI 2.7 section N.2.4.2.1 IA32/X64 Processor Error Information Structure. Cc:

[PATCH 4/8] efi: Decode UEFI-defined IA32/X64 Error Structure GUIDs

From: Yazen Ghannam For easier handling, match the known IA32/X64 error structure GUIDs to enums. Also, print out the name of the matching Error Structure Type. GUIDs taken from UEFI 2.7 section N.2.4.2.1 IA32/X64 Processor Error Information Structure. Cc: # 4.16.x Signed-off-by: Yazen

[PATCH 5/8] efi: Decode IA32/X64 Cache, TLB, and Bus Check structures

From: Yazen Ghannam Print the common fields of the Cache, TLB, and Bus check structures.The fields of these three check types are the same except for a few more fields in the Bus check structure. The remaining Bus check structure fields will be decoded in a following

[PATCH 5/8] efi: Decode IA32/X64 Cache, TLB, and Bus Check structures

From: Yazen Ghannam Print the common fields of the Cache, TLB, and Bus check structures.The fields of these three check types are the same except for a few more fields in the Bus check structure. The remaining Bus check structure fields will be decoded in a following patch. Based on UEFI 2.7,

[PATCH 8/8] efi: Decode IA32/X64 Context Info structure

From: Yazen Ghannam Print the fields of the IA32/X64 Context Information structure. Print the "Register Array" as raw values. Some context types are defined in the UEFI spec, so more detailed decoded may be added in the future. Based on UEFI 2.7 section N.2.4.2.2

[PATCH 8/8] efi: Decode IA32/X64 Context Info structure

From: Yazen Ghannam Print the fields of the IA32/X64 Context Information structure. Print the "Register Array" as raw values. Some context types are defined in the UEFI spec, so more detailed decoded may be added in the future. Based on UEFI 2.7 section N.2.4.2.2 IA32/X64 Processor Context

[PATCH 1/8] efi: Fix IA32/X64 Processor Error Record definition

From: Yazen Ghannam Based on UEFI 2.7 Table 255. Processor Error Record, the "Local APIC_ID" field is 8 bytes but Linux defines this field as 1 byte. Fix this in the struct cper_sec_proc_ia definition. Cc: # 4.16.x Signed-off-by: Yazen Ghannam

[PATCH 1/8] efi: Fix IA32/X64 Processor Error Record definition

From: Yazen Ghannam Based on UEFI 2.7 Table 255. Processor Error Record, the "Local APIC_ID" field is 8 bytes but Linux defines this field as 1 byte. Fix this in the struct cper_sec_proc_ia definition. Cc: # 4.16.x Signed-off-by: Yazen Ghannam --- include/linux/cper.h | 2 +- 1 file

[PATCHv5 4/5] ARM: dts: motorola-cpcap-mapphone: add audio-codec

Add node for audio-codec to its DT file. Signed-off-by: Sebastian Reichel --- arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi | 13 + 1 file changed, 13 insertions(+) diff --git a/arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi

[PATCHv5 4/5] ARM: dts: motorola-cpcap-mapphone: add audio-codec

Add node for audio-codec to its DT file. Signed-off-by: Sebastian Reichel --- arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi | 13 + 1 file changed, 13 insertions(+) diff --git a/arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi b/arch/arm/boot/dts/motorola-cpcap-mapphone.dtsi index

[PATCHv5 5/5] ARM: dts: omap4-droid4: add soundcard

Add sound support to Motorola Droid 4 using simple-soundcard and CPCAP's audio codec. This does not yet correctly represent the whole audio routing, since McBSP3 is also connected to Bluetooth and MDM6600 modem (and probably also 4G modem). These extra DAI links are not yet supported and have not

[PATCHv5 5/5] ARM: dts: omap4-droid4: add soundcard

Add sound support to Motorola Droid 4 using simple-soundcard and CPCAP's audio codec. This does not yet correctly represent the whole audio routing, since McBSP3 is also connected to Bluetooth and MDM6600 modem (and probably also 4G modem). These extra DAI links are not yet supported and have not

[PATCHv5 3/5] mfd: motorola-cpcap: Add audio-codec support

From: Sebastian Reichel Add support for the audio-codec node by converting from devm_of_platform_populate() to devm_mfd_add_devices(). Signed-off-by: Sebastian Reichel --- drivers/mfd/motorola-cpcap.c | 51

[PATCHv5 1/5] dt-bindings: mfd: motorola-cpcap: document audio-codec

This adds the DT binding for the audio-codec sub-module found inside the Motorola CPCAP PMIC. Signed-off-by: Sebastian Reichel --- .../devicetree/bindings/mfd/motorola-cpcap.txt | 42 ++ 1 file changed, 42 insertions(+) diff --git

[PATCHv5 0/5] Motorola Droid 4 Audio Support

Hi, This adds audio support to Motorola Droid 4. I dropped the regulator from the DT binding as requested by Mark. Tested: - Playing via both DACs using Speaker, Earpiece, Headphone - Recording using internal Mic - Volume Controls Known not to work: - 3.5mm detection support (requires

[PATCHv5 3/5] mfd: motorola-cpcap: Add audio-codec support

From: Sebastian Reichel Add support for the audio-codec node by converting from devm_of_platform_populate() to devm_mfd_add_devices(). Signed-off-by: Sebastian Reichel --- drivers/mfd/motorola-cpcap.c | 51 +++- 1 file changed, 50 insertions(+), 1

[PATCHv5 1/5] dt-bindings: mfd: motorola-cpcap: document audio-codec

This adds the DT binding for the audio-codec sub-module found inside the Motorola CPCAP PMIC. Signed-off-by: Sebastian Reichel --- .../devicetree/bindings/mfd/motorola-cpcap.txt | 42 ++ 1 file changed, 42 insertions(+) diff --git

[PATCHv5 0/5] Motorola Droid 4 Audio Support

Hi, This adds audio support to Motorola Droid 4. I dropped the regulator from the DT binding as requested by Mark. Tested: - Playing via both DACs using Speaker, Earpiece, Headphone - Recording using internal Mic - Volume Controls Known not to work: - 3.5mm detection support (requires

[PATCH 4.9 025/145] netfilter: on sockopt() acquire sock lock only in the required scope

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni commit 3f34cfae1238848fd53f25e5c8fd59da57901f4b upstream. Syzbot reported several deadlocks in the netfilter area caused by rtnl lock and socket lock being

[PATCH 4.9 025/145] netfilter: on sockopt() acquire sock lock only in the required scope

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Abeni commit 3f34cfae1238848fd53f25e5c8fd59da57901f4b upstream. Syzbot reported several deadlocks in the netfilter area caused by rtnl lock and socket lock being acquired with a

[PATCH 4.9 023/145] netfilter: x_tables: avoid out-of-bounds reads in xt_request_find_{match|target}

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit da17c73b6eb74aad3c3c0654394635675b623b3e upstream. It looks like syzbot found its way into netfilter territory. Issue here is that @name comes from

[PATCH 4.9 023/145] netfilter: x_tables: avoid out-of-bounds reads in xt_request_find_{match|target}

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet commit da17c73b6eb74aad3c3c0654394635675b623b3e upstream. It looks like syzbot found its way into netfilter territory. Issue here is that @name comes from user space and might

[PATCH 4.9 024/145] netfilter: ipt_CLUSTERIP: fix out-of-bounds accesses in clusterip_tg_check()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Vyukov commit 1a38956cce5eabd7b74f94bab70265e4df83165e upstream. Commit 136e92bbec0a switched local_nodes from an array to a bitmask but did not add proper bounds

[PATCH 4.9 024/145] netfilter: ipt_CLUSTERIP: fix out-of-bounds accesses in clusterip_tg_check()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Dmitry Vyukov commit 1a38956cce5eabd7b74f94bab70265e4df83165e upstream. Commit 136e92bbec0a switched local_nodes from an array to a bitmask but did not add proper bounds checks. As the result

[PATCH 4.9 029/145] net: avoid skb_warn_bad_offload on IS_ERR

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn commit 8d74e9f88d65af8bb2e095aff506aa6eac755ada upstream. skb_warn_bad_offload warns when packets enter the GSO stack that require skb_checksum_help or

[PATCH 4.9 027/145] netfilter: xt_RATEEST: acquire xt_rateest_mutex for hash insert

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang commit 7dc68e98757a8eccf8ca7a53a29b896f1eef1f76 upstream. rateest_hash is supposed to be protected by xt_rateest_mutex, and, as suggested by Eric, lookup

[PATCH 4.9 028/145] rds: tcp: atomically purge entries from rds_tcp_conn_list during netns delete

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sowmini Varadhan commit f10b4cff98c6977668434fbf5dd58695eeca2897 upstream. The rds_tcp_kill_sock() function parses the rds_tcp_conn_list to find the rds_connection

[PATCH 4.9 029/145] net: avoid skb_warn_bad_offload on IS_ERR

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Willem de Bruijn commit 8d74e9f88d65af8bb2e095aff506aa6eac755ada upstream. skb_warn_bad_offload warns when packets enter the GSO stack that require skb_checksum_help or vice versa. Do not warn

[PATCH 4.9 027/145] netfilter: xt_RATEEST: acquire xt_rateest_mutex for hash insert

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Cong Wang commit 7dc68e98757a8eccf8ca7a53a29b896f1eef1f76 upstream. rateest_hash is supposed to be protected by xt_rateest_mutex, and, as suggested by Eric, lookup and insert should be atomic,

[PATCH 4.9 028/145] rds: tcp: atomically purge entries from rds_tcp_conn_list during netns delete

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sowmini Varadhan commit f10b4cff98c6977668434fbf5dd58695eeca2897 upstream. The rds_tcp_kill_sock() function parses the rds_tcp_conn_list to find the rds_connection entries marked for deletion

[PATCH 4.9 031/145] crypto: hash - prevent using keyed hashes without setting key

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 9fa68f620041be04720d0cbfb1bd3ddfc6310b24 upstream. Currently, almost none of the keyed hash algorithms check whether a key has been set before

[PATCH 4.9 032/145] ASoC: ux500: add MODULE_LICENSE tag

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 1783c9d7cb7bc3181b9271665959b87280d98d8e upstream. This adds MODULE_LICENSE/AUTHOR/DESCRIPTION tags to the ux500 platform drivers, to avoid these build

[PATCH 4.9 031/145] crypto: hash - prevent using keyed hashes without setting key

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 9fa68f620041be04720d0cbfb1bd3ddfc6310b24 upstream. Currently, almost none of the keyed hash algorithms check whether a key has been set before proceeding. Some algorithms

[PATCH 4.9 032/145] ASoC: ux500: add MODULE_LICENSE tag

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 1783c9d7cb7bc3181b9271665959b87280d98d8e upstream. This adds MODULE_LICENSE/AUTHOR/DESCRIPTION tags to the ux500 platform drivers, to avoid these build warnings: WARNING:

[PATCH 4.9 037/145] staging: android: ashmem: Fix a race condition in pin ioctls

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit ce8a3a9e76d0193e2e8d74a06d275b3c324ca652 upstream. ashmem_pin_unpin() reads asma->file and asma->size before taking the ashmem_mutex, so it can race

[PATCH 4.9 034/145] ARM: 8743/1: bL_switcher: add MODULE_LICENSE tag

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit a21b4c10c7bf5b58112afa20d6fa829e8d74e3e6 upstream. Without this tag, we get a build warning: WARNING: modpost: missing MODULE_LICENSE() in

[PATCH 4.9 037/145] staging: android: ashmem: Fix a race condition in pin ioctls

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings commit ce8a3a9e76d0193e2e8d74a06d275b3c324ca652 upstream. ashmem_pin_unpin() reads asma->file and asma->size before taking the ashmem_mutex, so it can race with other operations

[PATCH 4.9 034/145] ARM: 8743/1: bL_switcher: add MODULE_LICENSE tag

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit a21b4c10c7bf5b58112afa20d6fa829e8d74e3e6 upstream. Without this tag, we get a build warning: WARNING: modpost: missing MODULE_LICENSE() in

[PATCH 4.9 035/145] arm64: dts: add #cooling-cells to CPU nodes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit acbf76ee05067c3942852019993f7beb69a0f45f upstream. dtc complains about the lack of #coolin-cells properties for the CPU nodes that are referred to as

[PATCH 4.9 035/145] arm64: dts: add #cooling-cells to CPU nodes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit acbf76ee05067c3942852019993f7beb69a0f45f upstream. dtc complains about the lack of #coolin-cells properties for the CPU nodes that are referred to as "cooling-device":

[PATCH 4.9 039/145] staging: iio: adc: ad7192: fix external frequency setting

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexandru Ardelean commit e31b617d0a63c6558485aaa730fd162faa95a766 upstream. The external clock frequency was set only when selecting the internal clock, which

[PATCH 4.9 038/145] binder: check for binder_thread allocation failure in binder_poll()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit f88982679f54f75daa5b8eff3da72508f1e7422f upstream. If the kzalloc() in binder_get_thread() fails, binder_poll() dereferences the resulting NULL

[PATCH 4.9 039/145] staging: iio: adc: ad7192: fix external frequency setting

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexandru Ardelean commit e31b617d0a63c6558485aaa730fd162faa95a766 upstream. The external clock frequency was set only when selecting the internal clock, which is fixed at 4.9152 Mhz. This is

[PATCH 4.9 038/145] binder: check for binder_thread allocation failure in binder_poll()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit f88982679f54f75daa5b8eff3da72508f1e7422f upstream. If the kzalloc() in binder_get_thread() fails, binder_poll() dereferences the resulting NULL pointer. Fix it by

[PATCH 4.9 040/145] staging: iio: ad5933: switch buffer mode to software

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexandru Ardelean commit 7d2b8e6aaf9ee87910c2337e1c59bb5d3e3ba8c5 upstream. Since commit 152a6a884ae1 ("staging:iio:accel:sca3000 move to hybrid hard / soft

[PATCH 4.9 040/145] staging: iio: ad5933: switch buffer mode to software

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Alexandru Ardelean commit 7d2b8e6aaf9ee87910c2337e1c59bb5d3e3ba8c5 upstream. Since commit 152a6a884ae1 ("staging:iio:accel:sca3000 move to hybrid hard / soft buffer design.") the buffer

[PATCH 4.9 007/145] xfrm: Fix stack-out-of-bounds read on socket policy lookup.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert commit ddc47e4404b58f03e98345398fb12d38fe291512 upstream. When we do tunnel or beet mode, we pass saddr and daddr from the template to

[PATCH 4.9 007/145] xfrm: Fix stack-out-of-bounds read on socket policy lookup.

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert commit ddc47e4404b58f03e98345398fb12d38fe291512 upstream. When we do tunnel or beet mode, we pass saddr and daddr from the template to xfrm_state_find(), this is ok. On

[PATCH 4.9 051/145] perf bench numa: Fixup discontiguous/sparse numa nodes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Satheesh Rajendran [ Upstream commit 321a7c35c90cc834851ceda18a8ee18f1d032b92 ] Certain systems are designed to have sparse/discontiguous nodes. On such systems,

[PATCH 4.9 010/145] blktrace: fix unlocked registration of tracepoints

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jens Axboe commit a6da0024ffc19e0d47712bb5ca4fd083f76b07df upstream. We need to ensure that tracepoints are registered and unregistered with the users of them. The existing

[PATCH 4.9 009/145] sctp: set frag_point in sctp_setsockopt_maxseg correctly

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long commit ecca8f88da5c4260cc2bccfefd2a24976704c366 upstream. Now in sctp_setsockopt_maxseg user_frag or frag_point can be set with val >= 8 and val <=

[PATCH 4.9 051/145] perf bench numa: Fixup discontiguous/sparse numa nodes

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Satheesh Rajendran [ Upstream commit 321a7c35c90cc834851ceda18a8ee18f1d032b92 ] Certain systems are designed to have sparse/discontiguous nodes. On such systems, 'perf bench numa' hangs,

[PATCH 4.9 010/145] blktrace: fix unlocked registration of tracepoints

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Jens Axboe commit a6da0024ffc19e0d47712bb5ca4fd083f76b07df upstream. We need to ensure that tracepoints are registered and unregistered with the users of them. The existing atomic count isn't

[PATCH 4.9 009/145] sctp: set frag_point in sctp_setsockopt_maxseg correctly

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Xin Long commit ecca8f88da5c4260cc2bccfefd2a24976704c366 upstream. Now in sctp_setsockopt_maxseg user_frag or frag_point can be set with val >= 8 and val <= SCTP_MAX_CHUNK_LEN. But both checks

[PATCH 4.9 002/145] kcm: Check if sk_user_data already set in kcm_attach

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tom Herbert commit e5571240236c5652f3e079b1d5866716a7ad819c upstream. This is needed to prevent sk_user_data being overwritten. The check is done under the callback lock.

[PATCH 4.9 002/145] kcm: Check if sk_user_data already set in kcm_attach

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Tom Herbert commit e5571240236c5652f3e079b1d5866716a7ad819c upstream. This is needed to prevent sk_user_data being overwritten. The check is done under the callback lock. This should prevent a

[PATCH 4.9 052/145] media: s5k6aa: describe some function parameters

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab [ Upstream commit 070250a1715cee2297de0d9e7e2cea58be999d37 ] as warned: drivers/media/i2c/s5k6aa.c:429: warning: No description found for

[PATCH 4.9 042/145] usb: build drivers/usb/common/ when USB_SUPPORT is set

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit c9d24f78268be444e803fb2bb138a2f598de9c23 ] PHY drivers can use ULPI interfaces when CONFIG_USB (which is host side support) is not

[PATCH 4.9 052/145] media: s5k6aa: describe some function parameters

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab [ Upstream commit 070250a1715cee2297de0d9e7e2cea58be999d37 ] as warned: drivers/media/i2c/s5k6aa.c:429: warning: No description found for parameter 's5k6aa'

[PATCH 4.9 042/145] usb: build drivers/usb/common/ when USB_SUPPORT is set

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Randy Dunlap [ Upstream commit c9d24f78268be444e803fb2bb138a2f598de9c23 ] PHY drivers can use ULPI interfaces when CONFIG_USB (which is host side support) is not enabled, so also build

[PATCH 4.9 055/145] i40iw: Correct ARP index mask

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mustafa Ismail [ Upstream commit a283cdc4d3670700182c820b59078387f9a01a30 ] The ARP table entry indexes are aliased to 12bits instead of the intended 16bits when

[PATCH 4.9 054/145] pinctrl: sunxi: Fix A64 UART mux value

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andre Przywara [ Upstream commit 7c5c2c2d18d778e51fd8b899965097168306031c ] To use pin PF4 as the RX signal of UART0, we have to write 0b011 into the respective pin

[PATCH 4.9 055/145] i40iw: Correct ARP index mask

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Mustafa Ismail [ Upstream commit a283cdc4d3670700182c820b59078387f9a01a30 ] The ARP table entry indexes are aliased to 12bits instead of the intended 16bits when uploaded to the QP Context.

[PATCH 4.9 054/145] pinctrl: sunxi: Fix A64 UART mux value

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Andre Przywara [ Upstream commit 7c5c2c2d18d778e51fd8b899965097168306031c ] To use pin PF4 as the RX signal of UART0, we have to write 0b011 into the respective pin controller register. Fix

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