[PATCH AUTOSEL 4.14 09/87] serial: sh-sci: Stop RX FIFO timer during port shutdown

2018-09-16 Thread Sasha Levin
From: Geert Uytterhoeven [ Upstream commit c5a9262fa8bfed0dddc7466ef10fcd292e2af61b ] The RX FIFO timer may be armed when the port is shut down, hence the timer function may still be called afterwards. Fix this race condition by deleting the timer during port shutdown. Fixes: 039403765e5da3c6

[PATCH AUTOSEL 4.14 26/87] powerpc/kdump: Handle crashkernel memory reservation failure

2018-09-16 Thread Sasha Levin
From: Hari Bathini [ Upstream commit 8950329c4a64c6d3ca0bc34711a1afbd9ce05657 ] Memory reservation for crashkernel could fail if there are holes around kdump kernel offset (128M). Fail gracefully in such cases and print an error message. Signed-off-by: Hari Bathini Tested-by: David Gibson

[PATCH AUTOSEL 4.14 04/87] vmci: type promotion bug in qp_host_get_user_memory()

2018-09-16 Thread Sasha Levin
From: Dan Carpenter [ Upstream commit 7fb2fd4e25fc1fb10dcb30b5519de257cfeae84c ] The problem is that if get_user_pages_fast() fails and returns a negative error code, it gets type promoted to a high positive value and treated as a success. Fixes: 06164d2b72aa ("VMCI: queue pairs

[PATCH AUTOSEL 4.18 124/136] staging: pi433: fix race condition in pi433_ioctl

2018-09-16 Thread Sasha Levin
From: Hugo Lefeuvre [ Upstream commit 6de4ef65a8c6f53ce7eef0410bc3b6e4b624 ] In the PI433_IOC_WR_TX_CFG case in pi433_ioctl, instance->tx_cfg is modified via copy_from_user(>tx_cfg, argp, sizeof(struct pi433_tx_cfg))) without any kind of synchronization. In the case where two threads

[PATCH AUTOSEL 4.18 121/136] nfsd: fix corrupted reply to badly ordered compound

2018-09-16 Thread Sasha Levin
From: "J. Bruce Fields" [ Upstream commit 5b7b15aee641904ae269be9846610a3950cbd64c ] We're encoding a single op in the reply but leaving the number of ops zero, so the reply makes no sense. Somewhat academic as this isn't a case any real client will hit, though in theory perhaps that could

[PATCH AUTOSEL 4.14 04/87] vmci: type promotion bug in qp_host_get_user_memory()

2018-09-16 Thread Sasha Levin
From: Dan Carpenter [ Upstream commit 7fb2fd4e25fc1fb10dcb30b5519de257cfeae84c ] The problem is that if get_user_pages_fast() fails and returns a negative error code, it gets type promoted to a high positive value and treated as a success. Fixes: 06164d2b72aa ("VMCI: queue pairs

[PATCH AUTOSEL 4.18 124/136] staging: pi433: fix race condition in pi433_ioctl

2018-09-16 Thread Sasha Levin
From: Hugo Lefeuvre [ Upstream commit 6de4ef65a8c6f53ce7eef0410bc3b6e4b624 ] In the PI433_IOC_WR_TX_CFG case in pi433_ioctl, instance->tx_cfg is modified via copy_from_user(>tx_cfg, argp, sizeof(struct pi433_tx_cfg))) without any kind of synchronization. In the case where two threads

[PATCH AUTOSEL 4.18 121/136] nfsd: fix corrupted reply to badly ordered compound

2018-09-16 Thread Sasha Levin
From: "J. Bruce Fields" [ Upstream commit 5b7b15aee641904ae269be9846610a3950cbd64c ] We're encoding a single op in the reply but leaving the number of ops zero, so the reply makes no sense. Somewhat academic as this isn't a case any real client will hit, though in theory perhaps that could

[PATCH AUTOSEL 4.18 119/136] module: exclude SHN_UNDEF symbols from kallsyms api

2018-09-16 Thread Sasha Levin
From: Jessica Yu [ Upstream commit 9f2d1e68cf4d641def734adaccfc3823d3575e6c ] Livepatch modules are special in that we preserve their entire symbol tables in order to be able to apply relocations after module load. The unwanted side effect of this is that undefined (SHN_UNDEF) symbols of

[PATCH AUTOSEL 4.18 119/136] module: exclude SHN_UNDEF symbols from kallsyms api

2018-09-16 Thread Sasha Levin
From: Jessica Yu [ Upstream commit 9f2d1e68cf4d641def734adaccfc3823d3575e6c ] Livepatch modules are special in that we preserve their entire symbol tables in order to be able to apply relocations after module load. The unwanted side effect of this is that undefined (SHN_UNDEF) symbols of

[PATCH AUTOSEL 4.18 118/136] ASoC: dapm: Fix potential DAI widget pointer deref when linking DAIs

2018-09-16 Thread Sasha Levin
From: Liam Girdwood [ Upstream commit e01b4f624278d5efe5fb5da585ca371947b16680 ] Sometime a component or topology may configure a DAI widget with no private data leading to a dev_dbg() dereferencne of this data. Fix this to check for non NULL private data and let users know if widget is

[PATCH AUTOSEL 4.18 114/136] ASoC: Intel: bytcr_rt5640: Fix Acer Iconia 8 over-current detect threshold

2018-09-16 Thread Sasha Levin
From: Hans de Goede [ Upstream commit f12a0a3c4cc6f594d7c2ea361f2396ae5c518d2c ] Change the over-current detect threshold on the Acer Iconia 8 from 2000ua to 1500uA, this fixes headset button presses not being detected. Signed-off-by: Hans de Goede Acked-by: Pierre-Louis Bossart

[PATCH AUTOSEL 4.18 118/136] ASoC: dapm: Fix potential DAI widget pointer deref when linking DAIs

