[PATCH] smp_call_function: use inline helpers instead of macros

A new caller of smp_call_function() passes a local variable as the 'wait' argument, and that variable is otherwise unused, so we get a warning in non-SMP configurations: virt/kvm/kvm_main.c: In function 'kvm_make_all_cpus_request': virt/kvm/kvm_main.c:195:7: error: unused variable 'wait' [-Werror

[PATCH 4.9 022/103] arm64: Improve detection of user/non-user mappings in set_pte(_at)

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Catalin Marinas commit ec663d967b2276448a416406ca59ff247c0c80c5 upstream. Commit cab15ce604e5 ("arm64: Introduce execute-only page access permissions") allowed a valid user PTE to have the PTE_

[PATCH 4.9 024/103] ARM: dts: NSP: GPIO reboot open-source

4.9-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 duri

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

On 11/05/17 16:01, Mark Rutland wrote: Currently, cpus_set_cap() calls static_branch_enable_cpuslocked(), which must take the jump_label mutex. We call cpus_set_cap() in the secondary bringup path, from the idle thread where interrupts are disabled. Taking a mutex in this path "is a NONO" regard

[PATCH 4.9 018/103] power: supply: bq24190_charger: Dont read fault register outside irq_handle_thread()

4.9-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 irq_handle_thr

[PATCH 4.9 020/103] arm64: dts: r8a7795: Mark EthernetAVB device node disabled

4.9-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 board-spe

[PATCH 4.9 019/103] power: supply: bq24190_charger: Handle fault before status on interrupt

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit ba52e75718784fda1b683ee0bfded72a0b83b047 upstream. Reading both fault and status registers and logging any fault should take priority over handling status register update. Fi

[PATCH 4.9 002/103] drm/sti: fix GDP size to support up to UHD resolution

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Vincent Abriou commit 2f410f88c0a1c7e19762918d2614f506a7b63a82 upstream. On stih407-410 chip family the GDP layers are able to support up to UHD resolution (3840 x 2160). Signed-off-by: Vincen

[PATCH 4.9 016/103] power: supply: bq24190_charger: Install irq_handler_thread() at end of probe()

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Liam Breck commit d62acc5ef0621463446091ebd7a345e06e9ab80c upstream. The device specific data is not fully initialized on request_threaded_irq(). This may cause a crash when the IRQ handler tri

Re: pinctrl-sx150x.c broken in 4.11

* Linus Walleij [170511 00:26]: > On Wed, May 10, 2017 at 9:32 PM, Nikita Yushchenko > wrote: > > > Looks like recent pinctrl changes - possibly commit 99e4f67508e1 > > ("pinctrl: core: Use delayed work for hogs") - breaks pinctrl-sx150x > > driver in all setups where it has any pinctrl settings

[PATCH 4.9 017/103] power: supply: bq24190_charger: Call power_supply_changed() for relevant component

4.9-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 wi

[PATCH 4.9 011/103] powerpc/ftrace: Fix confusing help text for DISABLE_MPROFILE_KERNEL

4.9-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 toolc

Re: [PATCH v2] xfs: avoid harmless gcc-7 warnings

On Thu, May 11, 2017 at 05:04:33PM +0200, Arnd Bergmann wrote: > gcc-7 flags the use of integer math inside of a condition > as a potential bug: > > fs/xfs/xfs_bmap_util.c: In function 'xfs_swap_extents_check_format': > fs/xfs/xfs_bmap_util.c:1619:8: error: '<<' in boolean context, did you mean >

[PATCH 4.10 112/129] tcp: fix wraparound issue in tcp_lp

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit a9f11f963a546fea9144f6a6d1a307e814a387e7 ] Be careful when comparing tcp_time_stamp to some u32 quantity, otherwise result can be surprising. Fixes: 7c106d7e78

[PATCH 4.10 120/129] bnxt_en: allocate enough space for ->ntp_fltr_bmap

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter [ Upstream commit ac45bd93a5035c2f39c9862b8b6ed692db0fdc87 ] We have the number of longs, but we need to calculate the number of bytes required. Fixes: c0c050c58d84 ("bnxt_en:

[PATCH 4.10 121/129] bpf: dont let ldimm64 leak map addresses on unprivileged

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit 0d0e57697f162da4aa218b5feafe614fb666db07 ] The patch fixes two things at once: 1) It checks the env->allow_ptr_leaks and only prints the map address to t

[PATCH 4.9 001/103] 9p: fix a potential acl leak

