[PATCH 5.0 07/95] staging: most: sound: pass correct device when creating a sound card

2019-05-09 Thread Greg Kroah-Hartman
From: Christian Gromm commit 98592c1faca82a9024a64e4ecead68b19f81c299 upstream. This patch fixes the usage of the wrong struct device when calling function snd_card_new. Reported-by: Eugeniu Rosca Signed-off-by: Christian Gromm Fixes: 69c90cf1b2fa ("staging: most: sound: call snd_card_new

[PATCH 5.0 09/95] ASoC: hdmi-codec: fix S/PDIF DAI

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 2e95f984aae4cf0608d0ba2189c756f2bd50b44a ] When using the S/PDIF DAI, there is no requirement to call snd_soc_dai_set_fmt() as there is no DAI format definition that defines S/PDIF. In any case, S/PDIF does not have separate clocks, this is embedded into the data stream.

[PATCH 4.19 52/66] USB: serial: f81232: fix interrupt worker not stop

2019-05-09 Thread Greg Kroah-Hartman
From: Ji-Ze Hong (Peter Hong) commit 804dbee1e49774918339c1e5a87400988c0819e8 upstream. The F81232 will use interrupt worker to handle MSR change. This patch will fix the issue that interrupt work should stop in close() and suspend(). This also fixes line-status events being disabled after a

[PATCH 4.19 50/66] genirq: Prevent use-after-free and work list corruption

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 59c39840f5abf4a71e1810a8da71aaccd6c17d26 ] When irq_set_affinity_notifier() replaces the notifier, then the reference count on the old notifier is dropped which causes it to be freed. But nothing ensures that the old notifier is not longer queued in the work list. If it is

[PATCH 5.0 10/95] ASoC: stm32: sai: fix iec958 controls indexation

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 5f8a1000c3e630c3ac06f1d664eeaa755bce8823 ] Allow indexation of sai iec958 controls according to device id. Signed-off-by: Olivier Moysan Signed-off-by: Mark Brown Signed-off-by: Sasha Levin --- sound/soc/stm/stm32_sai_sub.c | 7 --- 1 file changed, 4 insertions(+), 3

[PATCH 5.0 23/95] ASoC: wm_adsp: Add locking to wm_adsp2_bus_error

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit a2225a6d155fcb247fe4c6d87f7c91807462966d ] Best to lock across handling the bus error to ensure the DSP doesn't change power state as we are reading the status registers. Signed-off-by: Charles Keepax Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

[PATCH 5.0 21/95] ASoC: rt5682: fix jack type detection issue

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 675212bfb23394514b7f68ebf3954ba936281ccc ] The jack type detection needs the main bias power of analog. The modification makes sure the main bias power on/off while jack plug/unplug. Signed-off-by: Shuming Fan Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

[PATCH 4.19 66/66] arm64: futex: Bound number of LDXR/STXR loops in FUTEX_WAKE_OP

2019-05-09 Thread Greg Kroah-Hartman
From: Will Deacon commit 03110a5cb2161690ae5ac04994d47ed0cd6cef75 upstream. Our futex implementation makes use of LDXR/STXR loops to perform atomic updates to user memory from atomic context. This can lead to latency problems if we end up spinning around the LL/SC sequence at the expense of

[PATCH 4.19 47/66] platform/x86: pmc_atom: Drop __initconst on dmi table

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit b995dcca7cf12f208cfd95fd9d5768dca7cccec7 ] It's used by probe and that isn't an init function. Drop this so that we don't get a section mismatch. Reported-by: kbuild test robot Cc: David Müller Cc: Hans de Goede Cc: Andy Shevchenko Fixes: 7c2e07130090 ("clk: x86: Add system

[PATCH 5.0 13/95] ASoC:soc-pcm:fix a codec fixup issue in TDM case

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 570f18b6a8d1f0e60e8caf30e66161b6438dcc91 ] On HDaudio platforms, if playback is started when capture is working, there is no audible output. This can be root-caused to the use of the rx|tx_mask to store an HDaudio stream tag. If capture is stared before playback, rx_mask would

[PATCH 4.19 64/66] ASoC: Intel: avoid Oops if DMA setup fails

2019-05-09 Thread Greg Kroah-Hartman
From: Ross Zwisler commit 0efa3334d65b7f421ba12382dfa58f6ff5bf83c4 upstream. Currently in sst_dsp_new() if we get an error return from sst_dma_new() we just print an error message and then still complete the function successfully. This means that we are trying to run without sst->dma properly

[PATCH 5.0 24/95] clk: meson-gxbb: round the vdec dividers to closest

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 9b70c697e87286ade406e6a02091757307dd4b7c ] We want the video decoder clocks to always round to closest. While the muxes are already using CLK_MUX_ROUND_CLOSEST, the corresponding CLK_DIVIDER_ROUND_CLOSEST was forgotten for the dividers. Fix this by adding the flag to the two

[PATCH 4.19 53/66] USB: cdc-acm: fix unthrottle races

