[PATCH AUTOSEL 4.4 11/92] mac80211/cfg80211: update bss channel on channel switch

2019-05-22 Thread Sasha Levin
From: Sergey Matyukevich [ Upstream commit 5dc8cdce1d722c733f8c7af14c5fb595cfedbfa8 ] FullMAC STAs have no way to update bss channel after CSA channel switch completion. As a result, user-space tools may provide inconsistent channel info. For instance, consider the following two commands: $ sudo

[PATCH AUTOSEL 4.4 17/92] ssb: Fix possible NULL pointer dereference in ssb_host_pcmcia_exit

2019-05-22 Thread Sasha Levin
From: YueHaibing [ Upstream commit b2c01aab9646ed8ffb7c549afe55d5349c482425 ] Syzkaller report this: kasan: GPF could be caused by NULL-ptr deref or user memory access general protection fault: [#1] SMP KASAN PTI CPU: 0 PID: 4492 Comm: syz-executor.0 Not tainted 5.0.0-rc7+ #45 Hardware nam

[PATCH AUTOSEL 4.4 02/92] cxgb4: Fix error path in cxgb4_init_module

2019-05-22 Thread Sasha Levin
From: YueHaibing [ Upstream commit a3147770bea76c8dbad73eca3a24c2118da5e719 ] BUG: unable to handle kernel paging request at a016a270 PGD 3270067 P4D 3270067 PUD 3271063 PMD 230bbd067 PTE 0 Oops: [#1 CPU: 0 PID: 6134 Comm: modprobe Not tainted 5.1.0+ #33 Hardware name: QEMU Standard

[PATCH AUTOSEL 4.4 16/92] at76c50x-usb: Don't register led_trigger if usb_register_driver failed

2019-05-22 Thread Sasha Levin
From: YueHaibing [ Upstream commit 09ac2694b0475f96be895848687ebcbba97eeecf ] Syzkaller report this: [ 1213.468581] BUG: unable to handle kernel paging request at fbfff83bf338 [ 1213.469530] #PF error: [normal kernel read fault] [ 1213.469530] PGD 237fe4067 P4D 237fe4067 PUD 237e60067 PMD 1

[PATCH AUTOSEL 4.4 29/92] dmaengine: at_xdmac: remove BUG_ON macro in tasklet

2019-05-22 Thread Sasha Levin
From: Nicolas Ferre [ Upstream commit e2c114c06da2d9ffad5b16690abf008d6696f689 ] Even if this case shouldn't happen when controller is properly programmed, it's still better to avoid dumping a kernel Oops for this. As the sequence may happen only for debugging purposes, log the error and just fi

[PATCH AUTOSEL 4.9 041/114] media: ov6650: Move v4l2_clk_get() to ov6650_video_probe() helper

2019-05-22 Thread Sasha Levin
From: Janusz Krzysztofik [ Upstream commit ccdd85d518d8b9320ace1d87271f0ba2175f21fa ] In preparation for adding asynchronous subdevice support to the driver, don't acquire v4l2_clk from the driver .probe() callback as that may fail if the clock is provided by a bridge driver which may be not yet

[PATCH AUTOSEL 4.4 07/92] brcm80211: potential NULL dereference in brcmf_cfg80211_vndr_cmds_dcmd_handler()

2019-05-22 Thread Sasha Levin
From: Dan Carpenter [ Upstream commit e025da3d7aa4770bb1d1b3b0aa7cc4da1744852d ] If "ret_len" is negative then it could lead to a NULL dereference. The "ret_len" value comes from nl80211_vendor_cmd(), if it's negative then we don't allocate the "dcmd_buf" buffer. Then we pass "ret_len" to brcm

[PATCH AUTOSEL 4.4 22/92] RDMA/cma: Consider scope_id while binding to ipv6 ll address

2019-05-22 Thread Sasha Levin
From: Parav Pandit [ Upstream commit 5d7ed2f27bbd482fd29e6b2e204b1a1ee8a0b268 ] When two netdev have same link local addresses (such as vlan and non vlan), two rdma cm listen id should be able to bind to following different addresses. listener-1: addr=lla, scope_id=A, port=X listener-2: addr=ll

[PATCH AUTOSEL 4.4 23/92] x86/build: Move _etext to actual end of .text

2019-05-22 Thread Sasha Levin
From: Kees Cook [ Upstream commit 392bef709659abea614abfe53cf228e7a59876a4 ] When building x86 with Clang LTO and CFI, CFI jump regions are automatically added to the end of the .text section late in linking. As a result, the _etext position was being labelled before the appended jump regions, c

[PATCH AUTOSEL 4.4 28/92] pinctrl: pistachio: fix leaked of_node references

2019-05-22 Thread Sasha Levin
From: Wen Yang [ Upstream commit 44a4455ac2c6b0981eace683a2b6eccf47689022 ] The call to of_get_child_by_name 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/pinctr

[PATCH AUTOSEL 4.4 32/92] media: au0828: stop video streaming only when last user stops

2019-05-22 Thread Sasha Levin
From: Hans Verkuil [ Upstream commit f604f0f5afb88045944567f604409951b5eb6af8 ] If the application was streaming from both videoX and vbiX, and streaming from videoX was stopped, then the vbi streaming also stopped. The cause being that stop_streaming for video stopped the subdevs as well, inst

[PATCH AUTOSEL 4.4 31/92] media: ov6650: Move v4l2_clk_get() to ov6650_video_probe() helper

2019-05-22 Thread Sasha Levin
From: Janusz Krzysztofik [ Upstream commit ccdd85d518d8b9320ace1d87271f0ba2175f21fa ] In preparation for adding asynchronous subdevice support to the driver, don't acquire v4l2_clk from the driver .probe() callback as that may fail if the clock is provided by a bridge driver which may be not yet

[PATCH AUTOSEL 4.4 30/92] media: coda: clear error return value before picture run

2019-05-22 Thread Sasha Levin
From: Philipp Zabel [ Upstream commit bbeefa7357a648afe70e7183914c87c3878d528d ] The error return value is not written by some firmware codecs, such as MPEG-2 decode on CodaHx4. Clear the error return value before starting the picture run to avoid misinterpreting unrelated values returned by seq

[PATCH AUTOSEL 4.4 25/92] x86/mm: Remove in_nmi() warning from 64-bit implementation of vmalloc_fault()

2019-05-22 Thread Sasha Levin
From: Jiri Kosina [ Upstream commit a65c88e16f32aa9ef2e8caa68ea5c29bd5eb0ff0 ] In-NMI warnings have been added to vmalloc_fault() via: ebc8827f75 ("x86: Barf when vmalloc and kmemcheck faults happen in NMI") back in the time when our NMI entry code could not cope with nested NMIs. These day

[PATCH AUTOSEL 4.4 26/92] mm/uaccess: Use 'unsigned long' to placate UBSAN warnings on older GCC versions

2019-05-22 Thread Sasha Levin
From: Peter Zijlstra [ Upstream commit 29da93fea3ea39ab9b12270cc6be1b70ef201c9e ] Randy reported objtool triggered on his (GCC-7.4) build: lib/strncpy_from_user.o: warning: objtool: strncpy_from_user()+0x315: call to __ubsan_handle_add_overflow() with UACCESS enabled lib/strnlen_user.o: wa

[PATCH AUTOSEL 4.4 24/92] smpboot: Place the __percpu annotation correctly

2019-05-22 Thread Sasha Levin
From: Sebastian Andrzej Siewior [ Upstream commit d4645d30b50d1691c26ff0f8fa4e718b08f8d3bb ] The test robot reported a wrong assignment of a per-CPU variable which it detected by using sparse and sent a report. The assignment itself is correct. The annotation for sparse was wrong and hence the r

[PATCH AUTOSEL 4.4 21/92] bcache: avoid clang -Wunintialized warning

2019-05-22 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 78d4eb8ad9e1d413449d1b7a060f50b6efa81ebd ] clang has identified a code path in which it thinks a variable may be unused: drivers/md/bcache/alloc.c:333:4: error: variable 'bucket' is used uninitialized whenever 'if' condition is false [-Werror,-Wsomet

[PATCH AUTOSEL 4.4 20/92] bcache: add failure check to run_cache_set() for journal replay

2019-05-22 Thread Sasha Levin
From: Coly Li [ Upstream commit ce3e4cfb59cb382f8e5ce359238aa580d4ae7778 ] Currently run_cache_set() has no return value, if there is failure in bch_journal_replay(), the caller of run_cache_set() has no idea about such failure and just continue to execute following code after run_cache_set().

[PATCH AUTOSEL 4.4 14/92] mwifiex: prevent an array overflow

2019-05-22 Thread Sasha Levin
From: Dan Carpenter [ Upstream commit b4c35c17227fe437ded17ce683a6927845f8c4a4 ] The "rate_index" is only used as an index into the phist_data->rx_rate[] array in the mwifiex_hist_data_set() function. That array has MWIFIEX_MAX_AC_RX_RATES (74) elements and it's used to generate some debugfs in

[PATCH AUTOSEL 4.4 18/92] bcache: return error immediately in bch_journal_replay()

2019-05-22 Thread Sasha Levin
From: Coly Li [ Upstream commit 68d10e6979a3b59e3cd2e90bfcafed79c4cf180a ] When failure happens inside bch_journal_replay(), calling cache_set_err_on() and handling the failure in async way is not a good idea. Because after bch_journal_replay() returns, registering code will continue to execute

[PATCH AUTOSEL 4.4 19/92] bcache: fix failure in journal relplay

2019-05-22 Thread Sasha Levin
From: Tang Junhui [ Upstream commit 631207314d88e9091be02fbdd1fdadb1ae2ed79a ] journal replay failed with messages: Sep 10 19:10:43 ceph kernel: bcache: error on bb379a64-e44e-4812-b91d-a5599871a3b1: bcache: journal entries 2057493-2057567 missing! (replaying 2057493-2076601), disabling caching

[PATCH AUTOSEL 4.4 27/92] HID: logitech-hidpp: use RAP instead of FAP to get the protocol version

2019-05-22 Thread Sasha Levin
From: Hans de Goede [ Upstream commit 096377525cdb8251e4656085efc988bdf733fb4c ] According to the logitech_hidpp_2.0_specification_draft_2012-06-04.pdf doc: https://lekensteyn.nl/files/logitech/logitech_hidpp_2.0_specification_draft_2012-06-04.pdf We should use a register-access-protocol reques

[PATCH AUTOSEL 4.4 15/92] net: cw1200: fix a NULL pointer dereference

2019-05-22 Thread Sasha Levin
From: Kangjie Lu [ Upstream commit 0ed2a005347400500a39ea7c7318f1fea57fb3ca ] In case create_singlethread_workqueue fails, the fix free the hardware and returns NULL to avoid NULL pointer dereference. Signed-off-by: Kangjie Lu Signed-off-by: Kalle Valo Signed-off-by: Sasha Levin --- drivers

[PATCH AUTOSEL 4.4 06/92] spi: pxa2xx: fix SCR (divisor) calculation

2019-05-22 Thread Sasha Levin
From: Flavio Suligoi [ Upstream commit 29f2133717c527f492933b0622a4aafe0b3cbe9e ] Calculate the divisor for the SCR (Serial Clock Rate), avoiding that the SSP transmission rate can be greater than the device rate. When the division between the SSP clock and the device rate generates a reminder,

[PATCH AUTOSEL 4.4 05/92] ASoC: imx: fix fiq dependencies

2019-05-22 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit ea751227c813ab833609afecfeedaf0aa26f327e ] During randconfig builds, I occasionally run into an invalid configuration of the freescale FIQ sound support: WARNING: unmet direct dependencies detected for SND_SOC_IMX_PCM_FIQ Depends on [m]: SOUND [=y] && !UM

[PATCH AUTOSEL 4.4 08/92] rtc: 88pm860x: prevent use-after-free on device remove

2019-05-22 Thread Sasha Levin
From: Sven Van Asbroeck [ Upstream commit f22b1ba15ee5785aa028384ebf77dd39e8e47b70 ] The device's remove() attempts to shut down the delayed_work scheduled on the kernel-global workqueue by calling flush_scheduled_work(). Unfortunately, flush_scheduled_work() does not prevent the delayed_work f

[PATCH AUTOSEL 4.9 040/114] media: coda: clear error return value before picture run

2019-05-22 Thread Sasha Levin
From: Philipp Zabel [ Upstream commit bbeefa7357a648afe70e7183914c87c3878d528d ] The error return value is not written by some firmware codecs, such as MPEG-2 decode on CodaHx4. Clear the error return value before starting the picture run to avoid misinterpreting unrelated values returned by seq

[PATCH AUTOSEL 4.4 10/92] dmaengine: pl330: _stop: clear interrupt status

2019-05-22 Thread Sasha Levin
From: Sugar Zhang [ Upstream commit 2da254cc7908105a60a6bb219d18e8dced03dcb9 ] This patch kill instructs the DMAC to immediately terminate execution of a thread. and then clear the interrupt status, at last, stop generating interrupts for DMA_SEV. to guarantee the next dma start is clean. otherw

[PATCH AUTOSEL 4.4 04/92] powerpc/boot: Fix missing check of lseek() return value

2019-05-22 Thread Sasha Levin
From: Bo YU [ Upstream commit 5d085ec04a000fefb5182d3b03ee46ca96d8389b ] This is detected by Coverity scan: CID: 1440481 Signed-off-by: Bo YU Signed-off-by: Michael Ellerman Signed-off-by: Sasha Levin --- arch/powerpc/boot/addnote.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)

