[PATCH AUTOSEL 5.0 27/34] x86/mm/mem_encrypt: Disable all instrumentation for early SME setup

2019-05-16 Thread Sasha Levin
From: Gary Hook [ Upstream commit b51ce3744f115850166f3d6c292b9c8cb849ad4f ] Enablement of AMD's Secure Memory Encryption feature is determined very early after start_kernel() is entered. Part of this procedure involves scanning the command line for the parameter 'mem_encrypt'. To determine int

[PATCH AUTOSEL 4.19 13/25] x86: kvm: hyper-v: deal with buggy TLB flush requests from WS2012

2019-05-16 Thread Sasha Levin
From: Vitaly Kuznetsov [ Upstream commit da66761c2d93a46270d69001abb5692717495a68 ] It was reported that with some special Multi Processor Group configuration, e.g: bcdedit.exe /set groupsize 1 bcdedit.exe /set maxgroup on bcdedit.exe /set groupaware on for a 16-vCPU guest WS2012 shows BSOD o

Re: [alsa-devel] [PATCH V5] ASoC: cs42xx8: add reset-gpios in binding document

2019-05-16 Thread Fabio Estevam
[You should always submit dt-bindings patches to Rob and to the devicetree list as indicated by checkpatch] On Thu, May 16, 2019 at 8:42 AM S.j. Wang wrote: > > Add reset-gpios property, which is optional. > > Signed-off-by: Shengjiu Wang > +Optional properties: > + > + - reset-gpios : a GPIO

[PATCH AUTOSEL 4.19 05/25] esp4: add length check for UDP encapsulation

2019-05-16 Thread Sasha Levin
From: Sabrina Dubroca [ Upstream commit 8dfb4eba4100e7cdd161a8baef2d8d61b7a7e62e ] esp_output_udp_encap can produce a length that doesn't fit in the 16 bits of a UDP header's length field. In that case, we'll send a fragmented packet whose length is larger than IP_MAX_MTU (resulting in "Oversize

[PATCH AUTOSEL 4.19 10/25] securityfs: fix use-after-free on symlink traversal

2019-05-16 Thread Sasha Levin
From: Al Viro [ Upstream commit 46c874419652bbefdfed17420fd6e88d8a31d9ec ] symlink body shouldn't be freed without an RCU delay. Switch securityfs to ->destroy_inode() and use of call_rcu(); free both the inode and symlink body in the callback. Signed-off-by: Al Viro Signed-off-by: Sasha Levi

[PATCH AUTOSEL 4.19 08/25] clk: sunxi-ng: nkmp: Avoid GENMASK(-1, 0)

2019-05-16 Thread Sasha Levin
From: Jernej Skrabec [ Upstream commit 2abc330c514fe56c570bb1a6318b054b06a4f72e ] Sometimes one of the nkmp factors is unused. This means that one of the factors shift and width values are set to 0. Current nkmp clock code generates a mask for each factor with GENMASK(width + shift - 1, shift).

Re: [PATCH v3 6/7] iommu: Introduce IOMMU_RESV_DIRECT_RELAXABLE reserved memory regions

2019-05-16 Thread Auger Eric
Hi Jean-Philippe, On 5/16/19 1:16 PM, Jean-Philippe Brucker wrote: > On 16/05/2019 11:08, Eric Auger wrote: >> Note: At the moment the sysfs ABI is not changed. However I wonder >> whether it wouldn't be preferable to report the direct region as >> "direct_relaxed" there. At the moment, in case th

[PATCH AUTOSEL 4.19 17/25] power: supply: sysfs: prevent endless uevent loop with CONFIG_POWER_SUPPLY_DEBUG

2019-05-16 Thread Sasha Levin
From: Andrey Smirnov [ Upstream commit 349ced9984ff540ce74ca8a0b2e9b03dc434b9dd ] Fix a similar endless event loop as was done in commit 8dcf32175b4e ("i2c: prevent endless uevent loop with CONFIG_I2C_DEBUG_CORE"): The culprit is the dev_dbg printk in the i2c uevent handler. If this is acti

[PATCH AUTOSEL 4.19 14/25] mac80211: Fix kernel panic due to use of txq after free

2019-05-16 Thread Sasha Levin
From: Bhagavathi Perumal S [ Upstream commit f1267cf3c01b12e0f843fb6a7450a7f0b2efab8a ] The txq of vif is added to active_txqs list for ATF TXQ scheduling in the function ieee80211_queue_skb(), but it was not properly removed before freeing the txq object. It was causing use after free of the tx

[PATCH AUTOSEL 4.14 01/16] xfrm: policy: Fix out-of-bound array accesses in __xfrm_policy_unlink

2019-05-16 Thread Sasha Levin
From: YueHaibing [ Upstream commit b805d78d300bcf2c83d6df7da0c818b0fee41427 ] UBSAN report this: UBSAN: Undefined behaviour in net/xfrm/xfrm_policy.c:1289:24 index 6 is out of range for type 'unsigned int [6]' CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.162-514.55.6.9.x86_64+ #13 Hardware nam

[PATCH AUTOSEL 4.19 19/25] qmi_wwan: new Wistron, ZTE and D-Link devices

2019-05-16 Thread Sasha Levin
From: Bjørn Mork [ Upstream commit 88ef66a28391ea7b624bfb7508a5b015c13b28f3 ] Adding device entries found in vendor modified versions of this driver. Function maps for some of the devices follow: WNC D16Q1, D16Q5, D18Q1 LTE CAT3 module (1435:0918) MI_00 Qualcomm HS-USB Diagnostics MI_01 Andro

[PATCH AUTOSEL 4.19 22/25] x86/mm/mem_encrypt: Disable all instrumentation for early SME setup

2019-05-16 Thread Sasha Levin
From: Gary Hook [ Upstream commit b51ce3744f115850166f3d6c292b9c8cb849ad4f ] Enablement of AMD's Secure Memory Encryption feature is determined very early after start_kernel() is entered. Part of this procedure involves scanning the command line for the parameter 'mem_encrypt'. To determine int