2019-05-09 Thread Greg Kroah-Hartman
From: Johan Hovold commit 764478f41130f1b8d8057575b89e69980a0f600d upstream. Fix two long-standing bugs which could potentially lead to memory corruption or leave the port throttled until it is reopened (on weakly ordered systems), respectively, when read-URB completion races with unthrottle().

[PATCH 4.19 65/66] locking/futex: Allow low-level atomic operations to return -EAGAIN

2019-05-09 Thread Greg Kroah-Hartman
From: Will Deacon commit 6b4f4bc9cb22875f97023984a625386f0c7cc1c0 upstream. Some futex() operations, including FUTEX_WAKE_OP, require the kernel to perform an atomic read-modify-write of the futex word via the userspace mapping. These operations are implemented by each architecture in

[PATCH 5.0 03/95] ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings

2019-05-09 Thread Greg Kroah-Hartman
From: Andrey Ryabinin commit f0996bc2978e02d2ea898101462b960f6119b18f upstream. Building lib/ubsan.c with gcc-9 results in a ton of nasty warnings like this one: lib/ubsan.c warning: conflicting types for built-in function ‘__ubsan_handle_negate_overflow’; expected ‘void(void *,

[PATCH 5.0 27/95] ASoC: cs4270: Set auto-increment bit for register writes

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit f0f2338a9cfaf71db895fa989ea7234e8a9b471d ] The CS4270 does not by default increment the register address on consecutive writes. During normal operation it doesn't matter as all register accesses are done individually. At resume time after suspend, however, the regcache code

[PATCH 5.0 15/95] ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit c899df3e9b0bf7b76e642aed1a214582ea7012d5 ] If playback and capture are enabled concurrently, when the capture stops the output becomes inaudile. The playback application will become stuck and underrun after a timeout. This is caused by mistaken use of the stream_id, which

[PATCH 5.0 11/95] ASoC: stm32: sai: fix exposed capabilities in spdif mode

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit b8468192971807c43a80d6e2c41f83141cb7b211 ] Change capabilities exposed in SAI S/PDIF mode, to match actually supported formats. In S/PDIF mode only 32 bits stereo is supported. Signed-off-by: Olivier Moysan Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

[PATCH 5.0 12/95] ASoC: stm32: sai: fix race condition in irq handler

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 26f98e82dd49b7c3cc5ef0edd882aa732a62b672 ] When snd_pcm_stop_xrun() is called in interrupt routine, substream context may have already been released. Add protection on substream context. Signed-off-by: Olivier Moysan Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

[PATCH 5.0 16/95] ASoC: dpcm: prevent snd_soc_dpcm use after free

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit a9764869779081e8bf24da07ac040e8f3efcf13a ] The dpcm get from fe_clients/be_clients may be free before use Add a spin lock at snd_soc_card level, to protect the dpcm instance. The lock may be used in atomic context, so use spin lock. Use irq spin lock version, since the lock

[PATCH 5.0 26/95] ASoC: stm32: dfsdm: fix debugfs warnings on entry creation

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit c47255b61129857b74b0d86eaf59335348be05e0 ] Register platform component with a prefix, to avoid warnings on debugfs entries creation, due to component name redundancy. Signed-off-by: Olivier Moysan Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

[PATCH 4.19 51/66] usb: dwc3: Fix default lpm_nyet_threshold value

2019-05-09 Thread Greg Kroah-Hartman
From: Thinh Nguyen commit 8d791929b2fbdf7734c1596d808e55cb457f4562 upstream. The max possible value for DCTL.LPM_NYET_THRES is 15 and not 255. Change the default value to 15. Cc: sta...@vger.kernel.org Fixes: 80caf7d21adc ("usb: dwc3: add lpm erratum support") Signed-off-by: Thinh Nguyen

[PATCH 4.19 54/66] usb-storage: Set virt_boundary_mask to avoid SG overflows

2019-05-09 Thread Greg Kroah-Hartman
From: Alan Stern commit 747668dbc061b3e62bc1982767a3a1f9815fcf0e upstream. The USB subsystem has always had an unusual requirement for its scatter-gather transfers: Each element in the scatterlist (except the last one) must have a length divisible by the bulk maxpacket size. This is a

[PATCH 4.19 46/66] nvme-fc: correct csn initialization and increments on error

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 67f471b6ed3b09033c4ac77ea03f92afdb1989fe ] This patch fixes a long-standing bug that initialized the FC-NVME cmnd iu CSN value to 1. Early FC-NVME specs had the connection starting with CSN=1. By the time the spec reached approval, the language had changed to state a connection

[PATCH 4.19 60/66] scsi: qla2xxx: Fix device staying in blocked state

2019-05-09 Thread Greg Kroah-Hartman
From: Quinn Tran commit 2137490f2147a8d0799b72b9a1023efb012d40c7 upstream. This patch fixes issue reported by some of the customers, who discovered that after cable pull scenario the devices disappear and path seems to remain in blocked state. Once the device reappears, driver does not seem to

[PATCH 4.19 63/66] UAS: fix alignment of scatter/gather segments