2018-09-16 Thread Sasha Levin
From: Liam Girdwood [ Upstream commit e01b4f624278d5efe5fb5da585ca371947b16680 ] Sometime a component or topology may configure a DAI widget with no private data leading to a dev_dbg() dereferencne of this data. Fix this to check for non NULL private data and let users know if widget is

[PATCH AUTOSEL 4.18 114/136] ASoC: Intel: bytcr_rt5640: Fix Acer Iconia 8 over-current detect threshold

2018-09-16 Thread Sasha Levin
From: Hans de Goede [ Upstream commit f12a0a3c4cc6f594d7c2ea361f2396ae5c518d2c ] Change the over-current detect threshold on the Acer Iconia 8 from 2000ua to 1500uA, this fixes headset button presses not being detected. Signed-off-by: Hans de Goede Acked-by: Pierre-Louis Bossart

[PATCH AUTOSEL 4.18 120/136] gpio: Fix wrong rounding in gpio-menz127

2018-09-16 Thread Sasha Levin
From: Nadav Amit [ Upstream commit 7279d9917560bbd0d82813d6bf00490a82c06783 ] men_z127_debounce() tries to round up and down, but uses functions which are only suitable when the divider is a power of two, which is not the case. Use the appropriate ones. Found by static check. Compile tested.

[PATCH AUTOSEL 4.18 117/136] EDAC, i7core: Fix memleaks and use-after-free on probe and remove

2018-09-16 Thread Sasha Levin
From: Johan Hovold [ Upstream commit 6c974d4dfafe5e9ee754f2a6fba0eb1864f1649e ] Make sure to free and deregister the addrmatch and chancounts devices allocated during probe in all error paths. Also fix use-after-free in a probe error path and in the remove success path where the devices were

[PATCH AUTOSEL 4.18 120/136] gpio: Fix wrong rounding in gpio-menz127

2018-09-16 Thread Sasha Levin
From: Nadav Amit [ Upstream commit 7279d9917560bbd0d82813d6bf00490a82c06783 ] men_z127_debounce() tries to round up and down, but uses functions which are only suitable when the divider is a power of two, which is not the case. Use the appropriate ones. Found by static check. Compile tested.

[PATCH AUTOSEL 4.18 117/136] EDAC, i7core: Fix memleaks and use-after-free on probe and remove

2018-09-16 Thread Sasha Levin
From: Johan Hovold [ Upstream commit 6c974d4dfafe5e9ee754f2a6fba0eb1864f1649e ] Make sure to free and deregister the addrmatch and chancounts devices allocated during probe in all error paths. Also fix use-after-free in a probe error path and in the remove success path where the devices were

[PATCH AUTOSEL 4.18 082/136] media: tm6000: add error handling for dvb_register_adapter

2018-09-16 Thread Sasha Levin
From: Zhouyang Jia [ Upstream commit e95d7c6eb94c634852eaa5ff4caf3db05b5d2e86 ] When dvb_register_adapter fails, the lack of error-handling code may cause unexpected results. This patch adds error-handling code after calling dvb_register_adapter. Signed-off-by: Zhouyang Jia

[PATCH AUTOSEL 4.18 070/136] ath10k: use locked skb_dequeue for rx completions

2018-09-16 Thread Sasha Levin
From: Bob Copeland [ Upstream commit 62652555c616cad23a572f76cb5e870ab5395191 ] In our environment we are occasionally seeing the following stack trace in ath10k: Unable to handle kernel paging request at virtual address a800 pgd = c0204000 [a800] *pgd= Internal error: Oops: 17

[PATCH AUTOSEL 4.18 079/136] arm64: dts: renesas: salvator-common: Fix adv7482 decimal unit addresses

2018-09-16 Thread Sasha Levin
From: Geert Uytterhoeven [ Upstream commit c5a884838ce34681200b5a45b2330177036affd0 ] With recent dtc and W=1: ...salvator-x.dtb: Warning (graph_port): /soc/i2c@e66d8000/video-receiver@70/port@10: graph node unit address error, expected "a" ...salvator-x.dtb: Warning (graph_port):

[PATCH AUTOSEL 4.18 094/136] bitfield: fix *_encode_bits()

2018-09-16 Thread Sasha Levin
From: Johannes Berg [ Upstream commit e7d4a95da86e0b048702765bbdcdc968aaf312e7 ] There's a bug in *_encode_bits() in using ~field_multiplier() for the check whether or not the constant value fits into the field, this is wrong and clearly ~field_mask() was intended. This was triggering for me

[PATCH AUTOSEL 4.18 066/136] posix-timers: Sanitize overrun handling

2018-09-16 Thread Sasha Levin
From: Thomas Gleixner [ Upstream commit 78c9c4dfbf8c04883941445a195276bb4bb92c76 ] The posix timer overrun handling is broken because the forwarding functions can return a huge number of overruns which does not fit in an int. As a consequence timer_getoverrun(2) and siginfo::si_overrun can turn

[PATCH AUTOSEL 4.18 080/136] serial: pxa: Fix an error handling path in 'serial_pxa_probe()'

2018-09-16 Thread Sasha Levin
From: Christophe JAILLET [ Upstream commit 95a0e656580fab3128c7bee5f660c50784f53651 ] If port.line is out of range, we still need to release some resources, or we will leak them. Fixes: afc7851fab83 ("serial: pxa: Fix out-of-bounds access through serial port index") Signed-off-by: Christophe

[PATCH AUTOSEL 4.18 089/136] drm/sun4i: Fix releasing node when enumerating enpoints

2018-09-16 Thread Sasha Levin
From: Jernej Skrabec [ Upstream commit 367c359aa8637b15ee8df6335c5a29b7623966ec ] sun4i_drv_add_endpoints() has a memory leak since it uses of_node_put() when remote is equal to NULL and does nothing when remote has a valid pointer. Invert the logic to fix memory leak. Signed-off-by: Jernej

[PATCH AUTOSEL 4.18 090/136] ath10k: transmit queued frames after processing rx packets