[PATCH AUTOSEL 4.19 21/25] sched/cpufreq: Fix kobject memleak

2019-05-16 Thread Sasha Levin
From: "Tobin C. Harding" [ Upstream commit 9a4f26cc98d81b67ecc23b890c28e2df324e29f3 ] Currently the error return path from kobject_init_and_add() is not followed by a call to kobject_put() - which means we are leaking the kobject. Fix it by adding a call to kobject_put() in the error path of ko

[PATCH AUTOSEL 4.14 02/16] xfrm6_tunnel: Fix potential panic when unloading xfrm6_tunnel module

2019-05-16 Thread Sasha Levin
From: Su Yanjun [ Upstream commit 6ee02a54ef990a71bf542b6f0a4e3321de9d9c66 ] When unloading xfrm6_tunnel module, xfrm6_tunnel_fini directly frees the xfrm6_tunnel_spi_kmem. Maybe someone has gotten the xfrm6_tunnel_spi, so need to wait it. Fixes: 91cc3bb0b04ff("xfrm6_tunnel: RCU conversion") Si

[PATCH AUTOSEL 4.19 23/25] ufs: fix braino in ufs_get_inode_gid() for solaris UFS flavour

2019-05-16 Thread Sasha Levin
From: Al Viro [ Upstream commit 4e9036042fedaffcd868d7f7aa948756c48c637d ] To choose whether to pick the GID from the old (16bit) or new (32bit) field, we should check if the old gid field is set to 0x. Mainline checks the old *UID* field instead - cut'n'paste from the corresponding code in

[PATCH V5] ASoC: cs42xx8: add reset-gpios in binding document

2019-05-16 Thread S.j. Wang
Add reset-gpios property, which is optional. Signed-off-by: Shengjiu Wang --- Changes in V5 - use GPIO_ACTIVE_LOW Changes in V4 - use gpios instead of gpio Changes in RESEND v3 - send updated binding document only Changes in v3 - update binding document. Changes in v2 - use devm_gpiod_get_opt

[PATCH AUTOSEL 4.14 15/16] ufs: fix braino in ufs_get_inode_gid() for solaris UFS flavour

2019-05-16 Thread Sasha Levin
From: Al Viro [ Upstream commit 4e9036042fedaffcd868d7f7aa948756c48c637d ] To choose whether to pick the GID from the old (16bit) or new (32bit) field, we should check if the old gid field is set to 0x. Mainline checks the old *UID* field instead - cut'n'paste from the corresponding code in

[PATCH AUTOSEL 4.14 08/16] apparmorfs: fix use-after-free on symlink traversal

2019-05-16 Thread Sasha Levin
From: Al Viro [ Upstream commit f51dcd0f621caac5380ce90fbbeafc32ce4517ae ] symlink body shouldn't be freed without an RCU delay. Switch apparmorfs to ->destroy_inode() and use of call_rcu(); free both the inode and symlink body in the callback. Signed-off-by: Al Viro Signed-off-by: Sasha Levi

[PATCH AUTOSEL 4.14 11/16] power: supply: sysfs: prevent endless uevent loop with CONFIG_POWER_SUPPLY_DEBUG

2019-05-16 Thread Sasha Levin
From: Andrey Smirnov [ Upstream commit 349ced9984ff540ce74ca8a0b2e9b03dc434b9dd ] Fix a similar endless event loop as was done in commit 8dcf32175b4e ("i2c: prevent endless uevent loop with CONFIG_I2C_DEBUG_CORE"): The culprit is the dev_dbg printk in the i2c uevent handler. If this is acti

[PATCH AUTOSEL 4.9 7/9] power: supply: sysfs: prevent endless uevent loop with CONFIG_POWER_SUPPLY_DEBUG

2019-05-16 Thread Sasha Levin
From: Andrey Smirnov [ Upstream commit 349ced9984ff540ce74ca8a0b2e9b03dc434b9dd ] Fix a similar endless event loop as was done in commit 8dcf32175b4e ("i2c: prevent endless uevent loop with CONFIG_I2C_DEBUG_CORE"): The culprit is the dev_dbg printk in the i2c uevent handler. If this is acti

[PATCH AUTOSEL 4.9 8/9] ufs: fix braino in ufs_get_inode_gid() for solaris UFS flavour

2019-05-16 Thread Sasha Levin
From: Al Viro [ Upstream commit 4e9036042fedaffcd868d7f7aa948756c48c637d ] To choose whether to pick the GID from the old (16bit) or new (32bit) field, we should check if the old gid field is set to 0x. Mainline checks the old *UID* field instead - cut'n'paste from the corresponding code in

[PATCH AUTOSEL 4.4 4/8] xfrm4: Fix uninitialized memory read in _decode_session4

2019-05-16 Thread Sasha Levin
From: Steffen Klassert [ Upstream commit 8742dc86d0c7a9628117a989c11f04a9b6b898f3 ] We currently don't reload pointers pointing into skb header after doing pskb_may_pull() in _decode_session4(). So in case pskb_may_pull() changed the pointers, we read from random memory. Fix this by putting all

[PATCH AUTOSEL 4.4 6/8] power: supply: sysfs: prevent endless uevent loop with CONFIG_POWER_SUPPLY_DEBUG

2019-05-16 Thread Sasha Levin
From: Andrey Smirnov [ Upstream commit 349ced9984ff540ce74ca8a0b2e9b03dc434b9dd ] Fix a similar endless event loop as was done in commit 8dcf32175b4e ("i2c: prevent endless uevent loop with CONFIG_I2C_DEBUG_CORE"): The culprit is the dev_dbg printk in the i2c uevent handler. If this is acti

[PATCH AUTOSEL 3.18 1/6] xfrm: policy: Fix out-of-bound array accesses in __xfrm_policy_unlink