2019-05-09 Thread Greg Kroah-Hartman
From: Oliver Neukum commit 3ae62a42090f1ed48e2313ed256a1182a85fb575 upstream. This is the UAS version of 747668dbc061b3e62bc1982767a3a1f9815fcf0e usb-storage: Set virt_boundary_mask to avoid SG overflows We are not as likely to be vulnerable as storage, as it is unlikelier that UAS is run

[PATCH 4.19 55/66] intel_th: pci: Add Comet Lake support

2019-05-09 Thread Greg Kroah-Hartman
From: Alexander Shishkin commit e60e9a4b231a20a199d7a61caadc48693c30d695 upstream. This adds support for Intel TH on Comet Lake. Signed-off-by: Alexander Shishkin Cc: stable Signed-off-by: Greg Kroah-Hartman --- drivers/hwtracing/intel_th/pci.c |5 + 1 file changed, 5

[PATCH 4.19 62/66] Bluetooth: Align minimum encryption key size for LE and BR/EDR connections

2019-05-09 Thread Greg Kroah-Hartman
From: Marcel Holtmann commit d5bb334a8e171b262e48f378bd2096c0ea458265 upstream. The minimum encryption key size for LE connections is 56 bits and to align LE with BR/EDR, enforce 56 bits of minimum encryption key size for BR/EDR connections as well. Signed-off-by: Marcel Holtmann

[PATCH 4.19 56/66] cpufreq: armada-37xx: fix frequency calculation for opp

2019-05-09 Thread Greg Kroah-Hartman
From: Gregory CLEMENT commit 8db82563451f976597ab7b282ec655e4390a4088 upstream. The frequency calculation was based on the current(max) frequency of the CPU. However for low frequency, the value used was already the parent frequency divided by a factor of 2. Instead of using this frequency,

[PATCH 4.19 58/66] scsi: lpfc: change snprintf to scnprintf for possible overflow

2019-05-09 Thread Greg Kroah-Hartman
From: Silvio Cesare commit e7f7b6f38a44697428f5a2e7c606de028df2b0e3 upstream. Change snprintf to scnprintf. There are generally two cases where using snprintf causes problems. 1) Uses of size += snprintf(buf, SIZE - size, fmt, ...) In this case, if snprintf would have written more characters

[PATCH 4.19 13/66] ASoC: nau8824: fix the issue of the widget with prefix name

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 844a4a362dbec166b44d6b9b3dd45b08cb273703 ] The driver has two issues when machine add prefix name for codec. (1)The stream name of DAI can't find the AIF widgets. (2)The drivr can enable/disalbe the MICBIAS and SAR widgets. The patch will fix these issues caused by prefixed

[PATCH 4.19 12/66] ASoC:intel:skl:fix a simultaneous playback & capture issue on hda platform

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit c899df3e9b0bf7b76e642aed1a214582ea7012d5 ] If playback and capture are enabled concurrently, when the capture stops the output becomes inaudile. The playback application will become stuck and underrun after a timeout. This is caused by mistaken use of the stream_id, which

[PATCH 4.19 14/66] ASoC: nau8810: fix the issue of widget with prefixed name

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 54d1cf78b0f4ba348a7c7fb8b7d0708d71b6cc8a ] The driver changes the stream name of DAC and ADC to avoid the issue of widget with prefixed name. When the machine adds prefixed name for codec, the stream name of DAI may not find the widgets. Signed-off-by: John Hsu Signed-off-by:

[PATCH 4.19 43/66] drm/mediatek: fix possible object reference leak

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 2ae2c3316fb77dcf64275d011596b60104c45426 ] 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:

[PATCH 4.19 38/66] drm/sun4i: tcon top: Fix NULL/invalid pointer dereference in sun8i_tcon_top_un/bind

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 1a07a94b47b1f528f39c3e6187b5eaf02efe44ea ] There are two problems here: 1. Not all clk_data->hws[] need to be initialized, depending on various configured quirks. This leads to NULL ptr deref in clk_hw_unregister_gate() in sun8i_tcon_top_unbind() 2. If there is error when

[PATCH 4.19 39/66] virtio_pci: fix a NULL pointer reference in vp_del_vqs

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 6a8aae68c87349dbbcd46eac380bc43cdb98a13b ] If the msix_affinity_masks is alloced failed, then we'll try to free some resources in vp_free_vectors() that may access it directly. We met the following stack in our production: [ 29.296767] BUG: unable to handle kernel NULL

[PATCH 4.19 23/66] drm/omap: hdmi4_cec: Fix CEC clock handling for PM

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 36a1da15b5df493241b0011d2185fdd724ac1ed1 ] If CONFIG_OMAP4_DSS_HDMI_CEC is enabled in .config, deeper SoC idle states are blocked because the CEC clock gets always enabled on init. Let's fix the issue by moving the CEC clock handling to happen later in hdmi_cec_adap_enable() as

[PATCH 4.19 31/66] linux/kernel.h: Use parentheses around argument in u64_to_user_ptr()

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit a0fe2c6479aab5723239b315ef1b552673f434a3 ] Use parentheses around uses of the argument in u64_to_user_ptr() to ensure that the cast doesn't apply to part of the argument. There are existing uses of the macro of the form u64_to_user_ptr(A + B) which expands to (void