4.9-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 call

[PATCH 4.10 116/129] ipv4, ipv6: ensure raw socket message is big enough to hold an IP header

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Potapenko [ Upstream commit 86f4c90a1c5c1493f07f2d12c1079f5bf01936f2 ] raw_send_hdrinc() and rawv6_send_hdrinc() expect that the buffer copied from the userspace contains the IPv4/I

Re: [Xen-devel] [block-xen-blkback] question about pontential null pointer dereference

Hi Juergen, Quoting Juergen Gross : On 10/05/17 18:49, Gustavo A. R. Silva wrote: Hello everybody, While looking into Coverity ID 1350942 I ran into the following piece of code at drivers/block/xen-blkback/xenbus.c:490: 490static int xen_blkbk_remove(struct xenbus_device *dev) 491{ 492

[PATCH 4.10 118/129] ipv6: initialize route null entry in addrconf_init()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: WANG Cong [ Upstream commit 2f460933f58eee3393aba64f0f6d14acb08d1724 ] Andrey reported a crash on init_net.ipv6.ip6_null_entry->rt6i_idev since it is always NULL. This is clearly wrong, we h

[PATCH 4.10 115/129] tcp: do not inherit fastopen_req from parent

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 8b485ce69876c65db12ed390e7f9c0d2a64eff2c ] Under fuzzer stress, it is possible that a child gets a non NULL fastopen_req pointer from its parent at accept() tim

[PATCH 4.10 119/129] ipv6: reorder ip6_route_dev_notifier after ipv6_dev_notf

4.10-stable review patch. If anyone has any objections, please let me know. -- From: WANG Cong [ Upstream commit 242d3a49a2a1a71d8eb9f953db1bcaa9d698ce00 ] For each netns (except init_net), we initialize its null entry in 3 places: 1) The template itself, as we use kmemdup()

[PATCH 4.10 127/129] drm: mxsfb: drm_dev_alloc() returns error pointers

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit e89e50ac35d9126907a436dabe70f9a8311b9981 upstream. We should be checking for IS_ERR() instead of NULL because drm_dev_alloc() returns error pointers. Fixes: 45d59d704080

[PATCH RT v2] futex/rtmutex: Cure RT double blocking issue