2018-09-16 Thread Sasha Levin
From: Niklas Cassel [ Upstream commit 3f04950f32d5d592ab4fcaecac2178558a6f7437 ] When running iperf on ath10k SDIO, TX can stop working: iperf -c 192.168.1.1 -i 1 -t 20 -w 10K [ 3] 0.0- 1.0 sec 2.00 MBytes 16.8 Mbits/sec [ 3] 1.0- 2.0 sec 3.12 MBytes 26.2 Mbits/sec [ 3] 2.0- 3.0 sec

[PATCH AUTOSEL 4.18 082/136] media: tm6000: add error handling for dvb_register_adapter

2018-09-16 Thread Sasha Levin
From: Zhouyang Jia [ Upstream commit e95d7c6eb94c634852eaa5ff4caf3db05b5d2e86 ] When dvb_register_adapter fails, the lack of error-handling code may cause unexpected results. This patch adds error-handling code after calling dvb_register_adapter. Signed-off-by: Zhouyang Jia

[PATCH AUTOSEL 4.18 070/136] ath10k: use locked skb_dequeue for rx completions

2018-09-16 Thread Sasha Levin
From: Bob Copeland [ Upstream commit 62652555c616cad23a572f76cb5e870ab5395191 ] In our environment we are occasionally seeing the following stack trace in ath10k: Unable to handle kernel paging request at virtual address a800 pgd = c0204000 [a800] *pgd= Internal error: Oops: 17

[PATCH AUTOSEL 4.18 079/136] arm64: dts: renesas: salvator-common: Fix adv7482 decimal unit addresses

2018-09-16 Thread Sasha Levin
From: Geert Uytterhoeven [ Upstream commit c5a884838ce34681200b5a45b2330177036affd0 ] With recent dtc and W=1: ...salvator-x.dtb: Warning (graph_port): /soc/i2c@e66d8000/video-receiver@70/port@10: graph node unit address error, expected "a" ...salvator-x.dtb: Warning (graph_port):

[PATCH AUTOSEL 4.18 094/136] bitfield: fix *_encode_bits()

2018-09-16 Thread Sasha Levin
From: Johannes Berg [ Upstream commit e7d4a95da86e0b048702765bbdcdc968aaf312e7 ] There's a bug in *_encode_bits() in using ~field_multiplier() for the check whether or not the constant value fits into the field, this is wrong and clearly ~field_mask() was intended. This was triggering for me

[PATCH AUTOSEL 4.18 066/136] posix-timers: Sanitize overrun handling

2018-09-16 Thread Sasha Levin
From: Thomas Gleixner [ Upstream commit 78c9c4dfbf8c04883941445a195276bb4bb92c76 ] The posix timer overrun handling is broken because the forwarding functions can return a huge number of overruns which does not fit in an int. As a consequence timer_getoverrun(2) and siginfo::si_overrun can turn

[PATCH AUTOSEL 4.18 080/136] serial: pxa: Fix an error handling path in 'serial_pxa_probe()'

2018-09-16 Thread Sasha Levin
From: Christophe JAILLET [ Upstream commit 95a0e656580fab3128c7bee5f660c50784f53651 ] If port.line is out of range, we still need to release some resources, or we will leak them. Fixes: afc7851fab83 ("serial: pxa: Fix out-of-bounds access through serial port index") Signed-off-by: Christophe

[PATCH AUTOSEL 4.18 089/136] drm/sun4i: Fix releasing node when enumerating enpoints

2018-09-16 Thread Sasha Levin
From: Jernej Skrabec [ Upstream commit 367c359aa8637b15ee8df6335c5a29b7623966ec ] sun4i_drv_add_endpoints() has a memory leak since it uses of_node_put() when remote is equal to NULL and does nothing when remote has a valid pointer. Invert the logic to fix memory leak. Signed-off-by: Jernej

[PATCH AUTOSEL 4.18 090/136] ath10k: transmit queued frames after processing rx packets

2018-09-16 Thread Sasha Levin
From: Niklas Cassel [ Upstream commit 3f04950f32d5d592ab4fcaecac2178558a6f7437 ] When running iperf on ath10k SDIO, TX can stop working: iperf -c 192.168.1.1 -i 1 -t 20 -w 10K [ 3] 0.0- 1.0 sec 2.00 MBytes 16.8 Mbits/sec [ 3] 1.0- 2.0 sec 3.12 MBytes 26.2 Mbits/sec [ 3] 2.0- 3.0 sec

[PATCH AUTOSEL 4.18 109/136] iomap: complete partial direct I/O writes synchronously

2018-09-16 Thread Sasha Levin
From: Andreas Gruenbacher [ Upstream commit ebf00be37de35788cad72f4f20b4a39e30c0be4a ] According to xfstest generic/240, applications seem to expect direct I/O writes to either complete as a whole or to fail; short direct I/O writes are apparently not appreciated. This means that when only

[PATCH AUTOSEL 4.18 104/136] MIPS: boot: fix build rule of vmlinux.its.S

2018-09-16 Thread Sasha Levin
From: Masahiro Yamada [ Upstream commit 67e09db507db3e1642ddce512a4313d20addd6e5 ] As Documentation/kbuild/makefile.txt says, it is a typical mistake to forget the FORCE prerequisite for the rule invoked by if_changed. Add the FORCE to the prerequisite, but it must be filtered-out from the

[PATCH AUTOSEL 4.18 106/136] drm/v3d: Take a lock across GPU scheduler job creation and queuing.

2018-09-16 Thread Sasha Levin
From: Eric Anholt [ Upstream commit 7122b68b8a9692dcc3acf89595f04c492872115f ] Between creation and queueing of a job, you need to prevent any other job from being created and queued. Otherwise the scheduler's fences may be signaled out of seqno order. v2: move mutex unlock to the error

[PATCH AUTOSEL 4.18 109/136] iomap: complete partial direct I/O writes synchronously