[PATCH AUTOSEL 4.9 034/114] smpboot: Place the __percpu annotation correctly

2019-05-22 Thread Sasha Levin
From: Sebastian Andrzej Siewior [ Upstream commit d4645d30b50d1691c26ff0f8fa4e718b08f8d3bb ] The test robot reported a wrong assignment of a per-CPU variable which it detected by using sparse and sent a report. The assignment itself is correct. The annotation for sparse was wrong and hence the r

[PATCH AUTOSEL 4.4 09/92] w1: fix the resume command API

2019-05-22 Thread Sasha Levin
From: Mariusz Bialonczyk [ Upstream commit 62909da8aca048ecf9fbd7e484e5100608f40a63 ] >From the DS2408 datasheet [1]: "Resume Command function checks the status of the RC flag and, if it is set, directly transfers control to the control functions, similar to a Skip ROM command. The only way to

[PATCH AUTOSEL 4.4 12/92] driver core: platform: Fix the usage of platform device name(pdev->name)

2019-05-22 Thread Sasha Levin
From: Venkata Narendra Kumar Gutta [ Upstream commit edb16da34b084c66763f29bee42b4e6bb33c3d66 ] Platform core is using pdev->name as the platform device name to do the binding of the devices with the drivers. But, when the platform driver overrides the platform device name with dev_set_name(), t