2019-05-16 Thread Sasha Levin
From: YueHaibing [ Upstream commit b805d78d300bcf2c83d6df7da0c818b0fee41427 ] UBSAN report this: UBSAN: Undefined behaviour in net/xfrm/xfrm_policy.c:1289:24 index 6 is out of range for type 'unsigned int [6]' CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.162-514.55.6.9.x86_64+ #13 Hardware nam

Re: [alsa-devel] [PATCH V4] ASoC: cs42xx8: add reset-gpios in binding document

2019-05-16 Thread S.j. Wang
Hi > On Thu, May 16, 2019 at 8:36 AM S.j. Wang > wrote: > > > cs42888: codec@48 { > > @@ -25,4 +30,5 @@ cs42888: codec@48 { > > VD-supply = <®_audio>; > > VLS-supply = <®_audio>; > > VLC-supply = <®_audio>; > > + reset-gpios = <&pca9557_b 1 1>; > > reset-gpios =

[PATCH AUTOSEL 4.4 1/8] xfrm: policy: Fix out-of-bound array accesses in __xfrm_policy_unlink

2019-05-16 Thread Sasha Levin
From: YueHaibing [ Upstream commit b805d78d300bcf2c83d6df7da0c818b0fee41427 ] UBSAN report this: UBSAN: Undefined behaviour in net/xfrm/xfrm_policy.c:1289:24 index 6 is out of range for type 'unsigned int [6]' CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.162-514.55.6.9.x86_64+ #13 Hardware nam

Re: [PATCH v2 0/3] initramfs: add support for xattrs in the initial ram disk

2019-05-16 Thread Roberto Sassu
On 5/16/2019 7:29 AM, Arvind Sankar wrote: On Wed, May 15, 2019 at 07:06:52PM +0200, Roberto Sassu wrote: On 5/15/2019 6:08 PM, Arvind Sankar wrote: On Wed, May 15, 2019 at 01:19:04PM +0200, Roberto Sassu wrote: On 5/15/2019 2:52 AM, Arvind Sankar wrote: I don't understand what you mean? The

boot regression on da850-evm with commit f979c08f7624

2019-05-16 Thread Sekhar Nori
Hi Axel Lin, Your commit f979c08f7624 ("regulator: tps6507x: Convert to regulator core's simplified DT parsing code") causes a boot regression on da850- evm. The device-tree file is arch/arm/boot/dts/da850-evm.dts Full logs below. tps_board in tps6507x_pmic_probe() is NULL. The check for init_

[PATCH AUTOSEL 4.4 8/8] perf bench numa: Add define for RUSAGE_THREAD if not present

2019-05-16 Thread Sasha Levin
From: Arnaldo Carvalho de Melo [ Upstream commit bf561d3c13423fc54daa19b5d49dc15fafdb7acc ] While cross building perf to the ARC architecture on a fedora 30 host, we were failing with: CC /tmp/build/perf/bench/numa.o bench/numa.c: In function ‘worker_thread’: bench/numa.c:1261:1

[PATCH AUTOSEL 4.4 2/8] xfrm6_tunnel: Fix potential panic when unloading xfrm6_tunnel module

2019-05-16 Thread Sasha Levin
From: Su Yanjun [ Upstream commit 6ee02a54ef990a71bf542b6f0a4e3321de9d9c66 ] When unloading xfrm6_tunnel module, xfrm6_tunnel_fini directly frees the xfrm6_tunnel_spi_kmem. Maybe someone has gotten the xfrm6_tunnel_spi, so need to wait it. Fixes: 91cc3bb0b04ff("xfrm6_tunnel: RCU conversion") Si

[PATCH AUTOSEL 4.4 7/8] ufs: fix braino in ufs_get_inode_gid() for solaris UFS flavour

2019-05-16 Thread Sasha Levin
From: Al Viro [ Upstream commit 4e9036042fedaffcd868d7f7aa948756c48c637d ] To choose whether to pick the GID from the old (16bit) or new (32bit) field, we should check if the old gid field is set to 0x. Mainline checks the old *UID* field instead - cut'n'paste from the corresponding code in

[PATCH AUTOSEL 3.18 5/6] ufs: fix braino in ufs_get_inode_gid() for solaris UFS flavour

2019-05-16 Thread Sasha Levin
From: Al Viro [ Upstream commit 4e9036042fedaffcd868d7f7aa948756c48c637d ] To choose whether to pick the GID from the old (16bit) or new (32bit) field, we should check if the old gid field is set to 0x. Mainline checks the old *UID* field instead - cut'n'paste from the corresponding code in

[PATCH AUTOSEL 3.18 4/6] mac80211: Fix kernel panic due to use of txq after free

2019-05-16 Thread Sasha Levin
From: Bhagavathi Perumal S [ Upstream commit f1267cf3c01b12e0f843fb6a7450a7f0b2efab8a ] The txq of vif is added to active_txqs list for ATF TXQ scheduling in the function ieee80211_queue_skb(), but it was not properly removed before freeing the txq object. It was causing use after free of the tx

[PATCH AUTOSEL 3.18 2/6] xfrm6_tunnel: Fix potential panic when unloading xfrm6_tunnel module

2019-05-16 Thread Sasha Levin
From: Su Yanjun [ Upstream commit 6ee02a54ef990a71bf542b6f0a4e3321de9d9c66 ] When unloading xfrm6_tunnel module, xfrm6_tunnel_fini directly frees the xfrm6_tunnel_spi_kmem. Maybe someone has gotten the xfrm6_tunnel_spi, so need to wait it. Fixes: 91cc3bb0b04ff("xfrm6_tunnel: RCU conversion") Si

[PATCH AUTOSEL 4.14 07/16] securityfs: fix use-after-free on symlink traversal

2019-05-16 Thread Sasha Levin
From: Al Viro [ Upstream commit 46c874419652bbefdfed17420fd6e88d8a31d9ec ] symlink body shouldn't be freed without an RCU delay. Switch securityfs to ->destroy_inode() and use of call_rcu(); free both the inode and symlink body in the callback. Signed-off-by: Al Viro Signed-off-by: Sasha Levi

[PATCH AUTOSEL 4.14 13/16] sched/cpufreq: Fix kobject memleak

2019-05-16 Thread Sasha Levin
From: "Tobin C. Harding" [ Upstream commit 9a4f26cc98d81b67ecc23b890c28e2df324e29f3 ] Currently the error return path from kobject_init_and_add() is not followed by a call to kobject_put() - which means we are leaking the kobject. Fix it by adding a call to kobject_put() in the error path of ko

[PATCH AUTOSEL 4.14 10/16] KVM: arm/arm64: Ensure vcpu target is unset on reset failure

2019-05-16 Thread Sasha Levin
From: Andrew Jones [ Upstream commit 811328fc3222f7b55846de0cd0404339e2e1e6d7 ] A failed KVM_ARM_VCPU_INIT should not set the vcpu target, as the vcpu target is used by kvm_vcpu_initialized() to determine if other vcpu ioctls may proceed. We need to set the target before calling kvm_reset_vcpu()

[PATCH AUTOSEL 4.14 12/16] iwlwifi: mvm: check for length correctness in iwl_mvm_create_skb()

2019-05-16 Thread Sasha Levin
From: Luca Coelho [ Upstream commit de1887c064b9996ac03120d90d0a909a3f678f98 ] We don't check for the validity of the lengths in the packet received from the firmware. If the MPDU length received in the rx descriptor is too short to contain the header length and the crypt length together, we ma

[PATCH AUTOSEL 4.14 06/16] power: supply: cpcap-battery: Fix division by zero

2019-05-16 Thread Sasha Levin
From: Tony Lindgren [ Upstream commit dbe7208c6c4aec083571f2ec742870a0d0edbea3 ] If called fast enough so samples do not increment, we can get division by zero in kernel: __div0 cpcap_battery_cc_raw_div cpcap_battery_get_property power_supply_get_property.part.1 power_supply_get_property power_

[PATCH AUTOSEL 4.14 16/16] perf bench numa: Add define for RUSAGE_THREAD if not present

2019-05-16 Thread Sasha Levin
From: Arnaldo Carvalho de Melo [ Upstream commit bf561d3c13423fc54daa19b5d49dc15fafdb7acc ] While cross building perf to the ARC architecture on a fedora 30 host, we were failing with: CC /tmp/build/perf/bench/numa.o bench/numa.c: In function ‘worker_thread’: bench/numa.c:1261:1

[PATCH AUTOSEL 4.14 14/16] x86/mm/mem_encrypt: Disable all instrumentation for early SME setup

2019-05-16 Thread Sasha Levin
From: Gary Hook [ Upstream commit b51ce3744f115850166f3d6c292b9c8cb849ad4f ] Enablement of AMD's Secure Memory Encryption feature is determined very early after start_kernel() is entered. Part of this procedure involves scanning the command line for the parameter 'mem_encrypt'. To determine int

[PATCH AUTOSEL 4.19 25/25] perf/x86/intel: Fix race in intel_pmu_disable_event()

2019-05-16 Thread Sasha Levin
From: Jiri Olsa [ Upstream commit 6f55967ad9d9752813e36de6d5fdbd19741adfc7 ] New race in x86_pmu_stop() was introduced by replacing the atomic __test_and_clear_bit() of cpuc->active_mask by separate test_bit() and __clear_bit() calls in the following commit: 3966c3feca3f ("x86/perf/amd: Remov

[PATCH AUTOSEL 4.19 12/25] PCI: Fix issue with "pci=disable_acs_redir" parameter being ignored

2019-05-16 Thread Sasha Levin
From: Logan Gunthorpe [ Upstream commit d5bc73f34cc97c4b4b9202cc93182c2515076edf ] In most cases, kmalloc() will not be available early in boot when pci_setup() is called. Thus, the kstrdup() call that was added to fix the __initdata bug with the disable_acs_redir parameter usually returns NULL

[PATCH AUTOSEL 4.19 09/25] power: supply: cpcap-battery: Fix division by zero

2019-05-16 Thread Sasha Levin
From: Tony Lindgren [ Upstream commit dbe7208c6c4aec083571f2ec742870a0d0edbea3 ] If called fast enough so samples do not increment, we can get division by zero in kernel: __div0 cpcap_battery_cc_raw_div cpcap_battery_get_property power_supply_get_property.part.1 power_supply_get_property power_

[PATCH AUTOSEL 4.19 11/25] apparmorfs: fix use-after-free on symlink traversal

2019-05-16 Thread Sasha Levin
From: Al Viro [ Upstream commit f51dcd0f621caac5380ce90fbbeafc32ce4517ae ] symlink body shouldn't be freed without an RCU delay. Switch apparmorfs to ->destroy_inode() and use of call_rcu(); free both the inode and symlink body in the callback. Signed-off-by: Al Viro Signed-off-by: Sasha Levi

[PATCH AUTOSEL 4.19 18/25] bpf: Fix preempt_enable_no_resched() abuse

2019-05-16 Thread Sasha Levin
From: Peter Zijlstra [ Upstream commit 0edd6b64d1939e9e9168ff27947995bb7751db5d ] Unless the very next line is schedule(), or implies it, one must not use preempt_enable_no_resched(). It can cause a preemption to go missing and thereby cause arbitrary delays, breaking the PREEMPT=y invariant. C

[PATCH AUTOSEL 5.0 30/34] ufs: fix braino in ufs_get_inode_gid() for solaris UFS flavour

2019-05-16 Thread Sasha Levin
From: Al Viro [ Upstream commit 4e9036042fedaffcd868d7f7aa948756c48c637d ] To choose whether to pick the GID from the old (16bit) or new (32bit) field, we should check if the old gid field is set to 0x. Mainline checks the old *UID* field instead - cut'n'paste from the corresponding code in

[PATCH AUTOSEL 5.0 26/34] sched/cpufreq: Fix kobject memleak

2019-05-16 Thread Sasha Levin
From: "Tobin C. Harding" [ Upstream commit 9a4f26cc98d81b67ecc23b890c28e2df324e29f3 ] Currently the error return path from kobject_init_and_add() is not followed by a call to kobject_put() - which means we are leaking the kobject. Fix it by adding a call to kobject_put() in the error path of ko

[PATCH AUTOSEL 4.19 02/25] xfrm6_tunnel: Fix potential panic when unloading xfrm6_tunnel module

2019-05-16 Thread Sasha Levin
From: Su Yanjun [ Upstream commit 6ee02a54ef990a71bf542b6f0a4e3321de9d9c66 ] When unloading xfrm6_tunnel module, xfrm6_tunnel_fini directly frees the xfrm6_tunnel_spi_kmem. Maybe someone has gotten the xfrm6_tunnel_spi, so need to wait it. Fixes: 91cc3bb0b04ff("xfrm6_tunnel: RCU conversion") Si

[PATCH AUTOSEL 5.0 22/34] tools: bpftool: fix infinite loop in map create

2019-05-16 Thread Sasha Levin
From: Alban Crequy [ Upstream commit 8694d8c1f82cccec9380e0d3720b84eee315dfb7 ] "bpftool map create" has an infinite loop on "while (argc)". The error case is missing. Symptoms: when forgetting to type the keyword 'type' in front of 'hash': $ sudo bpftool map create /sys/fs/bpf/dir/foobar hash

[PATCH AUTOSEL 4.19 01/25] xfrm: policy: Fix out-of-bound array accesses in __xfrm_policy_unlink

2019-05-16 Thread Sasha Levin
From: YueHaibing [ Upstream commit b805d78d300bcf2c83d6df7da0c818b0fee41427 ] UBSAN report this: UBSAN: Undefined behaviour in net/xfrm/xfrm_policy.c:1289:24 index 6 is out of range for type 'unsigned int [6]' CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.162-514.55.6.9.x86_64+ #13 Hardware nam

[PATCH AUTOSEL 5.0 24/34] qmi_wwan: new Wistron, ZTE and D-Link devices

2019-05-16 Thread Sasha Levin
From: Bjørn Mork [ Upstream commit 88ef66a28391ea7b624bfb7508a5b015c13b28f3 ] Adding device entries found in vendor modified versions of this driver. Function maps for some of the devices follow: WNC D16Q1, D16Q5, D18Q1 LTE CAT3 module (1435:0918) MI_00 Qualcomm HS-USB Diagnostics MI_01 Andro

[PATCH AUTOSEL 5.0 15/34] apparmorfs: fix use-after-free on symlink traversal

2019-05-16 Thread Sasha Levin
From: Al Viro [ Upstream commit f51dcd0f621caac5380ce90fbbeafc32ce4517ae ] symlink body shouldn't be freed without an RCU delay. Switch apparmorfs to ->destroy_inode() and use of call_rcu(); free both the inode and symlink body in the callback. Signed-off-by: Al Viro Signed-off-by: Sasha Levi

[PATCH AUTOSEL 5.0 10/34] clk: sunxi-ng: nkmp: Avoid GENMASK(-1, 0)

2019-05-16 Thread Sasha Levin
From: Jernej Skrabec [ Upstream commit 2abc330c514fe56c570bb1a6318b054b06a4f72e ] Sometimes one of the nkmp factors is unused. This means that one of the factors shift and width values are set to 0. Current nkmp clock code generates a mask for each factor with GENMASK(width + shift - 1, shift).

[PATCH AUTOSEL 5.0 31/34] i2c: designware: ratelimit 'transfer when suspended' errors

2019-05-16 Thread Sasha Levin
From: Wolfram Sang [ Upstream commit 6bac9bc273cdab6157ad7a2ead09400aabfc445b ] There are two problems with dev_err() here. One: It is not ratelimited. Two: We don't see which driver tried to transfer something with a suspended adapter. Switch to dev_WARN_ONCE to fix both issues. Drawback is tha

Re: [alsa-devel] [PATCH V4] ASoC: cs42xx8: add reset-gpios in binding document

2019-05-16 Thread Fabio Estevam
On Thu, May 16, 2019 at 8:36 AM S.j. Wang wrote: > cs42888: codec@48 { > @@ -25,4 +30,5 @@ cs42888: codec@48 { > VD-supply = <®_audio>; > VLS-supply = <®_audio>; > VLC-supply = <®_audio>; > + reset-gpios = <&pca9557_b 1 1>; reset-gpios = <&pca9557_b 1 GPIO_ACTIVE_

Re: [alsa-devel] [PATCH RESEND V3] ASoC: cs42xx8: add reset-gpio in binding document

2019-05-16 Thread Fabio Estevam
On Thu, May 16, 2019 at 8:25 AM S.j. Wang wrote: > cs42888: codec@48 { > @@ -25,4 +30,5 @@ cs42888: codec@48 { > VD-supply = <®_audio>; > VLS-supply = <®_audio>; > VLC-supply = <®_audio>; > + reset-gpio = <&pca9557_b 1 1>; Please use GPIO_ACTIVE_LOW instead as it m

[PATCH V4] ASoC: cs42xx8: add reset-gpios in binding document

2019-05-16 Thread S.j. Wang
Add reset-gpios property, which is optional. Signed-off-by: Shengjiu Wang --- Changes in V4 - use gpios instead of gpio Changes in RESEND v3 - send updated binding document only Changes in v3 - update binding document. Changes in v2 - use devm_gpiod_get_optional instead of of_get_named_gpio

Re: [PATCH 4/4] uapi: Wire up the mount API syscalls on non-x86 arches

2019-05-16 Thread Arnd Bergmann
On Thu, May 16, 2019 at 1:24 PM David Howells wrote: > > Wire up the mount API syscalls on non-x86 arches. > > Reported-by: Arnd Bergmann > Signed-off-by: David Howells Reviewed-by: Arnd Bergmann but found a small mistake that breaks compilation on the asm-generic architectures: > diff --git

RE: [EXT] Re: [PATCH RESEND V3] ASoC: cs42xx8: add reset-gpio in binding document

2019-05-16 Thread S.j. Wang
Hi > > > +Optional properties: > > + > > + - reset-gpio : a GPIO spec to define which pin is connected to the chip's > > +!RESET pin > > gpio properties are supposed to be called -gpios even if there's a single > GPIO possible due to DT rules. The code will accept plain -gpio but the > do

Re: [RFC PATCH 2/4] KVM: selftests: Align memory region addresses to 1M on s390x

2019-05-16 Thread David Hildenbrand
On 16.05.19 13:12, Thomas Huth wrote: > On s390x, there is a constraint that memory regions have to be aligned > to 1M (or running the VM will fail). Introduce a new "alignment" variable > in the vm_userspace_mem_region_add() function which now can be used for > both, huge page and s390x alignment

[no subject]

2019-05-16 Thread MARTINS DONALD
Hello dear Friend,My Name is (Farouk Martins Abdel ) From Libya in North Africa, I have escaped from my country to Togo were i am under (Alliance missionary home) after my rebel have murdered my parents. My late father MAJOR GENERAL, (ABDEL FATTAH YOUNES ) He held the rank of Major General and the

Re: [PATCH 3/4] uapi, x86: Fix the syscall numbering of the mount API syscalls

2019-05-16 Thread Arnd Bergmann
On Thu, May 16, 2019 at 1:24 PM David Howells wrote: > > Fix the syscall numbering of the mount API syscalls so that the numbers > match between i386 and x86_64 and that they're in the common numbering > scheme space. > > Fixes: a07b20004793 ("vfs: syscall: Add open_tree(2) to reference or clone a

Re: [PATCH] spi: spidev: Add dhcom-board to compatibility list [Klartext]

2019-05-16 Thread Fabio Estevam
Hi Christoph, It seems that the [Klartext] string is added in the Subject by mistake? On Thu, May 16, 2019 at 8:23 AM Christoph Niedermaier wrote: > > Prepare to use devices on the external SPI interface > on a DH electronics Development Board. > > Signed-off-by: Christoph Niedermaier

Re: [PATCH RESEND V3] ASoC: cs42xx8: add reset-gpio in binding document

2019-05-16 Thread Mark Brown
On Thu, May 16, 2019 at 11:24:12AM +, S.j. Wang wrote: > +Optional properties: > + > + - reset-gpio : a GPIO spec to define which pin is connected to the chip's > +!RESET pin gpio properties are supposed to be called -gpios even if there's a single GPIO possible due to DT rules. The cod

[PATCH 3/4] uapi, x86: Fix the syscall numbering of the mount API syscalls

2019-05-16 Thread David Howells
Fix the syscall numbering of the mount API syscalls so that the numbers match between i386 and x86_64 and that they're in the common numbering scheme space. Fixes: a07b20004793 ("vfs: syscall: Add open_tree(2) to reference or clone a mount") Fixes: 2db154b3ea8e ("vfs: syscall: Add move_mount(2) t

[PATCH RESEND V3] ASoC: cs42xx8: add reset-gpio in binding document

2019-05-16 Thread S.j. Wang
Add reset-gpio property, which is an optional option Signed-off-by: Shengjiu Wang --- Changes in RESEND v3 - send updated binding document only Changes in v3 - update binding document. Changes in v2 - use devm_gpiod_get_optional instead of of_get_named_gpio Documentation/devicetree/bindings/s

[PATCH 4/4] uapi: Wire up the mount API syscalls on non-x86 arches

2019-05-16 Thread David Howells
Wire up the mount API syscalls on non-x86 arches. Reported-by: Arnd Bergmann Signed-off-by: David Howells --- arch/alpha/kernel/syscalls/syscall.tbl |6 ++ arch/arm/tools/syscall.tbl |6 ++ arch/arm64/include/asm/unistd32.h | 12 a

[PATCH 0/4] uapi, vfs: Change the mount API UAPI

2019-05-16 Thread David Howells
Hi Linus, Al, Here are some patches that make changes to the mount API UAPI and two of them really need applying, before -rc1 - if they're going to be applied at all. The following changes are made: (1) Make the file descriptors returned by open_tree(), fsopen(), fspick() and fsmount() O

Re: [PATCH] drivers: md: Unify common definitions of raid1 and raid10

2019-05-16 Thread Marcos Paulo de Souza
ping. On Thu, May 09, 2019 at 08:18:49AM -0300, Marcos Paulo de Souza wrote: > These definitions are being moved to raid1-10.c. > > Signed-off-by: Marcos Paulo de Souza > --- > drivers/md/raid1-10.c | 25 + > drivers/md/raid1.c| 29 ++--- > dr

[PATCH 1/4] uapi, fs: make all new mount api fds cloexec by default

2019-05-16 Thread David Howells
From: Christian Brauner This makes all file descriptors returned from new syscalls of the new mount api cloexec by default. >From a userspace perspective it is rarely the case that fds are supposed to be inherited across exec. Having them not cloexec by default forces userspace to remember to pa

[PATCH 2/4] uapi, fsopen: use square brackets around "fscontext"

2019-05-16 Thread David Howells
From: Christian Brauner Make the name of the anon inode fd "[fscontext]" instead of "fscontext". This is minor but most core-kernel anon inode fds already carry square brackets around their name: [eventfd] [eventpoll] [fanotify] [io_uring] [pidfd] [signalfd] [timerfd] [userfaultfd] For the sake

[PATCH] staging: vt6656: returns error code on vnt_int_start_interrupt fail

2019-05-16 Thread Quentin Deslandes
Returns error code from 'vnt_int_start_interrupt()' so the device's private buffers will be correctly freed and 'struct ieee80211_hw' start function will return an error code. Signed-off-by: Quentin Deslandes --- v2: instead of removing status variable, returns its value to caller and handle

[PATCH] spi: spidev: Add dhcom-board to compatibility list [Klartext]

2019-05-16 Thread Christoph Niedermaier
Prepare to use devices on the external SPI interface on a DH electronics Development Board. Signed-off-by: Christoph Niedermaier --- drivers/spi/spidev.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/spi/spidev.c b/drivers/spi/spidev.c index b0c76e2626ce..61ec1dce557f 100644 --- a/

Re: [RFC PATCH 1/4] KVM: selftests: Guard struct kvm_vcpu_events with __KVM_HAVE_VCPU_EVENTS

2019-05-16 Thread David Hildenbrand
On 16.05.19 13:12, Thomas Huth wrote: > The struct kvm_vcpu_events code is only available on certain architectures > (arm, arm64 and x86). To be able to compile kvm_util.c also for other > architectures, we've got to fence the code with __KVM_HAVE_VCPU_EVENTS. > > Signed-off-by: Thomas Huth > ---

Re: [PATCH v2] pinctrl: rockchip: fix leaked of_node references

2019-05-16 Thread Linus Walleij
On Mon, Apr 15, 2019 at 8:23 AM Wen Yang wrote: > The call to of_parse_phandle returns a node pointer with refcount > incremented thus it must be explicitly decremented after the last > usage. > > Detected by coccinelle with the following warnings: > ./drivers/pinctrl/pinctrl-rockchip.c:3221:2-8:

RE: [PATCH V3 2/4] nvmem: imx: add i.MX8 nvmem driver

2019-05-16 Thread Aisheng Dong
> From: Peng Fan > Sent: Wednesday, May 15, 2019 3:53 PM > > This patch adds i.MX8 nvmem ocotp driver to access fuse via RPC to i.MX8 > system controller. > > Cc: Srinivas Kandagatla > Cc: Shawn Guo > Cc: Sascha Hauer > Cc: Pengutronix Kernel Team > Cc: Fabio Estevam > Cc: NXP Linux Team >

Re: [PATCH v2 1/2] dt-bindings: Add vendor prefix for HopeRun

2019-05-16 Thread Simon Horman
On Wed, May 15, 2019 at 05:34:42PM +0100, Fabrizio Castro wrote: > Add "Jiangsu HopeRun Software Co., Ltd." to the list of devicetree > vendor prefixes as "hoperun". > > Website: http://www.hoperun.com/en > > Signed-off-by: Fabrizio Castro > Reviewed-by: Chris Paterson Reviewed-by: Simon Horma

Re: [PATCH 1/2] dt-bindings: Add vendor prefix for HopeRun

2019-05-16 Thread Simon Horman
On Wed, May 15, 2019 at 12:44:56PM +0100, Fabrizio Castro wrote: > Add "Jiangsu HopeRun Software Co., Ltd." to the list of devicetree > vendor prefixes as "hoperun". > > Website: http://www.hoperun.com/en > > Signed-off-by: Fabrizio Castro > Reviewed-by: Chris Paterson Reviewed-by: Simon Horma

Re: [PATCH V3 2/4] arm64/mm: Hold memory hotplug lock while walking for kernel page table dump

2019-05-16 Thread Michal Hocko
On Thu 16-05-19 16:36:12, Anshuman Khandual wrote: > On 05/16/2019 03:53 PM, Mark Rutland wrote: > > Hi Michal, > > > > On Wed, May 15, 2019 at 06:58:47PM +0200, Michal Hocko wrote: > >> On Tue 14-05-19 14:30:05, Anshuman Khandual wrote: > >>> The arm64 pagetable dump code can race with concurrent

RE: [EXT] Re: [PATCH V2] ASoC: cs42xx8: Add reset gpio handling

2019-05-16 Thread S.j. Wang
Hi > > On Thu, May 16, 2019 at 11:09:27AM +, S.j. Wang wrote: > > > > You also need a binding document update for this. > > ok, will send v3 > > Separate patch please, I already applied this and binding docs should be > separate patches anyway. Ok, I already send v3. please forget the v3,

Re: [PATCH] clk: imx: imx8mm: fix int pll clk gate

2019-05-16 Thread Fabio Estevam
Hi Peng, On Thu, May 16, 2019 at 6:08 AM Peng Fan wrote: > > To Frac pll, the gate shift is 13, however to Int PLL the gate shift > is 11. > > Signed-off-by: Peng Fan > Reviewed-by: Jacky Bai Reviewed-by: Fabio Estevam Please add a Fixes tag and Cc stable. Thanks

Applied "ASoC: dapm: allow muxes to force a disconnect" to the asoc tree

2019-05-16 Thread Mark Brown
The patch ASoC: dapm: allow muxes to force a disconnect has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "ASoC: meson: add g12a tohdmitx control" to the asoc tree

2019-05-16 Thread Mark Brown
The patch ASoC: meson: add g12a tohdmitx control has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: meson: axg-card: add basic codec-to-codec link support" to the asoc tree

2019-05-16 Thread Mark Brown
The patch ASoC: meson: axg-card: add basic codec-to-codec link support has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

Applied "ASoC: meson: add tohdmitx DT bindings" to the asoc tree

2019-05-16 Thread Mark Brown
The patch ASoC: meson: add tohdmitx DT bindings has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to

Applied "ASoC: meson: axg-card: set link name based on link node name" to the asoc tree

2019-05-16 Thread Mark Brown
The patch ASoC: meson: axg-card: set link name based on link node name has been applied to the asoc tree at https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-5.3 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next

[RFC PATCH 0/4] KVM selftests for s390x

2019-05-16 Thread Thomas Huth
This patch series enables the KVM selftests for s390x. As a first test, the sync_regs from x86 has been adapted to s390x. Please note that the ucall() interface is not used yet - since s390x neither has PIO nor MMIO, this needs some more work first before it becomes usable (we likely should use a

RE: [PATCH V3 1/2] soc: imx: Add SCU SoC info driver support

2019-05-16 Thread Aisheng Dong
> From: Anson Huang > Sent: Thursday, May 16, 2019 11:25 AM > > Add i.MX SCU SoC info driver to support i.MX8QXP SoC, introduce driver > dependency into Kconfig as CONFIG_IMX_SCU must be selected to support > i.MX SCU SoC driver, also need to use platform driver model to make sure > IMX_SCU driver

Re: [PATCH V2] ASoC: cs42xx8: Add reset gpio handling

2019-05-16 Thread Mark Brown
On Thu, May 16, 2019 at 11:09:27AM +, S.j. Wang wrote: > > You also need a binding document update for this. > ok, will send v3 Separate patch please, I already applied this and binding docs should be separate patches anyway. signature.asc Description: PGP signature

[RFC PATCH 1/4] KVM: selftests: Guard struct kvm_vcpu_events with __KVM_HAVE_VCPU_EVENTS

2019-05-16 Thread Thomas Huth
The struct kvm_vcpu_events code is only available on certain architectures (arm, arm64 and x86). To be able to compile kvm_util.c also for other architectures, we've got to fence the code with __KVM_HAVE_VCPU_EVENTS. Signed-off-by: Thomas Huth --- tools/testing/selftests/kvm/include/kvm_util.h |

[RFC PATCH 4/4] KVM: selftests: Add the sync_regs test for s390x

2019-05-16 Thread Thomas Huth
The test is an adaption of the same test for x86. Note that there are some differences in the way how s390x deals with the kvm_valid_regs in struct kvm_run, so some of the tests had to be removed. Also this test is not using the ucall() interface on s390x yet (which would need some work to be usabl

[RFC PATCH 3/4] KVM: selftests: Add processor code for s390x

2019-05-16 Thread Thomas Huth
Code that takes care of basic CPU setup, page table walking, etc. Signed-off-by: Thomas Huth --- MAINTAINERS | 1 + tools/testing/selftests/kvm/Makefile | 1 + .../selftests/kvm/include/s390x/processor.h | 22 ++ .../selftests/kvm/lib/s390x/proce

[RFC PATCH 2/4] KVM: selftests: Align memory region addresses to 1M on s390x

2019-05-16 Thread Thomas Huth
On s390x, there is a constraint that memory regions have to be aligned to 1M (or running the VM will fail). Introduce a new "alignment" variable in the vm_userspace_mem_region_add() function which now can be used for both, huge page and s390x alignment requirements. Signed-off-by: Thomas Huth ---

Re: [PATCH] ACPI / LPSS: Don't skip late system PM ops for hibernate on BYT/CHT

2019-05-16 Thread Rafael J. Wysocki
On Thursday, April 25, 2019 6:38:34 PM CEST Robert R. Howell wrote: > On 4/24/19 1:20 AM, Rafael J. Wysocki wrote: > > > On Tue, Apr 23, 2019 at 10:03 PM Robert R. Howell wrote: > >> > >> On 4/23/19 2:07 AM, Rafael J. Wysocki wrote: > >>> > >>> On Sat, Apr 20, 2019 at 12:44 AM Robert R. Howell

[PATCH V3] ASoC: cs42xx8: Add reset gpio handling

2019-05-16 Thread S.j. Wang
Handle the reset GPIO and reset the device every time we start it. Signed-off-by: Shengjiu Wang --- Changes in v3 - update binding document. Changes in v2 - use devm_gpiod_get_optional instead of of_get_named_gpio Documentation/devicetree/bindings/sound/cs42xx8.txt | 6 ++ sound/soc/codec

Re: [PATCH V2] ASoC: cs42xx8: Add reset gpio handling

2019-05-16 Thread S.j. Wang
Hi > > On Thu, May 16, 2019 at 06:04:58AM +, S.j. Wang wrote: > > > + cs42xx8->gpiod_reset = devm_gpiod_get_optional(dev, "reset", > > + GPIOD_OUT_HIGH); > > + if (IS_ERR(cs42xx8->gpiod_reset)) > > + return PTR_ERR(cs42xx8->gpio

RE: [PATCH V3 1/2] soc: imx: Add SCU SoC info driver support

2019-05-16 Thread Anson Huang
Hi, Leonard > -Original Message- > From: Leonard Crestez > Sent: Thursday, May 16, 2019 6:07 PM > To: Anson Huang ; shawn...@kernel.org > Cc: catalin.mari...@arm.com; will.dea...@arm.com; > s.ha...@pengutronix.de; ker...@pengutronix.de; feste...@gmail.com; > agr...@kernel.org; maxime.rip..

Re: [PATCH V3 2/4] arm64/mm: Hold memory hotplug lock while walking for kernel page table dump

2019-05-16 Thread Anshuman Khandual
On 05/16/2019 03:53 PM, Mark Rutland wrote: > Hi Michal, > > On Wed, May 15, 2019 at 06:58:47PM +0200, Michal Hocko wrote: >> On Tue 14-05-19 14:30:05, Anshuman Khandual wrote: >>> The arm64 pagetable dump code can race with concurrent modification of the >>> kernel page tables. When a leaf entrie

Re: [PATCH 3/3] char: misc: Move EXPORT_SYMBOL immediately next to the functions/varibles

2019-05-16 Thread Naveen Kumar Parna
On Wed, 15 May 2019 at 20:43, Greg KH wrote: > > On Wed, May 15, 2019 at 07:47:31PM +0530, parna.naveenku...@gmail.com wrote: > > From: Naveen Kumar Parna > > > > According to checkpatch: EXPORT_SYMBOL(foo); should immediately follow its > > function/variable. > > > > This patch fixes the followi

<    2   3   4   5   6   7   8   9   >