[PATCH 4.19 25/66] IB/hfi1: Fix the allocation of RSM table

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit d0294344470e6b52d097aa7369173f32d11f2f52 ] The receive side mapping (RSM) on hfi1 hardware is a special matching mechanism to direct an incoming packet to a given hardware receive context. It has 4 instances of matching capabilities (RSM0 - RSM3) that share the same RSM table

[PATCH 4.19 24/66] IB/hfi1: Eliminate opcode tests on mr deref

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit a8639a79e85c18c16c10089edd589c7948f19bbd ] When an old ack_queue entry is used to store an incoming request, it may need to clean up the old entry if it is still referencing the MR. Originally only RDMA READ request needed to reference MR on the responder side and therefore the

[PATCH 4.19 20/66] ASoC: stm32: dfsdm: fix debugfs warnings on entry creation

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit c47255b61129857b74b0d86eaf59335348be05e0 ] Register platform component with a prefix, to avoid warnings on debugfs entries creation, due to component name redundancy. Signed-off-by: Olivier Moysan Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

[PATCH 4.19 22/66] ASoC: dapm: Fix NULL pointer dereference in snd_soc_dapm_free_kcontrol

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit cacea3a90e211f0c111975535508d446a4a928d2 ] w_text_param can be NULL and it is being dereferenced without checking. Add the missing sanity check to prevent NULL pointer dereference. Signed-off-by: Pankaj Bharadiya Acked-by: Pierre-Louis Bossart Signed-off-by: Mark Brown

[PATCH 4.19 29/66] perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 583feb08e7f7ac9d533b446882eb3a54737a6dbb ] When an event is programmed with attr.wakeup_events=N (N>0), it means the caller is interested in getting a user level notification after N samples have been recorded in the kernel sampling buffer. With precise events on Intel

[PATCH 4.19 10/66] ASoC: stm32: sai: fix exposed capabilities in spdif mode

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit b8468192971807c43a80d6e2c41f83141cb7b211 ] Change capabilities exposed in SAI S/PDIF mode, to match actually supported formats. In S/PDIF mode only 32 bits stereo is supported. Signed-off-by: Olivier Moysan Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

[PATCH 4.19 09/66] ASoC: stm32: sai: fix iec958 controls indexation

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 5f8a1000c3e630c3ac06f1d664eeaa755bce8823 ] Allow indexation of sai iec958 controls according to device id. Signed-off-by: Olivier Moysan Signed-off-by: Mark Brown Signed-off-by: Sasha Levin --- sound/soc/stm/stm32_sai_sub.c | 7 --- 1 file changed, 4 insertions(+), 3

[PATCH 4.19 35/66] ASoC: cs35l35: Disable regulators on driver removal

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 47c4cc08cb5b34e93ab337b924c5ede77ca3c936 ] The chips main power supplies VA and VP are enabled during probe but then never disabled, this will cause warnings from the regulator framework on driver removal. Fix this by adding a remove callback and disabling the supplies, whilst

[PATCH 4.19 37/66] slab: fix a crash by reading /proc/slab_allocators

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit fcf88917dd435c6a4cb2830cb086ee58605a1d85 ] The commit 510ded33e075 ("slab: implement slab_root_caches list") changes the name of the list node within "struct kmem_cache" from "list" to "root_caches_node", but leaks_show() still use the "list" which causes a crash when reading

[PATCH 4.19 34/66] drm/amd/display: fix cursor black issue

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit c1cefe115d1cdc460014483319d440b2f0d07c68 ] [Why] the member sdr_white_level of struct dc_cursor_attributes was not initialized, then the random value result that dcn10_set_cursor_sdr_white_level() set error hw_scale value 0x20D9(normal value is 0x3c00), this cause the black

[PATCH 4.14 32/42] USB: serial: f81232: fix interrupt worker not stop

2019-05-09 Thread Greg Kroah-Hartman
From: Ji-Ze Hong (Peter Hong) commit 804dbee1e49774918339c1e5a87400988c0819e8 upstream. The F81232 will use interrupt worker to handle MSR change. This patch will fix the issue that interrupt work should stop in close() and suspend(). This also fixes line-status events being disabled after a

[PATCH 4.14 09/42] ASoC: samsung: odroid: Fix clock configuration for 44100 sample rate

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 2b13bee3884926cba22061efa75bd315e871de24 ] After commit fbeec965b8d1c ("ASoC: samsung: odroid: Fix 32000 sample rate handling") the audio root clock frequency is configured improperly for 44100 sample rate. Due to clock rate rounding it's 20070401 Hz instead of 22579000 Hz. This

[PATCH 4.19 03/66] Drivers: hv: vmbus: Remove the undesired put_cpu_ptr() in hv_synic_cleanup()

2019-05-09 Thread Greg Kroah-Hartman
From: Dexuan Cui commit a0033bd1eae4650b69be07c17cb87393da584563 upstream. With CONFIG_DEBUG_PREEMPT=y, the put_cpu_ptr() triggers an underflow warning in preempt_count_sub(). Fixes: 37cdd991fac8 ("vmbus: put related per-cpu variable together") Cc: sta...@vger.kernel.org Cc: Stephen Hemminger