2018-09-16 Thread Sasha Levin
From: Andreas Gruenbacher [ Upstream commit ebf00be37de35788cad72f4f20b4a39e30c0be4a ] According to xfstest generic/240, applications seem to expect direct I/O writes to either complete as a whole or to fail; short direct I/O writes are apparently not appreciated. This means that when only

[PATCH AUTOSEL 4.18 104/136] MIPS: boot: fix build rule of vmlinux.its.S

2018-09-16 Thread Sasha Levin
From: Masahiro Yamada [ Upstream commit 67e09db507db3e1642ddce512a4313d20addd6e5 ] As Documentation/kbuild/makefile.txt says, it is a typical mistake to forget the FORCE prerequisite for the rule invoked by if_changed. Add the FORCE to the prerequisite, but it must be filtered-out from the

[PATCH AUTOSEL 4.18 106/136] drm/v3d: Take a lock across GPU scheduler job creation and queuing.

2018-09-16 Thread Sasha Levin
From: Eric Anholt [ Upstream commit 7122b68b8a9692dcc3acf89595f04c492872115f ] Between creation and queueing of a job, you need to prevent any other job from being created and queued. Otherwise the scheduler's fences may be signaled out of seqno order. v2: move mutex unlock to the error

[PATCH AUTOSEL 4.18 047/136] scsi: target/iscsi: Make iscsit_ta_authentication() respect the output buffer size

2018-09-16 Thread Sasha Levin
From: Bart Van Assche [ Upstream commit 35bea5c84fd13c643cce63f0b5cd4b148f8c901d ] Fixes: e48354ce078c ("iscsi-target: Add iSCSI fabric support for target v4.1") Signed-off-by: Bart Van Assche Reviewed-by: Mike Christie Cc: Mike Christie Cc: Christoph Hellwig Cc: Hannes Reinecke

[PATCH AUTOSEL 4.18 055/136] powerpc/powernv/ioda2: Reduce upper limit for DMA window size

2018-09-16 Thread Sasha Levin
From: Alexey Kardashevskiy [ Upstream commit d3d4ffaae439981e1e441ebb125aa3588627c5d8 ] We use PHB in mode1 which uses bit 59 to select a correct DMA window. However there is mode2 which uses bits 59:55 and allows up to 32 DMA windows per a PE. Even though documentation does not clearly

[PATCH AUTOSEL 4.18 059/136] alarmtimer: Prevent overflow for relative nanosleep

2018-09-16 Thread Sasha Levin
From: Thomas Gleixner [ Upstream commit 5f936e19cc0ef97dbe3a56e9498922ad5ba1edef ] Air Icy reported: UBSAN: Undefined behaviour in kernel/time/alarmtimer.c:811:7 signed integer overflow: 1529859276030040771 + 9223372036854775807 cannot be represented in type 'long long int' Call

[PATCH AUTOSEL 4.18 060/136] s390/dasd: correct numa_node in dasd_alloc_queue

2018-09-16 Thread Sasha Levin
From: Vasily Gorbik [ Upstream commit b17e3abb0af404cb62ad4ef1a5962f58b06e2b78 ] The numa_node field of the tag_set struct has to be explicitly initialized, otherwise it stays as 0, which is a valid numa node id and cause memory allocation failure if node 0 is offline. Acked-by: Stefan

[PATCH AUTOSEL 4.18 041/136] IB/mlx5: Fix GRE flow specification