[PATCH AUTOSEL 4.4 01/92] gfs2: Fix lru_count going negative

2019-05-22 Thread Sasha Levin
From: Ross Lagerwall [ Upstream commit 7881ef3f33bb80f459ea6020d1e021fc524a6348 ] Under certain conditions, lru_count may drop below zero resulting in a large amount of log spam like this: vmscan: shrink_slab: gfs2_dump_glock+0x3b0/0x630 [gfs2] \ negative objects to delete nr=-1 This happe

[PATCH AUTOSEL 4.9 031/114] bcache: avoid clang -Wunintialized warning

2019-05-22 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 78d4eb8ad9e1d413449d1b7a060f50b6efa81ebd ] clang has identified a code path in which it thinks a variable may be unused: drivers/md/bcache/alloc.c:333:4: error: variable 'bucket' is used uninitialized whenever 'if' condition is false [-Werror,-Wsomet

[PATCH AUTOSEL 4.9 037/114] HID: logitech-hidpp: use RAP instead of FAP to get the protocol version

2019-05-22 Thread Sasha Levin
From: Hans de Goede [ Upstream commit 096377525cdb8251e4656085efc988bdf733fb4c ] According to the logitech_hidpp_2.0_specification_draft_2012-06-04.pdf doc: https://lekensteyn.nl/files/logitech/logitech_hidpp_2.0_specification_draft_2012-06-04.pdf We should use a register-access-protocol reques

[PATCH AUTOSEL 4.9 039/114] dmaengine: at_xdmac: remove BUG_ON macro in tasklet

2019-05-22 Thread Sasha Levin
From: Nicolas Ferre [ Upstream commit e2c114c06da2d9ffad5b16690abf008d6696f689 ] Even if this case shouldn't happen when controller is properly programmed, it's still better to avoid dumping a kernel Oops for this. As the sequence may happen only for debugging purposes, log the error and just fi

[PATCH AUTOSEL 4.9 042/114] media: au0828: stop video streaming only when last user stops

2019-05-22 Thread Sasha Levin
From: Hans Verkuil [ Upstream commit f604f0f5afb88045944567f604409951b5eb6af8 ] If the application was streaming from both videoX and vbiX, and streaming from videoX was stopped, then the vbi streaming also stopped. The cause being that stop_streaming for video stopped the subdevs as well, inst

[PATCH AUTOSEL 4.9 036/114] mm/uaccess: Use 'unsigned long' to placate UBSAN warnings on older GCC versions

2019-05-22 Thread Sasha Levin
From: Peter Zijlstra [ Upstream commit 29da93fea3ea39ab9b12270cc6be1b70ef201c9e ] Randy reported objtool triggered on his (GCC-7.4) build: lib/strncpy_from_user.o: warning: objtool: strncpy_from_user()+0x315: call to __ubsan_handle_add_overflow() with UACCESS enabled lib/strnlen_user.o: wa

[PATCH AUTOSEL 4.9 038/114] pinctrl: pistachio: fix leaked of_node references

2019-05-22 Thread Sasha Levin
From: Wen Yang [ Upstream commit 44a4455ac2c6b0981eace683a2b6eccf47689022 ] The call to of_get_child_by_name 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/pinctr

[PATCH AUTOSEL 4.9 033/114] x86/build: Move _etext to actual end of .text

2019-05-22 Thread Sasha Levin
From: Kees Cook [ Upstream commit 392bef709659abea614abfe53cf228e7a59876a4 ] When building x86 with Clang LTO and CFI, CFI jump regions are automatically added to the end of the .text section late in linking. As a result, the _etext position was being labelled before the appended jump regions, c

[PATCH AUTOSEL 4.9 032/114] RDMA/cma: Consider scope_id while binding to ipv6 ll address

2019-05-22 Thread Sasha Levin
From: Parav Pandit [ Upstream commit 5d7ed2f27bbd482fd29e6b2e204b1a1ee8a0b268 ] When two netdev have same link local addresses (such as vlan and non vlan), two rdma cm listen id should be able to bind to following different addresses. listener-1: addr=lla, scope_id=A, port=X listener-2: addr=ll

[PATCH AUTOSEL 4.9 026/114] ssb: Fix possible NULL pointer dereference in ssb_host_pcmcia_exit

2019-05-22 Thread Sasha Levin
From: YueHaibing [ Upstream commit b2c01aab9646ed8ffb7c549afe55d5349c482425 ] Syzkaller report this: kasan: GPF could be caused by NULL-ptr deref or user memory access general protection fault: [#1] SMP KASAN PTI CPU: 0 PID: 4492 Comm: syz-executor.0 Not tainted 5.0.0-rc7+ #45 Hardware nam

[PATCH AUTOSEL 4.9 028/114] bcache: return error immediately in bch_journal_replay()

2019-05-22 Thread Sasha Levin
From: Coly Li [ Upstream commit 68d10e6979a3b59e3cd2e90bfcafed79c4cf180a ] When failure happens inside bch_journal_replay(), calling cache_set_err_on() and handling the failure in async way is not a good idea. Because after bch_journal_replay() returns, registering code will continue to execute

[PATCH AUTOSEL 4.9 025/114] at76c50x-usb: Don't register led_trigger if usb_register_driver failed

2019-05-22 Thread Sasha Levin
From: YueHaibing [ Upstream commit 09ac2694b0475f96be895848687ebcbba97eeecf ] Syzkaller report this: [ 1213.468581] BUG: unable to handle kernel paging request at fbfff83bf338 [ 1213.469530] #PF error: [normal kernel read fault] [ 1213.469530] PGD 237fe4067 P4D 237fe4067 PUD 237e60067 PMD 1

[PATCH AUTOSEL 4.9 024/114] net: cw1200: fix a NULL pointer dereference

2019-05-22 Thread Sasha Levin
From: Kangjie Lu [ Upstream commit 0ed2a005347400500a39ea7c7318f1fea57fb3ca ] In case create_singlethread_workqueue fails, the fix free the hardware and returns NULL to avoid NULL pointer dereference. Signed-off-by: Kangjie Lu Signed-off-by: Kalle Valo Signed-off-by: Sasha Levin --- drivers

[PATCH AUTOSEL 4.9 023/114] mwifiex: prevent an array overflow

2019-05-22 Thread Sasha Levin
From: Dan Carpenter [ Upstream commit b4c35c17227fe437ded17ce683a6927845f8c4a4 ] The "rate_index" is only used as an index into the phist_data->rx_rate[] array in the mwifiex_hist_data_set() function. That array has MWIFIEX_MAX_AC_RX_RATES (74) elements and it's used to generate some debugfs in

[PATCH AUTOSEL 4.9 019/114] dmaengine: pl330: _stop: clear interrupt status

2019-05-22 Thread Sasha Levin
From: Sugar Zhang [ Upstream commit 2da254cc7908105a60a6bb219d18e8dced03dcb9 ] This patch kill instructs the DMAC to immediately terminate execution of a thread. and then clear the interrupt status, at last, stop generating interrupts for DMA_SEV. to guarantee the next dma start is clean. otherw

[PATCH AUTOSEL 4.9 016/114] iwlwifi: pcie: don't crash on invalid RX interrupt

2019-05-22 Thread Sasha Levin
From: Johannes Berg [ Upstream commit 30f24eabab8cd801064c5c37589d803cb4341929 ] If for some reason the device gives us an RX interrupt before we're ready for it, perhaps during device power-on with misconfigured IRQ causes mapping or so, we can crash trying to access the queues. Prevent that b

[PATCH AUTOSEL 4.9 018/114] w1: fix the resume command API

2019-05-22 Thread Sasha Levin
From: Mariusz Bialonczyk [ Upstream commit 62909da8aca048ecf9fbd7e484e5100608f40a63 ] >From the DS2408 datasheet [1]: "Resume Command function checks the status of the RC flag and, if it is set, directly transfers control to the control functions, similar to a Skip ROM command. The only way to

[PATCH AUTOSEL 4.9 015/114] scsi: qla2xxx: Fix a qla24xx_enable_msix() error path

2019-05-22 Thread Sasha Levin
From: Bart Van Assche [ Upstream commit 24afabdbd0b3553963a2bbf465895492b14d1107 ] Make sure that the allocated interrupts are freed if allocating memory for the msix_entries array fails. Cc: Himanshu Madhani Cc: Giridhar Malavali Signed-off-by: Bart Van Assche Acked-by: Himanshu Madhani Si

[PATCH AUTOSEL 4.9 010/114] spi: pxa2xx: fix SCR (divisor) calculation

2019-05-22 Thread Sasha Levin
From: Flavio Suligoi [ Upstream commit 29f2133717c527f492933b0622a4aafe0b3cbe9e ] Calculate the divisor for the SCR (Serial Clock Rate), avoiding that the SSP transmission rate can be greater than the device rate. When the division between the SSP clock and the device rate generates a reminder,

Re: [PATCH 0/2] public key: IMA signer logging: Log public key of IMA Signature signer in IMA log

2019-05-22 Thread Lakshmi
On 5/22/19 11:57 AM, Ken Goldman wrote: 1 - How is your solution - including a public key with each event - related to this issue? This a change from my earlier proposal. In the new proposal I am making the public key is not included with each event. The data included in each IMA event does

[PATCH AUTOSEL 4.9 001/114] gfs2: Fix lru_count going negative

2019-05-22 Thread Sasha Levin
From: Ross Lagerwall [ Upstream commit 7881ef3f33bb80f459ea6020d1e021fc524a6348 ] Under certain conditions, lru_count may drop below zero resulting in a large amount of log spam like this: vmscan: shrink_slab: gfs2_dump_glock+0x3b0/0x630 [gfs2] \ negative objects to delete nr=-1 This happe

Re: [PATCH v4 0/6] LM36274 Introduction

2019-05-22 Thread Jacek Anaszewski
Hi Dan, On 5/22/19 9:27 PM, Dan Murphy wrote: Hello This is patch set v4 for the LM36274. There were no changes made to this patch set except to rebase this on top of the latest TI LMU common code patchset. Why the rebase was needed? leds-lm36274.c was already including leds-ti-lmu-common.h.

[PATCH AUTOSEL 4.9 011/114] brcm80211: potential NULL dereference in brcmf_cfg80211_vndr_cmds_dcmd_handler()

2019-05-22 Thread Sasha Levin
From: Dan Carpenter [ Upstream commit e025da3d7aa4770bb1d1b3b0aa7cc4da1744852d ] If "ret_len" is negative then it could lead to a NULL dereference. The "ret_len" value comes from nl80211_vendor_cmd(), if it's negative then we don't allocate the "dcmd_buf" buffer. Then we pass "ret_len" to brcm

[PATCH AUTOSEL 4.9 005/114] net: ena: gcc 8: fix compilation warning

2019-05-22 Thread Sasha Levin
From: Sameeh Jubran [ Upstream commit f913308879bc6ae437ce64d878c7b05643ddea44 ] GCC 8 contains a number of new warnings as well as enhancements to existing checkers. The warning - Wstringop-truncation - warns for calls to bounded string manipulation functions such as strncat, strncpy, and stpnc

[PATCH AUTOSEL 4.9 013/114] arm64: Fix compiler warning from pte_unmap() with -Wunused-but-set-variable

2019-05-22 Thread Sasha Levin
From: Qian Cai [ Upstream commit 74dd022f9e6260c3b5b8d15901d27ebcc5f21eda ] When building with -Wunused-but-set-variable, the compiler shouts about a number of pte_unmap() users, since this expands to an empty macro on arm64: | mm/gup.c: In function 'gup_pte_range': | mm/gup.c:1727:16: warn

[PATCH AUTOSEL 4.9 008/114] powerpc/boot: Fix missing check of lseek() return value

2019-05-22 Thread Sasha Levin
From: Bo YU [ Upstream commit 5d085ec04a000fefb5182d3b03ee46ca96d8389b ] This is detected by Coverity scan: CID: 1440481 Signed-off-by: Bo YU Signed-off-by: Michael Ellerman Signed-off-by: Sasha Levin --- arch/powerpc/boot/addnote.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)

[PATCH AUTOSEL 4.9 006/114] orangefs: truncate before updating size

2019-05-22 Thread Sasha Levin
From: Martin Brandenburg [ Upstream commit 33713cd09ccdc1e01b10d0782ae60200d4989553 ] Otherwise we race with orangefs_writepage/orangefs_writepages which and does not expect i_size < page_offset. Fixes xfstests generic/129. Signed-off-by: Martin Brandenburg Signed-off-by: Mike Marshall Signe

[PATCH AUTOSEL 4.9 004/114] dmaengine: tegra210-dma: free dma controller in remove()

2019-05-22 Thread Sasha Levin
From: Sameer Pujar [ Upstream commit f030e419501cb95e961e9ed35c493b5d46a04eca ] Following kernel panic is seen during DMA driver unload->load sequence == Unable to handle kernel paging request at virtual address ff800119

[PATCH AUTOSEL 4.14 061/167] media: au0828: stop video streaming only when last user stops

2019-05-22 Thread Sasha Levin
From: Hans Verkuil [ Upstream commit f604f0f5afb88045944567f604409951b5eb6af8 ] If the application was streaming from both videoX and vbiX, and streaming from videoX was stopped, then the vbi streaming also stopped. The cause being that stop_streaming for video stopped the subdevs as well, inst

[PATCH AUTOSEL 4.14 058/167] dmaengine: at_xdmac: remove BUG_ON macro in tasklet

2019-05-22 Thread Sasha Levin
From: Nicolas Ferre [ Upstream commit e2c114c06da2d9ffad5b16690abf008d6696f689 ] Even if this case shouldn't happen when controller is properly programmed, it's still better to avoid dumping a kernel Oops for this. As the sequence may happen only for debugging purposes, log the error and just fi

[PATCH AUTOSEL 4.14 054/167] HID: logitech-hidpp: use RAP instead of FAP to get the protocol version

2019-05-22 Thread Sasha Levin
From: Hans de Goede [ Upstream commit 096377525cdb8251e4656085efc988bdf733fb4c ] According to the logitech_hidpp_2.0_specification_draft_2012-06-04.pdf doc: https://lekensteyn.nl/files/logitech/logitech_hidpp_2.0_specification_draft_2012-06-04.pdf We should use a register-access-protocol reques

[PATCH AUTOSEL 4.14 056/167] pinctrl: samsung: fix leaked of_node references

2019-05-22 Thread Sasha Levin
From: Wen Yang [ Upstream commit 44b9f86cd41db6c522effa5aec251d664a52fbc0 ] The call to of_find_compatible_node 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/sam

[PATCH AUTOSEL 4.14 047/167] RDMA/cma: Consider scope_id while binding to ipv6 ll address

2019-05-22 Thread Sasha Levin
From: Parav Pandit [ Upstream commit 5d7ed2f27bbd482fd29e6b2e204b1a1ee8a0b268 ] When two netdev have same link local addresses (such as vlan and non vlan), two rdma cm listen id should be able to bind to following different addresses. listener-1: addr=lla, scope_id=A, port=X listener-2: addr=ll

[PATCH AUTOSEL 4.14 049/167] vfio-ccw: Release any channel program when releasing/removing vfio-ccw mdev

2019-05-22 Thread Sasha Levin
From: Farhan Ali [ Upstream commit b49bdc8602b7c9c7a977758bee4125683f73e59f ] When releasing the vfio-ccw mdev, we currently do not release any existing channel program and its pinned pages. This can lead to the following warning: [1038876.561565] WARNING: CPU: 2 PID: 144727 at drivers/vfio/vf

Use logo on USB drive

2019-05-22 Thread David
Hi, Not sure if you received my last email? Are you interested in purchasing your LOGO promotional and marketing products for your company? We produce USB Drives with your Logo Printed or artwork printed to be used for gifts or marketing. Here is more info from our website: We can pre-load your

[PATCH AUTOSEL 4.14 046/167] bcache: avoid clang -Wunintialized warning

2019-05-22 Thread Sasha Levin
From: Arnd Bergmann [ Upstream commit 78d4eb8ad9e1d413449d1b7a060f50b6efa81ebd ] clang has identified a code path in which it thinks a variable may be unused: drivers/md/bcache/alloc.c:333:4: error: variable 'bucket' is used uninitialized whenever 'if' condition is false [-Werror,-Wsomet

[PATCH AUTOSEL 4.14 043/167] bcache: return error immediately in bch_journal_replay()

2019-05-22 Thread Sasha Levin
From: Coly Li [ Upstream commit 68d10e6979a3b59e3cd2e90bfcafed79c4cf180a ] When failure happens inside bch_journal_replay(), calling cache_set_err_on() and handling the failure in async way is not a good idea. Because after bch_journal_replay() returns, registering code will continue to execute

[PATCH AUTOSEL 4.14 041/167] ssb: Fix possible NULL pointer dereference in ssb_host_pcmcia_exit

2019-05-22 Thread Sasha Levin
From: YueHaibing [ Upstream commit b2c01aab9646ed8ffb7c549afe55d5349c482425 ] Syzkaller report this: kasan: GPF could be caused by NULL-ptr deref or user memory access general protection fault: [#1] SMP KASAN PTI CPU: 0 PID: 4492 Comm: syz-executor.0 Not tainted 5.0.0-rc7+ #45 Hardware nam

Re: [PATCH AUTOSEL 4.19 077/244] mlxsw: spectrum_router: Prevent ipv6 gateway with v4 route via replace and append

2019-05-22 Thread David Ahern
On 5/22/19 1:23 PM, Sasha Levin wrote: > From: David Ahern > > [ Upstream commit 7973d9e76727aa42f0824f5569e96248a572d50b ] > > mlxsw currently does not support v6 gateways with v4 routes. Commit > 19a9d136f198 ("ipv4: Flag fib_info with a fib_nh using IPv6 gateway") > prevents a route from bein

Re: [PATCH v4 0/6] LM36274 Introduction

2019-05-22 Thread Dan Murphy
Jacek On 5/22/19 2:37 PM, Jacek Anaszewski wrote: > Hi Dan, > > On 5/22/19 9:27 PM, Dan Murphy wrote: >> Hello >> >> This is patch set v4 for the LM36274.  There were no changes made >> to this patch set except to rebase this on top of the latest TI LMU common >> code >> patchset. > > Why the r

[PATCH AUTOSEL 4.14 035/167] libbpf: fix samples/bpf build failure due to undefined UINT32_MAX

2019-05-22 Thread Sasha Levin
From: "Daniel T. Lee" [ Upstream commit 32e621e55496a0009f44fe4914cd4a23cade4984 ] Currently, building bpf samples will cause the following error. ./tools/lib/bpf/bpf.h:132:27: error: 'UINT32_MAX' undeclared here (not in a function) .. #define BPF_LOG_BUF_SIZE (UINT32_MAX >> 8) /* ver

[PATCH AUTOSEL 4.14 036/167] driver core: platform: Fix the usage of platform device name(pdev->name)

2019-05-22 Thread Sasha Levin
From: Venkata Narendra Kumar Gutta [ Upstream commit edb16da34b084c66763f29bee42b4e6bb33c3d66 ] Platform core is using pdev->name as the platform device name to do the binding of the devices with the drivers. But, when the platform driver overrides the platform device name with dev_set_name(), t

[PATCH AUTOSEL 4.14 039/167] net: cw1200: fix a NULL pointer dereference

2019-05-22 Thread Sasha Levin
From: Kangjie Lu [ Upstream commit 0ed2a005347400500a39ea7c7318f1fea57fb3ca ] In case create_singlethread_workqueue fails, the fix free the hardware and returns NULL to avoid NULL pointer dereference. Signed-off-by: Kangjie Lu Signed-off-by: Kalle Valo Signed-off-by: Sasha Levin --- drivers

[PATCH AUTOSEL 4.14 032/167] w1: fix the resume command API

2019-05-22 Thread Sasha Levin
From: Mariusz Bialonczyk [ Upstream commit 62909da8aca048ecf9fbd7e484e5100608f40a63 ] >From the DS2408 datasheet [1]: "Resume Command function checks the status of the RC flag and, if it is set, directly transfers control to the control functions, similar to a Skip ROM command. The only way to

[PATCH AUTOSEL 4.14 037/167] ASoC: fsl_sai: Update is_slave_mode with correct value

2019-05-22 Thread Sasha Levin
From: Daniel Baluta [ Upstream commit ddb351145a967ee791a0fb0156852ec2fcb746ba ] is_slave_mode defaults to false because sai structure that contains it is kzalloc'ed. Anyhow, if we decide to set the following configuration SAI slave -> SAI master, is_slave_mode will remain set on true although

[PATCH AUTOSEL 4.14 031/167] scsi: qedi: Abort ep termination if offload not scheduled

2019-05-22 Thread Sasha Levin
From: Manish Rangankar [ Upstream commit f848bfd8e167210a29374e8a678892bed591684f ] Sometimes during connection recovery when there is a failure to resolve ARP, and offload connection was not issued, driver tries to flush pending offload connection work which was not queued up. kernel: WARNING:

[PATCH AUTOSEL 4.14 030/167] rtc: 88pm860x: prevent use-after-free on device remove

2019-05-22 Thread Sasha Levin
From: Sven Van Asbroeck [ Upstream commit f22b1ba15ee5785aa028384ebf77dd39e8e47b70 ] The device's remove() attempts to shut down the delayed_work scheduled on the kernel-global workqueue by calling flush_scheduled_work(). Unfortunately, flush_scheduled_work() does not prevent the delayed_work f

[PATCH AUTOSEL 4.14 029/167] iwlwifi: pcie: don't crash on invalid RX interrupt

2019-05-22 Thread Sasha Levin
From: Johannes Berg [ Upstream commit 30f24eabab8cd801064c5c37589d803cb4341929 ] If for some reason the device gives us an RX interrupt before we're ready for it, perhaps during device power-on with misconfigured IRQ causes mapping or so, we can crash trying to access the queues. Prevent that b

[PATCH AUTOSEL 4.14 027/167] btrfs: fix panic during relocation after ENOSPC before writeback happens

2019-05-22 Thread Sasha Levin
From: Josef Bacik [ Upstream commit ff612ba7849964b1898fd3ccd1f56941129c6aab ] We've been seeing the following sporadically throughout our fleet panic: kernel BUG at fs/btrfs/relocation.c:4584! netversion: 5.0-0 Backtrace: #0 [c90003adb880] machine_kexec at 81041da8 #1 [c90003

[PATCH AUTOSEL 4.14 023/167] scsi: qla2xxx: Fix a qla24xx_enable_msix() error path

2019-05-22 Thread Sasha Levin
From: Bart Van Assche [ Upstream commit 24afabdbd0b3553963a2bbf465895492b14d1107 ] Make sure that the allocated interrupts are freed if allocating memory for the msix_entries array fails. Cc: Himanshu Madhani Cc: Giridhar Malavali Signed-off-by: Bart Van Assche Acked-by: Himanshu Madhani Si

[PATCH AUTOSEL 4.14 022/167] sched/cpufreq: Fix kobject memleak

2019-05-22 Thread Sasha Levin
From: Viresh Kumar [ 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 kobject_

[PATCH AUTOSEL 4.14 019/167] ACPI / property: fix handling of data_nodes in acpi_get_next_subnode()

2019-05-22 Thread Sasha Levin
From: Pierre-Louis Bossart [ Upstream commit 23583f7795025e3c783b680d906509366b0906ad ] When the DSDT tables expose devices with subdevices and a set of hierarchical _DSD properties, the data returned by acpi_get_next_subnode() is incorrect, with the results suggesting a bad pointer assignment.

[PATCH AUTOSEL 4.14 012/167] ASoC: hdmi-codec: unlock the device on startup errors

2019-05-22 Thread Sasha Levin
From: Jerome Brunet [ Upstream commit 30180e8436046344b12813dc954b2e01dfdcd22d ] If the hdmi codec startup fails, it should clear the current_substream pointer to free the device. This is properly done for the audio_startup() callback but for snd_pcm_hw_constraint_eld(). Make sure the pointer c

[PATCH AUTOSEL 4.14 018/167] brcm80211: potential NULL dereference in brcmf_cfg80211_vndr_cmds_dcmd_handler()

2019-05-22 Thread Sasha Levin
From: Dan Carpenter [ Upstream commit e025da3d7aa4770bb1d1b3b0aa7cc4da1744852d ] If "ret_len" is negative then it could lead to a NULL dereference. The "ret_len" value comes from nl80211_vendor_cmd(), if it's negative then we don't allocate the "dcmd_buf" buffer. Then we pass "ret_len" to brcm

[PATCH AUTOSEL 4.14 014/167] powerpc/perf: Return accordingly on invalid chip-id in

2019-05-22 Thread Sasha Levin
From: Anju T Sudhakar [ Upstream commit a913e5e8b43be1d3897a141ce61c1ec071cad89c ] Nest hardware counter memory resides in a per-chip reserve-memory. During nest_imc_event_init(), chip-id of the event-cpu is considered to calculate the base memory addresss for that cpu. Return, proper error cond

[PATCH AUTOSEL 4.14 015/167] powerpc/boot: Fix missing check of lseek() return value

2019-05-22 Thread Sasha Levin
From: Bo YU [ Upstream commit 5d085ec04a000fefb5182d3b03ee46ca96d8389b ] This is detected by Coverity scan: CID: 1440481 Signed-off-by: Bo YU Signed-off-by: Michael Ellerman Signed-off-by: Sasha Levin --- arch/powerpc/boot/addnote.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-)

[PATCH AUTOSEL 4.14 011/167] pinctrl: zte: fix leaked of_node references

2019-05-22 Thread Sasha Levin
From: Wen Yang [ Upstream commit 02d15f0d80720545f1f4922a1550ea4aaad4e152 ] 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/zte/pinctr

[PATCH AUTOSEL 4.14 013/167] leds: avoid races with workqueue

2019-05-22 Thread Sasha Levin
From: Pavel Machek [ Upstream commit 0db37915d912e8dc6588f25da76d3ed36718d92f ] There are races between "main" thread and workqueue. They manifest themselves on Thinkpad X60: This should result in LED blinking, but it turns it off instead: root@amd:/data/pavel# cd /sys/class/leds/tpacpi\:\

[PATCH AUTOSEL 4.14 008/167] dmaengine: tegra210-dma: free dma controller in remove()

2019-05-22 Thread Sasha Levin
From: Sameer Pujar [ Upstream commit f030e419501cb95e961e9ed35c493b5d46a04eca ] Following kernel panic is seen during DMA driver unload->load sequence == Unable to handle kernel paging request at virtual address ff800119

[PATCH AUTOSEL 4.14 003/167] NFS: make nfs_match_client killable

2019-05-22 Thread Sasha Levin
From: Roberto Bergantinos Corpas [ Upstream commit 950a578c6128c2886e295b9c7ecb0b6b22fcc92b ] Actually we don't do anything with return value from nfs_wait_client_init_complete in nfs_match_client, as a consequence if we get a fatal signal and client is not fully initialised, we'

[PATCH AUTOSEL 4.14 004/167] IB/hfi1: Fix WQ_MEM_RECLAIM warning

2019-05-22 Thread Sasha Levin
From: Mike Marciniszyn [ Upstream commit 4c4b1996b5db688e2dcb8242b0a3bf7b1e845e42 ] The work_item cancels that occur when a QP is destroyed can elicit the following trace: workqueue: WQ_MEM_RECLAIM ipoib_wq:ipoib_cm_tx_reap [ib_ipoib] is flushing !WQ_MEM_RECLAIM hfi0_0:_hfi1_do_send [hfi1] W

[PATCH AUTOSEL 4.14 006/167] mmc: core: Verify SD bus width

2019-05-22 Thread Sasha Levin
From: Raul E Rangel [ Upstream commit 9e4be8d03f50d1b25c38e2b59e73b194c130df7d ] The SD Physical Layer Spec says the following: Since the SD Memory Card shall support at least the two bus modes 1-bit or 4-bit width, then any SD Card shall set at least bits 0 and 2 (SD_BUS_WIDTH="0101"). This ch

Re: [PATCH v6 0/6] Allwinner H6 Mali GPU support

2019-05-22 Thread Clément Péron
Hi Rob, On Wed, 22 May 2019 at 21:27, Rob Herring wrote: > > On Tue, May 21, 2019 at 11:11 AM Clément Péron wrote: > > > > Hi, > > > > The Allwinner H6 has a Mali-T720 MP2 which should be supported by > > the new panfrost driver. This series fix two issues and introduce the > > dt-bindings but a

[PATCH AUTOSEL 4.19 081/244] pinctrl: pistachio: fix leaked of_node references

2019-05-22 Thread Sasha Levin
From: Wen Yang [ Upstream commit 44a4455ac2c6b0981eace683a2b6eccf47689022 ] The call to of_get_child_by_name 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/pinctr

[PATCH AUTOSEL 4.19 076/244] x86/mm: Remove in_nmi() warning from 64-bit implementation of vmalloc_fault()

2019-05-22 Thread Sasha Levin
From: Jiri Kosina [ Upstream commit a65c88e16f32aa9ef2e8caa68ea5c29bd5eb0ff0 ] In-NMI warnings have been added to vmalloc_fault() via: ebc8827f75 ("x86: Barf when vmalloc and kmemcheck faults happen in NMI") back in the time when our NMI entry code could not cope with nested NMIs. These day

[PATCH AUTOSEL 4.14 005/167] gfs2: Fix occasional glock use-after-free

2019-05-22 Thread Sasha Levin
From: Andreas Gruenbacher [ Upstream commit 9287c6452d2b1f24ea8e84bd3cf6f3c6f267f712 ] This patch has to do with the life cycle of glocks and buffers. When gfs2 metadata or journaled data is queued to be written, a gfs2_bufdata object is assigned to track the buffer, and that is queued to vario

[PATCH AUTOSEL 4.14 002/167] cxgb4: Fix error path in cxgb4_init_module

2019-05-22 Thread Sasha Levin
From: YueHaibing [ Upstream commit a3147770bea76c8dbad73eca3a24c2118da5e719 ] BUG: unable to handle kernel paging request at a016a270 PGD 3270067 P4D 3270067 PUD 3271063 PMD 230bbd067 PTE 0 Oops: [#1 CPU: 0 PID: 6134 Comm: modprobe Not tainted 5.1.0+ #33 Hardware name: QEMU Standard

[PATCH AUTOSEL 4.19 083/244] clk: rockchip: undo several noc and special clocks as critical on rk3288

2019-05-22 Thread Sasha Levin
From: Douglas Anderson [ Upstream commit f4033db5b84ebe4b32c25ba2ed65ab20b628996a ] This is mostly a revert of commit 55bb6a633c33 ("clk: rockchip: mark noc and some special clk as critical on rk3288") except that we're keeping "pmu_hclk_otg0" as critical still. NOTE: turning these clocks off d

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