[PATCH 4.14 30/42] genirq: Prevent use-after-free and work list corruption

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 59c39840f5abf4a71e1810a8da71aaccd6c17d26 ] When irq_set_affinity_notifier() replaces the notifier, then the reference count on the old notifier is dropped which causes it to be freed. But nothing ensures that the old notifier is not longer queued in the work list. If it is

[PATCH 4.14 38/42] Bluetooth: Align minimum encryption key size for LE and BR/EDR connections

2019-05-09 Thread Greg Kroah-Hartman
From: Marcel Holtmann commit d5bb334a8e171b262e48f378bd2096c0ea458265 upstream. The minimum encryption key size for LE connections is 56 bits and to align LE with BR/EDR, enforce 56 bits of minimum encryption key size for BR/EDR connections as well. Signed-off-by: Marcel Holtmann

[PATCH 4.19 06/66] staging: most: cdev: fix chrdev_region leak in mod_exit

2019-05-09 Thread Greg Kroah-Hartman
From: Suresh Udipi commit af708900e9a48c0aa46070c8a8cdf0608a1d2025 upstream. It looks like v4.18-rc1 commit [0] which upstreams mld-1.8.0 commit [1] missed to fix the memory leak in mod_exit function. Do it now. [0] aba258b7310167 ("staging: most: cdev: fix chrdev_region leak") [1]

[PATCH 4.14 29/42] iommu/amd: Set exclusion range correctly

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 3c677d206210f53a4be972211066c0f1cd47fe12 ] The exlcusion range limit register needs to contain the base-address of the last page that is part of the range, as bits 0-11 of this register are treated as 0xfff by the hardware for comparisons. So correctly set the exclusion range

[PATCH 4.19 18/66] clk: meson-gxbb: round the vdec dividers to closest

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 9b70c697e87286ade406e6a02091757307dd4b7c ] We want the video decoder clocks to always round to closest. While the muxes are already using CLK_MUX_ROUND_CLOSEST, the corresponding CLK_DIVIDER_ROUND_CLOSEST was forgotten for the dividers. Fix this by adding the flag to the two

[PATCH 4.14 39/42] UAS: fix alignment of scatter/gather segments

2019-05-09 Thread Greg Kroah-Hartman
From: Oliver Neukum commit 3ae62a42090f1ed48e2313ed256a1182a85fb575 upstream. This is the UAS version of 747668dbc061b3e62bc1982767a3a1f9815fcf0e usb-storage: Set virt_boundary_mask to avoid SG overflows We are not as likely to be vulnerable as storage, as it is unlikelier that UAS is run

[PATCH 4.14 36/42] scsi: qla2xxx: Fix incorrect region-size setting in optrom SYSFS routines

2019-05-09 Thread Greg Kroah-Hartman
From: Andrew Vasquez commit 5cbdae10bf11f96e30b4d14de7b08c8b490e903c upstream. Commit e6f77540c067 ("scsi: qla2xxx: Fix an integer overflow in sysfs code") incorrectly set 'optrom_region_size' to 'start+size', which can overflow option-rom boundaries when 'start' is non-zero. Continue setting

[PATCH 4.14 34/42] usb-storage: Set virt_boundary_mask to avoid SG overflows

2019-05-09 Thread Greg Kroah-Hartman
From: Alan Stern commit 747668dbc061b3e62bc1982767a3a1f9815fcf0e upstream. The USB subsystem has always had an unusual requirement for its scatter-gather transfers: Each element in the scatterlist (except the last one) must have a length divisible by the bulk maxpacket size. This is a

[PATCH 4.14 40/42] ASoC: Intel: avoid Oops if DMA setup fails

2019-05-09 Thread Greg Kroah-Hartman
From: Ross Zwisler commit 0efa3334d65b7f421ba12382dfa58f6ff5bf83c4 upstream. Currently in sst_dsp_new() if we get an error return from sst_dma_new() we just print an error message and then still complete the function successfully. This means that we are trying to run without sst->dma properly

[PATCH 4.19 02/66] scsi: libsas: fix a race condition when smp task timeout

2019-05-09 Thread Greg Kroah-Hartman
From: Jason Yan commit b90cd6f2b905905fb42671009dc0e27c310a16ae upstream. When the lldd is processing the complete sas task in interrupt and set the task stat as SAS_TASK_STATE_DONE, the smp timeout timer is able to be triggered at the same time. And smp_task_timedout() will complete the task

[PATCH 4.19 04/66] ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings

2019-05-09 Thread Greg Kroah-Hartman
From: Andrey Ryabinin commit f0996bc2978e02d2ea898101462b960f6119b18f upstream. Building lib/ubsan.c with gcc-9 results in a ton of nasty warnings like this one: lib/ubsan.c warning: conflicting types for built-in function ‘__ubsan_handle_negate_overflow’; expected ‘void(void *,

[PATCH 4.19 05/66] staging: greybus: power_supply: fix prop-descriptor request size

2019-05-09 Thread Greg Kroah-Hartman
From: Johan Hovold commit 47830c1127ef166af787caf2f871f23089610a7f upstream. Since moving the message buffers off the stack, the dynamically allocated get-prop-descriptor request buffer is incorrectly sized due to using the pointer rather than request-struct size when creating the operation.

[PATCH 4.14 42/42] arm64: futex: Bound number of LDXR/STXR loops in FUTEX_WAKE_OP

2019-05-09 Thread Greg Kroah-Hartman
From: Will Deacon commit 03110a5cb2161690ae5ac04994d47ed0cd6cef75 upstream. Our futex implementation makes use of LDXR/STXR loops to perform atomic updates to user memory from atomic context. This can lead to latency problems if we end up spinning around the LL/SC sequence at the expense of

[PATCH 4.19 07/66] ASoC: tlv320aic3x: fix reset gpio reference counting

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 82ad759143ed77673db0d93d53c1cde7b99917ee ] This patch fixes a bug that prevents freeing the reset gpio on unloading the module. aic3x_i2c_probe is called when loading the module and it calls list_add with a probably uninitialized list entry aic3x->list (next = prev = NULL)). So

[PATCH 4.14 41/42] locking/futex: Allow low-level atomic operations to return -EAGAIN

2019-05-09 Thread Greg Kroah-Hartman
From: Will Deacon commit 6b4f4bc9cb22875f97023984a625386f0c7cc1c0 upstream. Some futex() operations, including FUTEX_WAKE_OP, require the kernel to perform an atomic read-modify-write of the futex word via the userspace mapping. These operations are implemented by each architecture in

[PATCH 4.14 04/42] staging: greybus: power_supply: fix prop-descriptor request size

2019-05-09 Thread Greg Kroah-Hartman
From: Johan Hovold commit 47830c1127ef166af787caf2f871f23089610a7f upstream. Since moving the message buffers off the stack, the dynamically allocated get-prop-descriptor request buffer is incorrectly sized due to using the pointer rather than request-struct size when creating the operation.

[PATCH 4.14 06/42] ASoC:soc-pcm:fix a codec fixup issue in TDM case

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 570f18b6a8d1f0e60e8caf30e66161b6438dcc91 ] On HDaudio platforms, if playback is started when capture is working, there is no audible output. This can be root-caused to the use of the rx|tx_mask to store an HDaudio stream tag. If capture is stared before playback, rx_mask would

[PATCH 4.14 08/42] ASoC: nau8810: fix the issue of widget with prefixed name

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 54d1cf78b0f4ba348a7c7fb8b7d0708d71b6cc8a ] The driver changes the stream name of DAC and ADC to avoid the issue of widget with prefixed name. When the machine adds prefixed name for codec, the stream name of DAI may not find the widgets. Signed-off-by: John Hsu Signed-off-by:

[PATCH 4.14 03/42] ubsan: Fix nasty -Wbuiltin-declaration-mismatch GCC-9 warnings

2019-05-09 Thread Greg Kroah-Hartman
From: Andrey Ryabinin commit f0996bc2978e02d2ea898101462b960f6119b18f upstream. Building lib/ubsan.c with gcc-9 results in a ton of nasty warnings like this one: lib/ubsan.c warning: conflicting types for built-in function ‘__ubsan_handle_negate_overflow’; expected ‘void(void *,

[PATCH 4.14 26/42] ASoC: Intel: kbl: fix wrong number of channels

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit d6ba3f815bc5f3c4249d15c8bc5fbb012651b4a4 ] Fix wrong setting on number of channels. The context wants to set constraint to 2 channels instead of 4. Signed-off-by: Tzung-Bi Shih Acked-by: Pierre-Louis Bossart Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

[PATCH 4.14 07/42] ASoC: nau8824: fix the issue of the widget with prefix name

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 844a4a362dbec166b44d6b9b3dd45b08cb273703 ] The driver has two issues when machine add prefix name for codec. (1)The stream name of DAI can't find the AIF widgets. (2)The drivr can enable/disalbe the MICBIAS and SAR widgets. The patch will fix these issues caused by prefixed

[PATCH 4.14 27/42] virtio-blk: limit number of hw queues by nr_cpu_ids

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit bf348f9b78d413e75bb079462751a1d86b6de36c ] When tag_set->nr_maps is 1, the block layer limits the number of hw queues by nr_cpu_ids. No matter how many hw queues are used by virtio-blk, as it has (tag_set->nr_maps == 1), it can use at most nr_cpu_ids hw queues. In addition,

[PATCH 4.14 28/42] platform/x86: pmc_atom: Drop __initconst on dmi table

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit b995dcca7cf12f208cfd95fd9d5768dca7cccec7 ] It's used by probe and that isn't an init function. Drop this so that we don't get a section mismatch. Reported-by: kbuild test robot Cc: David Müller Cc: Hans de Goede Cc: Andy Shevchenko Fixes: 7c2e07130090 ("clk: x86: Add system

[PATCH 4.14 21/42] slab: fix a crash by reading /proc/slab_allocators

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit fcf88917dd435c6a4cb2830cb086ee58605a1d85 ] The commit 510ded33e075 ("slab: implement slab_root_caches list") changes the name of the list node within "struct kmem_cache" from "list" to "root_caches_node", but leaks_show() still use the "list" which causes a crash when reading