RT has a problem when the wait on a futex/rtmutex got interrupted by a timeout or a signal. task->pi_blocked_on is still set when returning from rt_mutex_wait_proxy_lock(). The task must acquire the hash bucket lock after this. If the hash bucket lock is contended then the BUG_ON(rt_mutex_real_wai

[PATCH 4.10 125/129] xen: Revert commits da72ff5bfcb0 and 72a9b186292d

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Boris Ostrovsky commit 84d582d236dc1f9085e741affc72e9ba061a67c2 upstream. Recent discussion (http://marc.info/?l=xen-devel&m=149192184523741) established that commit 72a9b186292d ("xen: Remove

[PATCH 4.10 123/129] openvswitch: Set internal device max mtu to ETH_MAX_MTU.

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Jarno Rajahalme [ Upstream commit 425df17ce3a26d98f76e2b6b0af2acf4aeb0b026 ] Commit 91572088e3fd ("net: use core MTU range checking in core net infra") changed the openvswitch internal device

[PATCH 4.10 113/129] net: ipv6: Do not duplicate DAD on link up

4.10-stable review patch. If anyone has any objections, please let me know. -- From: David Ahern [ Upstream commit 6d717134a1a6e1b34a7d0d70e953037bc2642046 ] Andrey reported a warning triggered by the rcu code: [ cut here ] WARNING: CPU: 1 PID: 5911 a

[PATCH 4.10 077/129] USB: serial: ssu100: fix control-message error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 1eac5c244f705182d1552a53e2f74e2775ed95d6 upstream. Make sure to detect short control-message transfers rather than continue with zero-initialised data when retrieving modem

[PATCH 4.10 079/129] USB: serial: ti_usb_3410_5052: fix control-message error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 39712e8bfa8d3aa6ce1e60fc9d62c9b076c17a30 upstream. Make sure to detect and return an error on zero-length control-message transfers when reading from the device. This addr

Re: [PATCH] omapfb: Use devm_kcalloc() in vrfb_probe()

On Thursday, May 11, 2017 04:27:19 PM Bartlomiej Zolnierkiewicz wrote: > > @@ -358,11 +358,7 @@ static int __init vrfb_probe(struct platform_device > > *pdev) > > return PTR_ERR(vrfb_base); > > > > num_ctxs = pdev->num_resources - 1; > > - > > - ctxs = devm_kzalloc(&pdev->dev,

[PATCH 4.10 111/129] bpf, arm64: fix jit branch offset related to ldimm64

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Borkmann [ Upstream commit ddc665a4bb4b728b4e6ecec8db1b64efa9184b9c ] When the instruction right before the branch destination is a 64 bit load immediate, we currently calculate the wr

[PATCH 4.10 075/129] USB: serial: keyspan_pda: fix receive sanity checks

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit c528fcb116e61afc379a2e0a0f70906b937f1e2c upstream. Make sure to check for short transfers before parsing the receive buffer to avoid acting on stale data. Fixes: 1da177e4c

[PATCH 4.10 074/129] usb: chipidea: Handle extcon events properly

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit a89b94b53371bbfa582787c2fa3378000ea4263d upstream. We're currently emulating the vbus and id interrupts in the OTGSC read API, but we also need to make sure that if we're h

[PATCH 4.10 110/129] bpf: enhance verifier to understand stack pointer arithmetic

4.10-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 106/129] tcp: do not underestimate skb->truesize in tcp_trim_head()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit 7162fb242cb8322beb558828fd26b33c3e9fc805 ] Andrey found a way to trigger the WARN_ON_ONCE(delta < len) in skb_try_coalesce() using syzkaller and a filter attach

[PATCH 4.10 107/129] net: adjust skb->truesize in ___pskb_trim()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Eric Dumazet [ Upstream commit c21b48cc1bbf2f5af3ef54ada559f7fadf8b508b ] Andrey found a way to trigger the WARN_ON_ONCE(delta < len) in skb_try_coalesce() using syzkaller and a filter attach

[PATCH 4.10 102/129] staging: lustre: ptlrpc: avoid warning on missing return

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit 74e3bb75315ce62a4567f2871276bab32802e8b4 upstream. The newly added function triggers a harmless warning: drivers/staging/lustre/lustre/ptlrpc/pack_generic.c: In function

[PATCH 4.10 103/129] ALSA: hda - Fix deadlock of controller device lock at unbinding

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit ab949d519601880fd46e8bc1445d6a453bf2dc09 upstream. Imre Deak reported a deadlock of HD-audio driver at unbinding while it's still in probing. Since we probe the codecs asy

[PATCH 4.10 105/129] macsec: dynamically allocate space for sglist

4.10-stable review patch. If anyone has any objections, please let me know. -- From: "Jason A. Donenfeld" [ Upstream commit 5294b83086cc1c35b4efeca03644cf9d12282e5b ] We call skb_cow_data, which is good anyway to ensure we can actually modify the skb as such (another error fr

Re: [PATCH] pinctrl: use non-devm kmalloc versions for free functions

Hi Linus, On 11/05/17 15:01, Linus Walleij wrote: > On Thu, May 4, 2017 at 1:57 AM, Andre Przywara wrote: > >> When a pinctrl driver gets interrupted during its probe process >> (returning -EPROBE_DEFER), the devres system cleans up all allocated >> resources. During this process it calls pinmux

Re: [PATCH 2/3] livepatch/rcu: Warn when system consistency is broken in RCU code

On Thu, May 11, 2017 at 03:52:46PM +0200, Petr Mladek wrote: > Anyway, a crazy idea is to use the livepatch consistency model instead > of RCU to protect the function stack. The model makes sure that all > tasks, including the idle ones, were not running any patched function > (and their ftrace han

[PATCH] block: xen-blkback: add null check to avoid null pointer dereference

Add null check before calling xen_blkif_put() to avoid potential null pointer dereference. Addresses-Coverity-ID: 1350942 Cc: Juergen Gross Signed-off-by: Gustavo A. R. Silva --- drivers/block/xen-blkback/xenbus.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/drive

[PATCH] Partially Revert "of: fix sparse warnings in fdt, irq, reserved mem, and resolver code"

A change to function pointers that was meant to address a sparse warning turned out to cause hundreds of new gcc-7 warnings: include/linux/of_irq.h:11:13: error: type qualifiers ignored on function return type [-Werror=ignored-qualifiers] drivers/of/of_reserved_mem.c: In function '__reserved_mem_

Re: [PATCH] smp_call_function: use inline helpers instead of macros

On 11/05/2017 17:13, Arnd Bergmann wrote: > A new caller of smp_call_function() passes a local variable as the 'wait' > argument, and that variable is otherwise unused, so we get a warning > in non-SMP configurations: > > virt/kvm/kvm_main.c: In function 'kvm_make_all_cpus_request': > virt/kvm/k

Re: [patch 3/3] MM: allow per-cpu vmstat_worker configuration

On Wed, May 10, 2017 at 11:34:26AM -0400, Rik van Riel wrote: > On Wed, 2017-05-03 at 15:40 -0300, Marcelo Tosatti wrote: > > Following the reasoning on the last patch in the series, > > this patch allows configuration of the per-CPU vmstat worker: > > it allows the user to disable the per-CPU vmst

Re: [PATCH] filesystem-dax: fix broken __dax_zero_page_range() conversion

On Wed, May 10, 2017 at 07:49:47PM -0700, Dan Williams wrote: > The conversion of __dax_zero_page_range() to 'struct dax_operations' > caused it to frequently fail. The mistake was treating the @size > parameter as a dax mapping length rather than just a length of the > clear_pmem() operation. The

Re: [PATCH 00/10] fujitsu-laptop: use device-specific data instead of module-wide globals

On Thu, May 11, 2017 at 04:37:30PM +0200, Rafael Wysocki wrote: > On Thursday, May 11, 2017 03:52:11 PM Michał Kępień wrote: > > > On Tuesday, May 09, 2017 09:47:34 AM Darren Hart wrote: > > > > On Tue, May 09, 2017 at 11:35:24AM +0200, Michał Kępień wrote: > > > > > > On Sat, May 06, 2017 at 02:45

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

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(&arm64_const_caps_ready)) > >+return __cpus_have_const_cap(num); > >+else > >+

Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration

On Tue, 2 May 2017, Luiz Capitulino wrote: > Ah, OK. Got this now. I'll give this patch a try. But I think we want > to hear from Christoph (who worked on reducing the vmstat interruptions > in the past). A bit confused by this one. The vmstat worker is already disabled if there are no updates. A

Re: [PATCH] efi: remove duplicate 'const' specifiers

Arnd Bergmann wrote: > gcc-7 shows a harmless warning: > > drivers/firmware/efi/libstub/secureboot.c:19:27: error: duplicate 'const' > declaration specifier [-Werror=duplicate-decl-specifier] > static const efi_char16_t const efi_SecureBoot_name[] = { > drivers/firmware/efi/libstub/secureboot.

[PATCH 4.10 100/129] staging: wlan-ng: add missing byte order conversion

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Igor Pylypiv commit 2c474b8579e9b67ff72b2bcefce9f53c7f4469d4 upstream. Conversion macros le16_to_cpu was removed and that caused new sparse warning sparse output: drivers/staging/wlan-ng/p802

[PATCH 4.10 096/129] MIPS: R2-on-R6 MULTU/MADDU/MSUBU emulation bugfix

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Leonid Yegoshin commit d65e5677ad5b3a49c43f60ec07644dc1f87bbd2e upstream. MIPS instructions MULTU, MADDU and MSUBU emulation requires registers HI/LO to be converted to signed 32bits before 64

[PATCH 4.10 073/129] usb: chipidea: Only read/write OTGSC from one place

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit f60f8ccd54e03c1afafb2b20ceb029a0eaf7a134 upstream. With the id and vbus detection done via extcon we need to make sure we poll the status of OTGSC properly by considering w

[PATCH 4.10 090/129] scsi: qedi: Fix possible memory leak in qedi_iscsi_update_conn()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit 8b9b22ba75907dcced88c815a5427ec0b4298aec upstream. 'conn_info' is malloced in qedi_iscsi_update_conn() and should be freed before leaving from the error handling cases, othe

[PATCH 4.10 095/129] scsi: smartpqi: fix time handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Arnd Bergmann commit ed10858eadd4988260c6bc7d75fc25176342b5a7 upstream. When we have turned off RTC support, the smartpqi driver fails to build: ERROR: "rtc_time64_to_tm" [drivers/scsi/smartp

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

On Thu, May 11, 2017 at 04:37:20PM +0100, 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(&arm64_const_caps_ready)) > > >

[PATCH 4.10 098/129] brcmfmac: Make skb header writable before use

4.10-stable review patch. If anyone has any objections, please let me know. -- From: James Hughes commit 9cc4b7cb86cbcc6330a3faa8cd65268cd2d3c227 upstream. The driver was making changes to the skb_header without ensuring it was writable (i.e. uncloned). This patch also removes

[PATCH 4.10 092/129] scsi: qla2xxx: Fix crash in qla2xxx_eh_abort on bad ptr

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Bill Kuzeja commit 5f7c2beef819d9ea2d1b814edf6f5981420e9cf8 upstream. After a Qlogic card breaks when initializing (test case), the system can crash in qla2xxx_eh_abort if processing anything

[PATCH 4.10 093/129] scsi: mac_scsi: Fix MAC_SCSI=m option when SCSI=m

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Finn Thain commit 2559a1ef688f933835912c731bed2254146a9b04 upstream. The mac_scsi driver still gets disabled when SCSI=m. This should have been fixed back when I enabled the tristate but I did

[PATCH 4.10 081/129] USB: serial: ftdi_sio: fix latency-timer error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit e3e574ad85a208cb179f33720bb5f12b453de33c upstream. Make sure to detect short responses when reading the latency timer to avoid using stale buffer data. Note that no heap d

[PATCH 4.10 094/129] scsi: scsi_dh_emc: return success in clariion_std_inquiry()

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 4d7d39a18b8b81511f0b893b7d2203790bf8a58b upstream. We accidentally return an uninitialized variable on success. Fixes: b6ff1b14cdf4 ("[SCSI] scsi_dh: Update EMC handler")

[PATCH 4.10 082/129] USB: serial: quatech2: fix control-message error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 8c34cb8ddfe808d557b51da983ff10c02793beb2 upstream. Make sure to detect short control-message transfers when fetching modem and line state in open and when retrieving regist

[PATCH 4.10 072/129] usb: host: ohci-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 68bd6fc3cfa98ef253e17307ccafd8ef907b5556 upstream. Returning from for_each_available_child_of_node() loop requires cleaning up node refcount. Error paths lacked it

Re: [PATCH] Partially Revert "of: fix sparse warnings in fdt, irq, reserved mem, and resolver code"

On Thu, May 11, 2017 at 5:30 PM, Rob Herring wrote: > A change to function pointers that was meant to address a sparse warning > turned out to cause hundreds of new gcc-7 warnings: > > include/linux/of_irq.h:11:13: error: type qualifiers ignored on function > return type [-Werror=ignored-qualifie

[PATCH 4.10 089/129] serial: 8250_omap: Fix probe and remove for PM runtime

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Tony Lindgren commit 4e0f5cc65098ea32a1e77baae74215b9bd5276b1 upstream. Otherwise the interconnect related code implementing PM runtime will produce these errors on a failed probe: omap_uart

[PATCH 4.10 085/129] USB: serial: io_edgeport: fix descriptor error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 3c0e25d883d06a1fbd1ad35257e8abaa57befb37 upstream. Make sure to detect short control-message transfers and log an error when reading incomplete manufacturer and boot descri

Re: [RFC PATCH 6/6] drm/i915/gvt: support QEMU getting the dmabuf

On Thu, 11 May 2017 15:27:53 +0200 Gerd Hoffmann wrote: > Hi, > > > While read the framebuffer region we have to tell the vendor driver which > > framebuffer we want to read? There are two framebuffers now in KVMGT that > > is primary and cursor. > > There are two methods to implement this:

[PATCH 4.10 086/129] USB: serial: sierra: fix bogus alternate-setting assumption

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 16620b483eaf7750413bae472f4363b6b959fcaa upstream. Interface numbers do not change when enabling alternate settings as comment and code in this driver suggested. Remove th

[PATCH 4.10 088/129] phy: qcom-usb-hs: Add depends on EXTCON

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Boyd commit 1a09b6a7c10e22c489a8b212dd6862b1fd9674ad upstream. We get the following compile errors if EXTCON is enabled as a module but this driver is builtin: drivers/built-in.o: In

[PATCH 4.10 080/129] USB: serial: ark3116: fix open error handling

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit b631433b175f1002a31020e09bbfc2e5caecf290 upstream. Fix open error handling which failed to detect errors when reading the MSR and LSR registers, something which could lead

[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 reset-resume

[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 del

[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 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 ma

[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 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 dur

[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 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: a

[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 ou

[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 bu

[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 a

[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 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 iwl_mvm_fw

[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. This

[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 er

[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 bug

[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 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 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: 7e62a6

[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. Fi

[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 ap

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

[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. Dat

[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 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 devm_spi_register_mas

[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 recei

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(&arm64_const_caps_ready)) + return __cpus_have_const

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

[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 board-sp

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