2018-09-16 Thread Sasha Levin
From: Maor Gottlieb [ Upstream commit a93b632c4531ff50c43d658447a45cbc11f488fd ] Currently the driver sets the mask of the gre_protocol to 0x without consideration in the user request. Fix it by copy the mask from the verbs spec. Fixes: da2f22ae7707 ("IB/mlx5: Add support for GRE flow

[PATCH AUTOSEL 4.18 047/136] scsi: target/iscsi: Make iscsit_ta_authentication() respect the output buffer size

2018-09-16 Thread Sasha Levin
From: Bart Van Assche [ Upstream commit 35bea5c84fd13c643cce63f0b5cd4b148f8c901d ] Fixes: e48354ce078c ("iscsi-target: Add iSCSI fabric support for target v4.1") Signed-off-by: Bart Van Assche Reviewed-by: Mike Christie Cc: Mike Christie Cc: Christoph Hellwig Cc: Hannes Reinecke

[PATCH AUTOSEL 4.18 055/136] powerpc/powernv/ioda2: Reduce upper limit for DMA window size

2018-09-16 Thread Sasha Levin
From: Alexey Kardashevskiy [ Upstream commit d3d4ffaae439981e1e441ebb125aa3588627c5d8 ] We use PHB in mode1 which uses bit 59 to select a correct DMA window. However there is mode2 which uses bits 59:55 and allows up to 32 DMA windows per a PE. Even though documentation does not clearly

[PATCH AUTOSEL 4.18 059/136] alarmtimer: Prevent overflow for relative nanosleep

2018-09-16 Thread Sasha Levin
From: Thomas Gleixner [ Upstream commit 5f936e19cc0ef97dbe3a56e9498922ad5ba1edef ] Air Icy reported: UBSAN: Undefined behaviour in kernel/time/alarmtimer.c:811:7 signed integer overflow: 1529859276030040771 + 9223372036854775807 cannot be represented in type 'long long int' Call

[PATCH AUTOSEL 4.18 060/136] s390/dasd: correct numa_node in dasd_alloc_queue

2018-09-16 Thread Sasha Levin
From: Vasily Gorbik [ Upstream commit b17e3abb0af404cb62ad4ef1a5962f58b06e2b78 ] The numa_node field of the tag_set struct has to be explicitly initialized, otherwise it stays as 0, which is a valid numa node id and cause memory allocation failure if node 0 is offline. Acked-by: Stefan

[PATCH AUTOSEL 4.18 041/136] IB/mlx5: Fix GRE flow specification

2018-09-16 Thread Sasha Levin
From: Maor Gottlieb [ Upstream commit a93b632c4531ff50c43d658447a45cbc11f488fd ] Currently the driver sets the mask of the gre_protocol to 0x without consideration in the user request. Fix it by copy the mask from the verbs spec. Fixes: da2f22ae7707 ("IB/mlx5: Add support for GRE flow

[PATCH AUTOSEL 4.18 063/136] mtd: rawnand: atmel: add module param to avoid using dma

2018-09-16 Thread Sasha Levin
From: Peter Rosin [ Upstream commit efc6362c6f8c1e74b340e2611f1b35e7d557ce7b ] On a sama5d31 with a Full-HD dual LVDS panel (132MHz pixel clock) NAND flash accesses have a tendency to cause display disturbances. Add a module param to disable DMA from the NAND controller, since that fixes the

[PATCH AUTOSEL 4.18 064/136] iio: accel: adxl345: convert address field usage in iio_chan_spec

2018-09-16 Thread Sasha Levin
From: Akinobu Mita [ Upstream commit 9048f1f18a70a01eaa3c8e7166fdb2538929d780 ] Currently the address field in iio_chan_spec is filled with an accel data register address for the corresponding axis. In preparation for adding calibration offset support, this sets the address field to the index

[PATCH AUTOSEL 4.18 063/136] mtd: rawnand: atmel: add module param to avoid using dma

2018-09-16 Thread Sasha Levin
From: Peter Rosin [ Upstream commit efc6362c6f8c1e74b340e2611f1b35e7d557ce7b ] On a sama5d31 with a Full-HD dual LVDS panel (132MHz pixel clock) NAND flash accesses have a tendency to cause display disturbances. Add a module param to disable DMA from the NAND controller, since that fixes the

[PATCH AUTOSEL 4.18 064/136] iio: accel: adxl345: convert address field usage in iio_chan_spec

2018-09-16 Thread Sasha Levin
From: Akinobu Mita [ Upstream commit 9048f1f18a70a01eaa3c8e7166fdb2538929d780 ] Currently the address field in iio_chan_spec is filled with an accel data register address for the corresponding axis. In preparation for adding calibration offset support, this sets the address field to the index

[PATCH AUTOSEL 4.18 052/136] usb: wusbcore: security: cast sizeof to int for comparison

2018-09-16 Thread Sasha Levin
From: Julia Lawall [ Upstream commit d3ac5598c5010a878ebbcca3b1c6188ca36b ] Comparing an int to a size, which is unsigned, causes the int to become unsigned, giving the wrong result. usb_get_descriptor can return a negative error code. A simplified version of the semantic match that finds

[PATCH AUTOSEL 4.18 067/136] ALSA: snd-aoa: add of_node_put() in error path

2018-09-16 Thread Sasha Levin
From: Nicholas Mc Guire [ Upstream commit 222bce5eb88d1af656419db04bcd84b2419fb900 ] Both calls to of_find_node_by_name() and of_get_next_child() return a node pointer with refcount incremented thus it must be explicidly decremented here after the last usage. As we are assured to have a

[PATCH AUTOSEL 4.18 048/136] thermal: i.MX: Allow thermal probe to fail gracefully in case of bad calibration.

2018-09-16 Thread Sasha Levin
From: Jean-Christophe Dubois [ Upstream commit be926ceeb4efc3bf44cb9b56f5c71aac9b1f8bbe ] Without this fix, the thermal probe on i.MX6 might trigger a division by zero exception later in the probe if the calibration does fail. Note: This linux behavior (Division by zero in kernel) has been

[PATCH AUTOSEL 4.18 065/136] posix-timers: Make forward callback return s64

2018-09-16 Thread Sasha Levin
From: Thomas Gleixner [ Upstream commit 6fec64e1c92d5c715c6d0f50786daa7708266bde ] The posix timer ti_overrun handling is broken because the forwarding functions can return a huge number of overruns which does not fit in an int. As a consequence timer_getoverrun(2) and siginfo::si_overrun can

[PATCH AUTOSEL 4.18 052/136] usb: wusbcore: security: cast sizeof to int for comparison

2018-09-16 Thread Sasha Levin
From: Julia Lawall [ Upstream commit d3ac5598c5010a878ebbcca3b1c6188ca36b ] Comparing an int to a size, which is unsigned, causes the int to become unsigned, giving the wrong result. usb_get_descriptor can return a negative error code. A simplified version of the semantic match that finds

[PATCH AUTOSEL 4.18 067/136] ALSA: snd-aoa: add of_node_put() in error path

2018-09-16 Thread Sasha Levin
From: Nicholas Mc Guire [ Upstream commit 222bce5eb88d1af656419db04bcd84b2419fb900 ] Both calls to of_find_node_by_name() and of_get_next_child() return a node pointer with refcount incremented thus it must be explicidly decremented here after the last usage. As we are assured to have a

[PATCH AUTOSEL 4.18 048/136] thermal: i.MX: Allow thermal probe to fail gracefully in case of bad calibration.

2018-09-16 Thread Sasha Levin
From: Jean-Christophe Dubois [ Upstream commit be926ceeb4efc3bf44cb9b56f5c71aac9b1f8bbe ] Without this fix, the thermal probe on i.MX6 might trigger a division by zero exception later in the probe if the calibration does fail. Note: This linux behavior (Division by zero in kernel) has been

[PATCH AUTOSEL 4.18 065/136] posix-timers: Make forward callback return s64

2018-09-16 Thread Sasha Levin
From: Thomas Gleixner [ Upstream commit 6fec64e1c92d5c715c6d0f50786daa7708266bde ] The posix timer ti_overrun handling is broken because the forwarding functions can return a huge number of overruns which does not fit in an int. As a consequence timer_getoverrun(2) and siginfo::si_overrun can

[PATCH AUTOSEL 4.18 026/136] drm/amd/display: fix use of uninitialized memory

2018-09-16 Thread Sasha Levin
From: Wesley Chalmers [ Upstream commit f3e077d95ca0a016fdf3d6b1e97a9910dfdaff17 ] DML does not calculate chroma values for RQ when surface is not YUV, but DC will unconditionally use the uninitialized values for HW programming. This does not cause visual corruption since HW will ignore garbage

[PATCH AUTOSEL 4.18 025/136] drm/amd/display/dc/dce: Fix multiple potential integer overflows

2018-09-16 Thread Sasha Levin
From: "Gustavo A. R. Silva" [ Upstream commit 6f3472a993e7cb63cde5d818dcabc8e42fc03744 ] Add suffix ULL to constant 5 and cast variables target_pix_clk_khz and feedback_divider to uint64_t in order to avoid multiple potential integer overflows and give the compiler complete information about

[PATCH AUTOSEL 4.18 027/136] md-cluster: clear another node's suspend_area after the copy is finished

2018-09-16 Thread Sasha Levin
From: Guoqing Jiang [ Upstream commit 010228e4a932ca1e8365e3b58c8e1e44c16ff793 ] When one node leaves cluster or stops the resyncing (resync or recovery) array, then other nodes need to call recover_bitmaps to continue the unfinished task. But we need to clear suspend_area later after other

[PATCH AUTOSEL 4.18 028/136] cxgb4: Fix the condition to check if the card is T5

2018-09-16 Thread Sasha Levin
From: Ganesh Goudar [ Upstream commit dfecc759e64b0ea581468fe2359836f1998deac9 ] Use 'chip_ver' rather than 'chip' to check if the card is T5. Fixes: e8d452923ae6 ("cxgb4: clean up init_one") Signed-off-by: Ganesh Goudar Signed-off-by: David S. Miller Signed-off-by: Sasha Levin ---

[PATCH AUTOSEL 4.18 026/136] drm/amd/display: fix use of uninitialized memory

2018-09-16 Thread Sasha Levin
From: Wesley Chalmers [ Upstream commit f3e077d95ca0a016fdf3d6b1e97a9910dfdaff17 ] DML does not calculate chroma values for RQ when surface is not YUV, but DC will unconditionally use the uninitialized values for HW programming. This does not cause visual corruption since HW will ignore garbage

[PATCH AUTOSEL 4.18 025/136] drm/amd/display/dc/dce: Fix multiple potential integer overflows

2018-09-16 Thread Sasha Levin
From: "Gustavo A. R. Silva" [ Upstream commit 6f3472a993e7cb63cde5d818dcabc8e42fc03744 ] Add suffix ULL to constant 5 and cast variables target_pix_clk_khz and feedback_divider to uint64_t in order to avoid multiple potential integer overflows and give the compiler complete information about

[PATCH AUTOSEL 4.18 027/136] md-cluster: clear another node's suspend_area after the copy is finished

2018-09-16 Thread Sasha Levin
From: Guoqing Jiang [ Upstream commit 010228e4a932ca1e8365e3b58c8e1e44c16ff793 ] When one node leaves cluster or stops the resyncing (resync or recovery) array, then other nodes need to call recover_bitmaps to continue the unfinished task. But we need to clear suspend_area later after other

[PATCH AUTOSEL 4.18 028/136] cxgb4: Fix the condition to check if the card is T5

2018-09-16 Thread Sasha Levin
From: Ganesh Goudar [ Upstream commit dfecc759e64b0ea581468fe2359836f1998deac9 ] Use 'chip_ver' rather than 'chip' to check if the card is T5. Fixes: e8d452923ae6 ("cxgb4: clean up init_one") Signed-off-by: Ganesh Goudar Signed-off-by: David S. Miller Signed-off-by: Sasha Levin ---

[PATCH AUTOSEL 4.18 032/136] arm64: fix infinite stacktrace

2018-09-16 Thread Sasha Levin
From: Mikulas Patocka [ Upstream commit 7e7df71fd57ff2894d96abb0080922bf39460a79 ] I've got this infinite stacktrace when debugging another problem: [ 908.795225] INFO: rcu_preempt detected stalls on CPUs/tasks: [ 908.796176] 1-...!: (1 GPs behind) idle=952/1/4611686018427387904

[PATCH AUTOSEL 4.18 032/136] arm64: fix infinite stacktrace

2018-09-16 Thread Sasha Levin
From: Mikulas Patocka [ Upstream commit 7e7df71fd57ff2894d96abb0080922bf39460a79 ] I've got this infinite stacktrace when debugging another problem: [ 908.795225] INFO: rcu_preempt detected stalls on CPUs/tasks: [ 908.796176] 1-...!: (1 GPs behind) idle=952/1/4611686018427387904

[PATCH AUTOSEL 4.18 029/136] RDMA/bnxt_re: Fix a couple off by one bugs

2018-09-16 Thread Sasha Levin
From: Dan Carpenter [ Upstream commit 474e5a86067e5f12c97d1db8b170c7f45b53097a ] The sgid_tbl->tbl[] array is allocated in bnxt_qplib_alloc_sgid_tbl(). It has sgid_tbl->max elements. So the > should be >= to prevent accessing one element beyond the end of the array. Fixes: 1ac5a4047975

[PATCH AUTOSEL 4.18 021/136] 6lowpan: iphc: reset mac_header after decompress to fix panic

2018-09-16 Thread Sasha Levin
From: Michael Scott [ Upstream commit 03bc05e1a4972f73b4eb8907aa373369e825c252 ] After decompression of 6lowpan socket data, an IPv6 header is inserted before the existing socket payload. After this, we reset the network_header value of the skb to account for the difference in payload size

[PATCH AUTOSEL 4.18 029/136] RDMA/bnxt_re: Fix a couple off by one bugs

2018-09-16 Thread Sasha Levin
From: Dan Carpenter [ Upstream commit 474e5a86067e5f12c97d1db8b170c7f45b53097a ] The sgid_tbl->tbl[] array is allocated in bnxt_qplib_alloc_sgid_tbl(). It has sgid_tbl->max elements. So the > should be >= to prevent accessing one element beyond the end of the array. Fixes: 1ac5a4047975

[PATCH AUTOSEL 4.18 021/136] 6lowpan: iphc: reset mac_header after decompress to fix panic

2018-09-16 Thread Sasha Levin
From: Michael Scott [ Upstream commit 03bc05e1a4972f73b4eb8907aa373369e825c252 ] After decompression of 6lowpan socket data, an IPv6 header is inserted before the existing socket payload. After this, we reset the network_header value of the skb to account for the difference in payload size

[PATCH AUTOSEL 4.18 015/136] serial: sh-sci: Stop RX FIFO timer during port shutdown

2018-09-16 Thread Sasha Levin
From: Geert Uytterhoeven [ Upstream commit c5a9262fa8bfed0dddc7466ef10fcd292e2af61b ] The RX FIFO timer may be armed when the port is shut down, hence the timer function may still be called afterwards. Fix this race condition by deleting the timer during port shutdown. Fixes: 039403765e5da3c6

[PATCH AUTOSEL 4.18 010/136] net: hns3: Fix get_vector ops in hclgevf_main module

2018-09-16 Thread Sasha Levin
From: Yunsheng Lin [ Upstream commit 03718db97bfb57535f3aa8110f0cbe0c616a67c0 ] The hclgevf_free_vector function expects the caller to pass the vector_id to it, and hclgevf_put_vector pass vector to it now, which will cause vector allocation problem. This patch fixes it by converting vector

[PATCH AUTOSEL 4.18 002/136] iio: adc: ina2xx: avoid kthread_stop() with stale task_struct

2018-09-16 Thread Sasha Levin
From: Akinobu Mita [ Upstream commit 7d6cd21d82bacab2d1786fe5e989e4815b75d9a3 ] When the buffer is enabled for ina2xx driver, a dedicated kthread is invoked to capture mesurement data. When the buffer is disabled, the kthread is stopped. However if the kthread gets register access errors, it

[PATCH AUTOSEL 4.18 030/136] RDMA/i40w: Hold read semaphore while looking after VMA

2018-09-16 Thread Sasha Levin
From: Leon Romanovsky [ Upstream commit 5d9a2b0e28759e319a623da33940dbb3ce952b7d ] VMA lookup is supposed to be performed while mmap_sem is held. Fixes: f26c7c83395b ("i40iw: Add 2MB page support") Signed-off-by: Leon Romanovsky Signed-off-by: Jason Gunthorpe Signed-off-by: Sasha Levin ---

[PATCH AUTOSEL 4.18 004/136] misc: ibmvmc: Use GFP_ATOMIC under spin lock

2018-09-16 Thread Sasha Levin
From: Wei Yongjun [ Upstream commit 97b715b62e5b4c6edb75d023f556fd09a46cb4e1 ] The function alloc_dma_buffer() is called from ibmvmc_add_buffer(), in which a spin lock be held here, so we should use GFP_ATOMIC when a lock is held. Fixes: 0eca353e7ae7 ("misc: IBM Virtual Management Channel

[PATCH AUTOSEL 4.18 001/136] crypto: skcipher - Fix -Wstringop-truncation warnings

2018-09-16 Thread Sasha Levin
From: Stafford Horne [ Upstream commit cefd769fd0192c84d638f66da202459ed8ad63ba ] As of GCC 9.0.0 the build is reporting warnings like: crypto/ablkcipher.c: In function ‘crypto_ablkcipher_report’: crypto/ablkcipher.c:374:2: warning: ‘strncpy’ specified bound 64 equals destination size

[PATCH AUTOSEL 4.18 008/136] net: hns3: Fix for mac pause not disable in pfc mode

2018-09-16 Thread Sasha Levin
From: Yunsheng Lin [ Upstream commit 6d0ec65cb5810f9bf08671be008785bb8c84d39f ] When pfc pause mode is enable, the mac pause mode need to be disabled, otherwise the pfc pause packet will not be sent when congestion happens. This patch fixes by disabling the mac pause when pfc pause is enabled.

[PATCH AUTOSEL 4.18 007/136] net: hns3: Fix for mailbox message truncated problem

2018-09-16 Thread Sasha Levin
From: Fuyun Liang [ Upstream commit ead5bd4d35c0a14d5ce1474177718c678dff5205 ] The payload of mailbox message is 16 byte and the value of HCLGE_MBX_MAX_ARQ_MSG_SIZE is 8. A message truncated problem will happen when mailbox message is converted to ARQ message. This patch replaces

[PATCH AUTOSEL 4.18 015/136] serial: sh-sci: Stop RX FIFO timer during port shutdown

2018-09-16 Thread Sasha Levin
From: Geert Uytterhoeven [ Upstream commit c5a9262fa8bfed0dddc7466ef10fcd292e2af61b ] The RX FIFO timer may be armed when the port is shut down, hence the timer function may still be called afterwards. Fix this race condition by deleting the timer during port shutdown. Fixes: 039403765e5da3c6

[PATCH AUTOSEL 4.18 010/136] net: hns3: Fix get_vector ops in hclgevf_main module

2018-09-16 Thread Sasha Levin
From: Yunsheng Lin [ Upstream commit 03718db97bfb57535f3aa8110f0cbe0c616a67c0 ] The hclgevf_free_vector function expects the caller to pass the vector_id to it, and hclgevf_put_vector pass vector to it now, which will cause vector allocation problem. This patch fixes it by converting vector

[PATCH AUTOSEL 4.18 002/136] iio: adc: ina2xx: avoid kthread_stop() with stale task_struct

2018-09-16 Thread Sasha Levin
From: Akinobu Mita [ Upstream commit 7d6cd21d82bacab2d1786fe5e989e4815b75d9a3 ] When the buffer is enabled for ina2xx driver, a dedicated kthread is invoked to capture mesurement data. When the buffer is disabled, the kthread is stopped. However if the kthread gets register access errors, it

[PATCH AUTOSEL 4.18 030/136] RDMA/i40w: Hold read semaphore while looking after VMA

2018-09-16 Thread Sasha Levin
From: Leon Romanovsky [ Upstream commit 5d9a2b0e28759e319a623da33940dbb3ce952b7d ] VMA lookup is supposed to be performed while mmap_sem is held. Fixes: f26c7c83395b ("i40iw: Add 2MB page support") Signed-off-by: Leon Romanovsky Signed-off-by: Jason Gunthorpe Signed-off-by: Sasha Levin ---

[PATCH AUTOSEL 4.18 004/136] misc: ibmvmc: Use GFP_ATOMIC under spin lock

2018-09-16 Thread Sasha Levin
From: Wei Yongjun [ Upstream commit 97b715b62e5b4c6edb75d023f556fd09a46cb4e1 ] The function alloc_dma_buffer() is called from ibmvmc_add_buffer(), in which a spin lock be held here, so we should use GFP_ATOMIC when a lock is held. Fixes: 0eca353e7ae7 ("misc: IBM Virtual Management Channel

[PATCH AUTOSEL 4.18 001/136] crypto: skcipher - Fix -Wstringop-truncation warnings

2018-09-16 Thread Sasha Levin
From: Stafford Horne [ Upstream commit cefd769fd0192c84d638f66da202459ed8ad63ba ] As of GCC 9.0.0 the build is reporting warnings like: crypto/ablkcipher.c: In function ‘crypto_ablkcipher_report’: crypto/ablkcipher.c:374:2: warning: ‘strncpy’ specified bound 64 equals destination size

[PATCH AUTOSEL 4.18 008/136] net: hns3: Fix for mac pause not disable in pfc mode

2018-09-16 Thread Sasha Levin
From: Yunsheng Lin [ Upstream commit 6d0ec65cb5810f9bf08671be008785bb8c84d39f ] When pfc pause mode is enable, the mac pause mode need to be disabled, otherwise the pfc pause packet will not be sent when congestion happens. This patch fixes by disabling the mac pause when pfc pause is enabled.

[PATCH AUTOSEL 4.18 007/136] net: hns3: Fix for mailbox message truncated problem

2018-09-16 Thread Sasha Levin
From: Fuyun Liang [ Upstream commit ead5bd4d35c0a14d5ce1474177718c678dff5205 ] The payload of mailbox message is 16 byte and the value of HCLGE_MBX_MAX_ARQ_MSG_SIZE is 8. A message truncated problem will happen when mailbox message is converted to ARQ message. This patch replaces

Re: Linux 4.19-rc4 released, an apology, and a maintainership note

2018-09-16 Thread Luke Kenneth Casson Leighton
hi linus, just saw the note on slashdot. i just wanted to say how amazed, relieved and delighted i was to see what you wrote. that you recognised that you needed to reflect, *sought feedback*, and, most importantly, were willing and able to discuss that and ask publicly. as the longest-serving

Re: Linux 4.19-rc4 released, an apology, and a maintainership note

2018-09-16 Thread Luke Kenneth Casson Leighton
hi linus, just saw the note on slashdot. i just wanted to say how amazed, relieved and delighted i was to see what you wrote. that you recognised that you needed to reflect, *sought feedback*, and, most importantly, were willing and able to discuss that and ask publicly. as the longest-serving

Re: [BUG] mfd: ezx-pcap: Possible sleep-in-atomic-context bugs in pcap_adc_irq()

2018-09-16 Thread Jia-Ju Bai
On 2018/9/17 9:03, Lee Jones wrote: On Sat, 15 Sep 2018, Jia-Ju Bai wrote: The driver may sleep in an interrupt handler. The function call paths (from bottom to top) in Linux-4.17 are: [FUNC] mutex_lock_nested drivers/mfd/ezx-pcap.c, 272: mutex_lock_nested in pcap_adc_irq (interrupt

Re: [BUG] mfd: ezx-pcap: Possible sleep-in-atomic-context bugs in pcap_adc_irq()

2018-09-16 Thread Jia-Ju Bai
On 2018/9/17 9:03, Lee Jones wrote: On Sat, 15 Sep 2018, Jia-Ju Bai wrote: The driver may sleep in an interrupt handler. The function call paths (from bottom to top) in Linux-4.17 are: [FUNC] mutex_lock_nested drivers/mfd/ezx-pcap.c, 272: mutex_lock_nested in pcap_adc_irq (interrupt

[PATCH] power: supply: bq25890_charger: fix semicolon.cocci warnings

2018-09-16 Thread kbuild test robot
From: kbuild test robot drivers/power/supply/bq25890_charger.c:614:2-3: Unneeded semicolon drivers/power/supply/bq25890_charger.c:621:2-3: Unneeded semicolon drivers/power/supply/bq25890_charger.c:630:3-4: Unneeded semicolon drivers/power/supply/bq25890_charger.c:638:2-3: Unneeded semicolon

[PATCH] power: supply: bq25890_charger: fix semicolon.cocci warnings

2018-09-16 Thread kbuild test robot
From: kbuild test robot drivers/power/supply/bq25890_charger.c:614:2-3: Unneeded semicolon drivers/power/supply/bq25890_charger.c:621:2-3: Unneeded semicolon drivers/power/supply/bq25890_charger.c:630:3-4: Unneeded semicolon drivers/power/supply/bq25890_charger.c:638:2-3: Unneeded semicolon

[PATCH v3 0/3] Add Mediatek SPI slave driver

2018-09-16 Thread Leilk Liu
>From 82bced99683343899dea4634452940b15d6374eb Mon Sep 17 00:00:00 2001 From: Leilk Liu Date: Mon, 17 Sep 2018 10:07:45 +0800 Subject: [PATCH v3 0/3] Add Mediatek SPI slave driver v3: 1. Fix Rob Herring review comment about bindings. 2. remove unused variables in driver. v2: 1. Fix Sean Wang

[PATCH v3 3/3] arm64: dts: Add spi slave dts

2018-09-16 Thread Leilk Liu
This patch adds MT2712 spi slave into device tree. Signed-off-by: Leilk Liu --- arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi index

<    3   4   5   6   7   8   9   10   11   >