[PATCH 4.14 17/42] perf/x86/intel: Initialize TFA MSR

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit d7262457e35dbe239659e62654e56f8ddb814bed ] Stephane reported that the TFA MSR is not initialized by the kernel, but the TFA bit could set by firmware or as a leftover from a kexec, which makes the state inconsistent. Reported-by: Stephane Eranian Tested-by: Nelson DSouza

[PATCH 4.14 14/42] ASoC: tlv320aic32x4: Fix Common Pins

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit c63adb28f6d913310430f14c69f0a2ea55eed0cc ] The common pins were mistakenly not added to the DAPM graph. Adding these pins will allow valid graphs to be created. Signed-off-by: Annaliese McDermond Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

Re: [PATCH 02/25] tracing: Improve "if" macro code generation

2019-05-09 Thread Josh Poimboeuf
On Thu, May 09, 2019 at 02:29:02PM -0400, Steven Rostedt wrote: > On Thu, 9 May 2019 09:51:59 -0700 > Linus Torvalds wrote: > > > On Thu, May 9, 2019 at 6:01 AM Steven Rostedt wrote: > > > > > > This patch works. Can I get your Signed-off-by for it? > > > > Yes. Please write some kind of

[PATCH 4.14 20/42] ASoC: rockchip: pdm: fix regmap_ops hang issue

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit c85064435fe7a216ec0f0238ef2b8f7cd850a450 ] This is because set_fmt ops maybe called when PD is off, and in such case, regmap_ops will lead system hang. enale PD before doing regmap_ops. Signed-off-by: Sugar Zhang Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

[PATCH 4.14 10/42] ASoC: wm_adsp: Add locking to wm_adsp2_bus_error

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit a2225a6d155fcb247fe4c6d87f7c91807462966d ] Best to lock across handling the bus error to ensure the DSP doesn't change power state as we are reading the status registers. Signed-off-by: Charles Keepax Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

[PATCH 4.14 13/42] MIPS: KGDB: fix kgdb support for SMP platforms.

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit ab8a6d821179ab9bea1a9179f535ccba6330c1ed ] KGDB_call_nmi_hook is called by other cpu through smp call. MIPS smp call is processed in ipi irq handler and regs is saved in handle_int. So kgdb_call_nmi_hook get regs by get_irq_regs and regs will be passed to kgdb_cpu_enter.

[PATCH 4.9 07/28] IB/hfi1: Eliminate opcode tests on mr deref

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit a8639a79e85c18c16c10089edd589c7948f19bbd ] When an old ack_queue entry is used to store an incoming request, it may need to clean up the old entry if it is still referencing the MR. Originally only RDMA READ request needed to reference MR on the responder side and therefore the

[PATCH 4.9 25/28] Bluetooth: Align minimum encryption key size for LE and BR/EDR connections

2019-05-09 Thread Greg Kroah-Hartman
From: Marcel Holtmann commit d5bb334a8e171b262e48f378bd2096c0ea458265 upstream. The minimum encryption key size for LE connections is 56 bits and to align LE with BR/EDR, enforce 56 bits of minimum encryption key size for BR/EDR connections as well. Signed-off-by: Marcel Holtmann

[PATCH 4.9 27/28] ASoC: Intel: avoid Oops if DMA setup fails

2019-05-09 Thread Greg Kroah-Hartman
From: Ross Zwisler commit 0efa3334d65b7f421ba12382dfa58f6ff5bf83c4 upstream. Currently in sst_dsp_new() if we get an error return from sst_dma_new() we just print an error message and then still complete the function successfully. This means that we are trying to run without sst->dma properly

[PATCH 4.9 08/28] ASoC: tlv320aic32x4: Fix Common Pins

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit c63adb28f6d913310430f14c69f0a2ea55eed0cc ] The common pins were mistakenly not added to the DAPM graph. Adding these pins will allow valid graphs to be created. Signed-off-by: Annaliese McDermond Signed-off-by: Mark Brown Signed-off-by: Sasha Levin ---

[PATCH 4.9 04/28] ASoC:soc-pcm:fix a codec fixup issue in TDM case

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 570f18b6a8d1f0e60e8caf30e66161b6438dcc91 ] On HDaudio platforms, if playback is started when capture is working, there is no audible output. This can be root-caused to the use of the rx|tx_mask to store an HDaudio stream tag. If capture is stared before playback, rx_mask would

[PATCH 4.9 09/28] drm/mediatek: Fix an error code in mtk_hdmi_dt_parse_pdata()

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 2d85978341e6a32e7443d9f28639da254d53f400 ] We don't want to overwrite "ret", it already holds the correct error code. The "regmap" variable might be a valid pointer as this point. Fixes: 8f83f26891e1 ("drm/mediatek: Add HDMI support") Signed-off-by: Dan Carpenter

[PATCH 4.9 28/28] timer/debug: Change /proc/timer_stats from 0644 to 0600

2019-05-09 Thread Greg Kroah-Hartman
From: Ben Hutchings The timer_stats facility should filter and translate PIDs if opened from a non-initial PID namespace, to avoid leaking information about the wider system. It should also not show kernel virtual addresses. Unfortunately it has now been removed upstream (as redundant) instead

[PATCH 4.9 06/28] ASoC: cs4270: Set auto-increment bit for register writes

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit f0f2338a9cfaf71db895fa989ea7234e8a9b471d ] The CS4270 does not by default increment the register address on consecutive writes. During normal operation it doesn't matter as all register accesses are done individually. At resume time after suspend, however, the regcache code

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

2019-05-09 Thread Rob Landley
On 5/9/19 6:24 AM, Roberto Sassu wrote: > This patch set aims at solving the following use case: appraise files from > the initial ram disk. To do that, IMA checks the signature/hash from the > security.ima xattr. Unfortunately, this use case cannot be implemented > currently, as the CPIO format

Re: [RFC] simple_lmk: Introduce Simple Low Memory Killer for Android

2019-05-09 Thread Sultan Alsawaf
On Thu, May 09, 2019 at 05:56:46PM +0200, Oleg Nesterov wrote: > Impossible ;) I bet lockdep should report the deadlock as soon as > find_victims() > calls find_lock_task_mm() when you already have a locked victim. I hope you're not a betting man ;) With the following configured:

Re: [PATCH 2/5] ktest: cleanup get_grub_index

2019-05-09 Thread Masayoshi Mizuma
On Thu, May 09, 2019 at 01:57:21PM -0400, Steven Rostedt wrote: > On Thu, 9 May 2019 13:46:27 -0400 > Masayoshi Mizuma wrote: > > > From: Masayoshi Mizuma > > > > Cleanup get_grub_index(). > > Hi Masayoshi, > > Thanks for the patches, quick comment below. > > > > > Signed-off-by:

Re: [PATCH 2/4] x86/kprobes: Fix frame pointer annotations

2019-05-09 Thread Steven Rostedt
On Thu, 9 May 2019 20:26:22 +0200 Peter Zijlstra wrote: > Still, maybe we can wrap the thing in a .macro and reuse things that > way. Because I really hate there are at least 3 (x2 for x86_64) copies > of this around. I'm good with something like this. Have a single place that does the pt_regs

[PATCH 4.9 13/28] scsi: csiostor: fix missing data copy in csio_scsi_err_handler()

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 5c2442fd78998af60e13aba506d103f7f43f8701 ] If scsi cmd sglist is not suitable for DDP then csiostor driver uses preallocated buffers for DDP, because of this data copy is required from DDP buffer to scsi cmd sglist before calling ->scsi_done(). Signed-off-by: Varun Prakash

[PATCH 4.9 12/28] xtensa: fix initialization of pt_regs::syscall in start_thread

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 2663147dc7465cb29040a05cc4286fdd839978b5 ] New pt_regs should indicate that there's no syscall, not that there's syscall #0. While at it wrap macro body in do/while and parenthesize macro arguments. Signed-off-by: Max Filippov Signed-off-by: Sasha Levin ---

[PATCH 4.9 01/28] scsi: libsas: fix a race condition when smp task timeout

2019-05-09 Thread Greg Kroah-Hartman
From: Jason Yan commit b90cd6f2b905905fb42671009dc0e27c310a16ae upstream. When the lldd is processing the complete sas task in interrupt and set the task stat as SAS_TASK_STATE_DONE, the smp timeout timer is able to be triggered at the same time. And smp_task_timedout() will complete the task

[RFC 1/3] arm64: dts: qcom: sdm845-cheza: add initial cheza dt

2019-05-09 Thread Rob Clark
From: Rob Clark This is essentialy a squash of a bunch of history of cheza dt updates from chromium kernel, some of which were themselves squashes of history from older chromium kernels. I don't claim any credit other than wanting to more easily boot upstream kernel on cheza to have an easier

[RFC 2/3] arm64: dts: qcom: sdm845-cheza: Re-add reserved memory

2019-05-09 Thread Rob Clark
From: Douglas Anderson Let's fixup the reserved memory to re-add the things we deleted in ("CHROMIUM: arm64: dts: qcom: sdm845-cheza: Temporarily delete reserved-mem changes") in a way that plays nicely with the new upstream definitions. Signed-off-by: Douglas Anderson Reviewed-by: Stephen

[PATCH 4.9 10/28] perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit 583feb08e7f7ac9d533b446882eb3a54737a6dbb ] When an event is programmed with attr.wakeup_events=N (N>0), it means the caller is interested in getting a user level notification after N samples have been recorded in the kernel sampling buffer. With precise events on Intel

[PATCH 4.9 11/28] linux/kernel.h: Use parentheses around argument in u64_to_user_ptr()

2019-05-09 Thread Greg Kroah-Hartman
[ Upstream commit a0fe2c6479aab5723239b315ef1b552673f434a3 ] Use parentheses around uses of the argument in u64_to_user_ptr() to ensure that the cast doesn't apply to part of the argument. There are existing uses of the macro of the form u64_to_user_ptr(A + B) which expands to (void

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