Re: [PATCH v2 2/2] mwifiex: Make use of the new sdio_trigger_replug() API to reset

2019-07-24 Thread Kalle Valo
Doug Anderson writes: > Hi, > > On Wed, Jul 24, 2019 at 4:35 AM Kalle Valo wrote: >> >> Douglas Anderson wrote: >> >> > As described in the patch ("mmc: core: Add sdio_trigger_replug() >> > API"), the current mwifiex_sdio_card_reset() is broken in the cases >> > where we're running Bluetooth

Re: [PATCH v4 1/3] driver core: platform: Add an error message to platform_get_irq*()

2019-07-24 Thread Markus Elfring
… > +++ b/drivers/base/platform.c > @@ -99,12 +99,7 @@ void __iomem *devm_platform_ioremap_resource(struct > platform_device *pdev, … > -int platform_get_irq(struct platform_device *dev, unsigned int num) > +static int __platform_get_irq(struct platform_device *dev, unsigned int num) > { … I

[PATCH 4.19 110/271] ath10k: add missing error handling

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 4b553f3ca4cbde67399aa3a756c37eb92145b8a1 ] In function ath10k_sdio_mbox_rx_alloc() [sdio.c], ath10k_sdio_mbox_alloc_rx_pkt() is called without handling the error cases. This will make the driver think the allocation for skb is successful and try to access the skb. If we enable

[PATCH 4.19 105/271] rtlwifi: rtl8192cu: fix error handle when usb probe failed

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 6c0ed66f1a5b84e2a812c7c2d6571a5621bf3396 ] rtl_usb_probe() must do error handle rtl_deinit_core() only if rtl_init_core() is done, otherwise goto error_out2. | usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 | rtl_usb: reg 0xf0, usbctrl_vendorreq TimeOut!

Trabaja conmigo

2019-07-24 Thread lzz
Hola, Tenemos algunas finanzas en su nombre de familia amablemente Póngase en contacto conmigo aquí [(info.attltz...@gmail.com)] para más información. Saludos, Lutz

[PATCH 4.19 083/271] x86/cacheinfo: Fix a -Wtype-limits warning

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 1b7aebf0487613033aff26420e32fa2076d52846 ] cpuinfo_x86.x86_model is an unsigned type, so comparing against zero will generate a compilation warning: arch/x86/kernel/cpu/cacheinfo.c: In function 'cacheinfo_amd_init_llc_id': arch/x86/kernel/cpu/cacheinfo.c:662:19: warning:

[PATCH 4.19 119/271] ixgbe: Check DDM existence in transceiver before access

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 655c91414579d7bb115a4f7898ee726fc18e0984 ] Some transceivers may comply with SFF-8472 but not implement the Digital Diagnostic Monitoring (DDM) interface described in it. The existence of such area is specified by bit 6 of byte 92, set to 1 if implemented. Currently, due to not

[PATCH 4.19 081/271] vhost_net: disable zerocopy by default

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 098eadce3c622c07b328d0a43dda379b38cf7c5e ] Vhost_net was known to suffer from HOL[1] issues which is not easy to fix. Several downstream disable the feature by default. What's more, the datapath was split and datacopy path got the support of batching and XDP support recently

[PATCH 4.19 107/271] x86/build: Add set -e to mkcapflags.sh to delete broken capflags.c

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit bc53d3d777f81385c1bb08b07bd1c06450ecc2c1 ] Without 'set -e', shell scripts continue running even after any error occurs. The missed 'set -e' is a typical bug in shell scripting. For example, when a disk space shortage occurs while this script is running, it actually ends up

Re: WARNING in __mmdrop

2019-07-24 Thread Michael S. Tsirkin
On Tue, Jul 23, 2019 at 09:31:35PM +0800, Jason Wang wrote: > > On 2019/7/23 下午5:26, Michael S. Tsirkin wrote: > > On Tue, Jul 23, 2019 at 04:49:01PM +0800, Jason Wang wrote: > > > On 2019/7/23 下午4:10, Michael S. Tsirkin wrote: > > > > On Tue, Jul 23, 2019 at 03:53:06PM +0800, Jason Wang wrote: >

[PATCH 4.19 113/271] ASoC: Intel: hdac_hdmi: Set ops to NULL on remove

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 0f6ff78540bd1b4df1e0f17806b0ce2e1dff0d78 ] When we unload Skylake driver we may end up calling hdac_component_master_unbind(), it uses acomp->audio_ops, which we set in hdmi_codec_probe(), so we need to set it to NULL in hdmi_codec_remove(), otherwise we will dereference no

[PATCH 4.19 115/271] clocksource/drivers/exynos_mct: Increase priority over ARM arch timer

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 6282edb72bed5324352522d732080d4c1b9dfed6 ] Exynos SoCs based on CA7/CA15 have 2 timer interfaces: custom Exynos MCT (Multi Core Timer) and standard ARM Architected Timers. There are use cases, where both timer interfaces are used simultanously. One of such examples is using

[PATCH 4.19 134/271] iwlwifi: mvm: Drop large non sta frames

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit ac70499ee97231a418dc1a4d6c9dc102e8f64631 ] In some buggy scenarios we could possible attempt to transmit frames larger than maximum MSDU size. Since our devices don't know how to handle this, it may result in asserts, hangs etc. This can happen, for example, when we receive a

[PATCH 4.19 117/271] rslib: Fix decoding of shortened codes

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 2034a42d1747fc1e1eeef2c6f1789c4d0762cb9c ] The decoding of shortenend codes is broken. It only works as expected if there are no erasures. When decoding with erasures, Lambda (the error and erasure locator polynomial) is initialized from the given erasure positions. The pad

Re: [PATCH v2 0/1] mm/memory-failure: Poison read receives SIGKILL instead of SIGBUS issue

2019-07-24 Thread Jane Chu
On 7/24/2019 3:52 PM, Dan Williams wrote: On Wed, Jul 24, 2019 at 3:35 PM Jane Chu wrote: Changes in v2: - move 'tk' allocations internal to add_to_kill(), suggested by Dan; Oh, sorry if it wasn't clear, this should move to its own patch that only does the cleanup, and then the follow on

[PATCH 4.19 133/271] igb: clear out skb->tstamp after reading the txtime

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 1e08511d5d01884a3c9070afd52a47799312074a ] If a packet which is utilizing the launchtime feature (via SO_TXTIME socket option) also requests the hardware transmit timestamp, the hardware timestamp is not delivered to the userspace. This is because the value in skb->tstamp is

[PATCH 4.19 132/271] net: mvpp2: prs: Dont override the sign bit in SRAM parser shift

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 8ec3ede559956f8ad58db7b57d25ac724bab69e9 ] The Header Parser allows identifying various fields in the packet headers, used for various kind of filtering and classification steps. This is a re-entrant process, where the offset in the packet header depends on the previous lookup

[PATCH 4.19 078/271] perf/x86/intel/uncore: Handle invalid event coding for free-running counter

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 543ac280b3576c0009e8c0fcd4d6bfc9978d7bd0 ] Counting with invalid event coding for free-running counter may cause OOPs, e.g. uncore_iio_free_running_0/event=1/. Current code only validate the event with free-running event format, event=0xff,umask=0xXY. Non-free-running event

Re: [PATCH 1/3] iio: imu: st_lsm6sdx: move some register definitions to sensor_settings struct

2019-07-24 Thread Martin Kepplinger
On 15.07.19 15:19, Martin Kepplinger wrote: > Move some register definitions to the per-device array of struct > st_lsm6dsx_sensor_settings in order to simplify adding new sensor > devices to the driver. > > Also, remove completely unused register definitions. > > Signed-off-by: Martin

[PATCH 4.19 123/271] EDAC: Fix global-out-of-bounds write when setting edac_mc_poll_msec

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit d8655e7630dafa88bc37f101640e39c736399771 ] Commit 9da21b1509d8 ("EDAC: Poll timeout cannot be zero, p2") assumes edac_mc_poll_msec to be unsigned long, but the type of the variable still remained as int. Setting edac_mc_poll_msec can trigger out-of-bounds write. Reproducer:

[PATCH 4.19 138/271] bnx2x: Prevent ptp_task to be rescheduled indefinitely

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 3c91f25c2f72ba6001775a5932857c1d2131c531 ] Currently bnx2x ptp worker tries to read a register with timestamp information in case of TX packet timestamping and in case it fails, the routine reschedules itself indefinitely. This was reported as a kworker always at 100% of CPU

[PATCH 4.19 137/271] perf stat: Fix group lookup for metric group

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 2f87f33f4226523df9c9cc28f9874ea02fcc3d3f ] The metric group code tries to find a group it added earlier in the evlist. Fix the lookup to handle groups with partially overlaps correctly. When a sub string match fails and we reset the match, we have to compare the first element

[PATCH 4.19 125/271] bcache: check CACHE_SET_IO_DISABLE bit in bch_journal()

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 383ff2183ad16a8842d1fbd9dd3e1cbd66813e64 ] When too many I/O errors happen on cache set and CACHE_SET_IO_DISABLE bit is set, bch_journal() may continue to work because the journaling bkey might be still in write set yet. The caller of bch_journal() may believe the journal still

[PATCH 4.19 143/271] bonding: validate ip header before check IPPROTO_IGMP

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 9d1bc24b52fb8c5d859f9a47084bf1179470e04c ] bond_xmit_roundrobin() checks for IGMP packets but it parses the IP header even before checking skb->protocol. We should validate the IP header with pskb_may_pull() before using iph->protocol. Reported-and-tested-by:

[PATCH 4.19 148/271] Bluetooth: Add new 13d3:3501 QCA_ROME device

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 881cec4f6b4da78e54b73c046a60f39315964c7d ] Without the QCA ROME setup routine this adapter fails to establish a SCO connection. T: Bus=01 Lev=01 Prnt=01 Port=04 Cnt=01 Dev#= 2 Spd=12 MxCh= 0 D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 P: Vendor=13d3

[PATCH 4.19 177/271] crypto: crypto4xx - fix AES CTR blocksize value

2019-07-24 Thread Greg Kroah-Hartman
From: Christian Lamparter commit bfa2ba7d9e6b20aca82b99e6842fe18842ae3a0f upstream. This patch fixes a issue with crypto4xx's ctr(aes) that was discovered by libcapi's kcapi-enc-test.sh test. The some of the ctr(aes) encryptions test were failing on the non-power-of-two test: kcapi-enc -

[PATCH 4.19 145/271] tools: bpftool: Fix json dump crash on powerpc

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit aa52bcbe0e72fac36b1862db08b9c09c4caefae3 ] Michael reported crash with by bpf program in json mode on powerpc: # bpftool prog -p dump jited id 14 [{ "name": "0xda9aa760", "insns": [{ "pc": "0x0", "operation": "nop",

[PATCH 4.19 127/271] bcache: check c->gc_thread by IS_ERR_OR_NULL in cache_set_flush()

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit b387e9b58679c60f5b1e4313939bd4878204fc37 ] When system memory is in heavy pressure, bch_gc_thread_start() from run_cache_set() may fail due to out of memory. In such condition, c->gc_thread is assigned to -ENOMEM, not NULL pointer. Then in following failure code path

[PATCH 4.19 154/271] gtp: fix suspicious RCU usage

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit e198987e7dd7d3645a53875151cd6f8fc425b706 ] gtp_encap_enable_socket() and gtp_encap_destroy() are not protected by rcu_read_lock(). and it's not safe to write sk->sk_user_data. This patch make these functions to use lock_sock() instead of rcu_dereference_sk_user_data(). Test

[PATCH 4.19 156/271] gtp: fix use-after-free in gtp_encap_destroy()

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 1788b8569f5de27da09087fa3f6580d2aa04cc75 ] gtp_encap_destroy() is called twice. 1. When interface is deleted. 2. When udp socket is destroyed. either gtp->sk0 or gtp->sk1u could be freed by sock_put() in gtp_encap_destroy(). so, when gtp_encap_destroy() is called again, it would

[PATCH 4.19 167/271] Revert "scsi: ncr5380: Increase register polling limit"

2019-07-24 Thread Greg Kroah-Hartman
From: Finn Thain commit 25fcf94a2fa89dd3e73e965ebb0b38a2a4f72aa4 upstream. This reverts commit 4822827a69d7cd3bc5a07b7637484ebd2cf88db6. The purpose of that commit was to suppress a timeout warning message which appeared to be caused by target latency. But suppressing the warning is

[PATCH 4.19 149/271] Bluetooth: 6lowpan: search for destination address in all peers

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit b188b03270b7f8568fc714101ce82fbf5e811c5a ] Handle overlooked case where the target address is assigned to a peer and neither route nor gateway exist. For one peer, no checks are performed to see if it is meant to receive packets for a given address. As soon as there is a

[PATCH 4.19 126/271] bcache: acquire bch_register_lock later in cached_dev_free()

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 80265d8dfd77792e133793cef44a21323aac2908 ] When enable lockdep engine, a lockdep warning can be observed when reboot or shutdown system, [ 3142.764557][T1] bcache: bcache_reboot() Stopping all devices: [ 3142.776265][ T2649] [ 3142.777159][ T2649]

[PATCH 4.19 189/271] Input: gtco - bounds check collection indent level

2019-07-24 Thread Greg Kroah-Hartman
From: Grant Hernandez commit 2a017fd82c5402b3c8df5e3d6e5165d9e6147dc1 upstream. The GTCO tablet input driver configures itself from an HID report sent via USB during the initial enumeration process. Some debugging messages are generated during the parsing. A debugging message indentation

[PATCH 4.19 187/271] bcache: fix mistaken sysfs entry for io_error counter

2019-07-24 Thread Greg Kroah-Hartman
From: Coly Li commit 5461999848e0462c14f306a62923d22de820a59c upstream. In bch_cached_dev_files[] from driver/md/bcache/sysfs.c, sysfs_errors is incorrectly inserted in. The correct entry should be sysfs_io_errors. This patch fixes the problem and now I/O errors of cached device can be read

[PATCH 4.19 192/271] Input: alps - fix a mismatch between a condition check and its comment

2019-07-24 Thread Greg Kroah-Hartman
From: Hui Wang commit 771a081e44a9baa1991ef011cc453ef425591740 upstream. In the function alps_is_cs19_trackpoint(), we check if the param[1] is in the 0x20~0x2f range, but the code we wrote for this checking is not correct: (param[1] & 0x20) does not mean param[1] is in the range of 0x20~0x2f,

[PATCH 4.19 186/271] bcache: ignore read-ahead request failure on backing device

2019-07-24 Thread Greg Kroah-Hartman
From: Coly Li commit 578df99b1b0531d19af956530fe4da63d01a1604 upstream. When md raid device (e.g. raid456) is used as backing device, read-ahead requests on a degrading and recovering md raid device might be failured immediately by md raid code, but indeed this md raid array can still be read

[PATCH 4.19 180/271] crypto: ccp - memset structure fields to zero before reuse

2019-07-24 Thread Greg Kroah-Hartman
From: Hook, Gary commit 20e833dc36355ed642d00067641a679c618303fa upstream. The AES GCM function reuses an 'op' data structure, which members contain values that must be cleared for each (re)use. This fix resolves a crypto self-test failure: alg: aead: gcm-aes-ccp encryption test failed (wrong

[PATCH 4.19 196/271] iwlwifi: pcie: fix ALIVE interrupt handling for gen2 devices w/o MSI-X

2019-07-24 Thread Greg Kroah-Hartman
From: Emmanuel Grumbach commit ec46ae30245ecb41d73f8254613db07c653fb498 upstream. We added code to restock the buffer upon ALIVE interrupt when MSI-X is disabled. This was added as part of the context info code. This code was added only if the ISR debug level is set which is very unlikely to be

Re: [PATCH 1/4] mailbox: arm_mhuv2: add device tree binding documentation

2019-07-24 Thread Jassi Brar
On Sun, Jul 21, 2019 at 4:58 PM Jassi Brar wrote: > > On Wed, Jul 17, 2019 at 2:26 PM Tushar Khandelwal > wrote: > > > diff --git a/Documentation/devicetree/bindings/mailbox/arm,mhuv2.txt > > b/Documentation/devicetree/bindings/mailbox/arm,mhuv2.txt > > new file mode 100644 > > index

[PATCH 4.19 197/271] iwlwifi: dont WARN when calling iwl_get_shared_mem_conf with RF-Kill

2019-07-24 Thread Greg Kroah-Hartman
From: Emmanuel Grumbach commit 0d53cfd0cca3c729a089c39eef0e7d8ae7662974 upstream. iwl_mvm_send_cmd returns 0 when the command won't be sent because RF-Kill is asserted. Do the same when we call iwl_get_shared_mem_conf since it is not sent through iwl_mvm_send_cmd but directly calls the

[PATCH 4.19 202/271] pnfs: Fix a problem where we gratuitously start doing I/O through the MDS

2019-07-24 Thread Greg Kroah-Hartman
From: Trond Myklebust commit 58bbeab425c6c5e318f5b6ae31d351331ddfb34b upstream. If the client has to stop in pnfs_update_layout() to wait for another layoutget to complete, it currently exits and defaults to I/O through the MDS if the layoutget was successful. Fixes: d03360aaf5cc ("pNFS:

[PATCH 4.19 200/271] pnfs/flexfiles: Fix PTR_ERR() dereferences in ff_layout_track_ds_error

2019-07-24 Thread Greg Kroah-Hartman
From: Trond Myklebust commit 8e04fdfadda75a849c649f7e50fe7d97772e1fcb upstream. mirror->mirror_ds can be NULL if uninitialised, but can contain a PTR_ERR() if call to GETDEVICEINFO failed. Fixes: 65990d1afbd2 ("pNFS/flexfiles: Fix a deadlock on LAYOUTGET") Signed-off-by: Trond Myklebust Cc:

[PATCH 4.19 223/271] x86/boot: Fix memory leak in default_get_smp_config()

2019-07-24 Thread Greg Kroah-Hartman
From: David Rientjes commit e74bd96989dd42a51a73eddb4a5510a6f5e42ac3 upstream. When default_get_smp_config() is called with early == 1 and mpf->feature1 is non-zero, mpf is leaked because the return path does not do early_memunmap(). Fix this and share a common exit routine. Fixes:

[PATCH 4.19 203/271] lib/scatterlist: Fix mapping iterator when sg->offset is greater than PAGE_SIZE

2019-07-24 Thread Greg Kroah-Hartman
From: Christophe Leroy commit aeb87246537a83c2aff482f3f34a2e0991e02cbc upstream. All mapping iterator logic is based on the assumption that sg->offset is always lower than PAGE_SIZE. But there are situations where sg->offset is such that the SG item is on the second page. In that case

[PATCH 4.19 206/271] ALSA: seq: Break too long mutex context in the write loop

2019-07-24 Thread Greg Kroah-Hartman
From: Takashi Iwai commit ede34f397ddb063b145b9e7d79c6026f819ded13 upstream. The fix for the racy writes and ioctls to sequencer widened the application of client->ioctl_mutex to the whole write loop. Although it does unlock/relock for the lengthy operation like the event dup, the loop keeps

[PATCH 4.19 210/271] media: coda: Remove unbalanced and unneeded mutex unlock

2019-07-24 Thread Greg Kroah-Hartman
From: Ezequiel Garcia commit 766b9b168f6c75c350dd87c3e0bc6a9b322f0013 upstream. The mutex unlock in the threaded interrupt handler is not paired with any mutex lock. Remove it. This bug has been here for a really long time, so it applies to any stable repo. Reviewed-by: Philipp Zabel

[PATCH 4.19 175/271] crypto: arm64/sha2-ce - correct digest for empty data in finup

2019-07-24 Thread Greg Kroah-Hartman
From: Elena Petrova commit 6bd934de1e393466b319d29c4427598fda096c57 upstream. The sha256-ce finup implementation for ARM64 produces wrong digest for empty input (len=0). Expected: the actual digest, result: initial value of SHA internal state. The error is in sha256_ce_finup: for empty data

[PATCH 4.19 219/271] dm zoned: fix zone state management race

2019-07-24 Thread Greg Kroah-Hartman
From: Damien Le Moal commit 3b8cafdd5436f9298b3bf6eb831df5eef5ee82b6 upstream. dm-zoned uses the zone flag DMZ_ACTIVE to indicate that a zone of the backend device is being actively read or written and so cannot be reclaimed. This flag is set as long as the zone atomic reference counter is not

[PATCH 4.19 173/271] crypto: ccp - Validate the the error value used to index error messages

2019-07-24 Thread Greg Kroah-Hartman
From: Hook, Gary commit 52393d617af7b554f03531e6756facf2ea687d2e upstream. The error code read from the queue status register is only 6 bits wide, but we need to verify its value is within range before indexing the error messages. Fixes: 81422badb3907 ("crypto: ccp - Make syslog errors

[PATCH 4.19 166/271] scsi: NCR5380: Always re-enable reselection interrupt

2019-07-24 Thread Greg Kroah-Hartman
From: Finn Thain commit 57f31326518e98ee4cabf9a04efe00ed57c54147 upstream. The reselection interrupt gets disabled during selection and must be re-enabled when hostdata->connected becomes NULL. If it isn't re-enabled a disconnected command may time-out or the target may wedge the bus while

[PATCH 4.19 238/271] HID: wacom: correct touch resolution x/y typo

2019-07-24 Thread Greg Kroah-Hartman
From: Aaron Armstrong Skomra commit 68c20cc2164cc5c7c73f8012ae6491afdb1f7f72 upstream. This affects the 2nd-gen Intuos Pro Medium and Large when using their Bluetooth connection. Fixes: 4922cd26f03c ("HID: wacom: Support 2nd-gen Intuos Pro's Bluetooth classic interface") Cc: # v4.11+

[PATCH 4.19 227/271] drm/edid: parse CEA blocks embedded in DisplayID

2019-07-24 Thread Greg Kroah-Hartman
From: Andres Rodriguez commit e28ad544f462231d3fd081a7316339359efbb481 upstream. DisplayID blocks allow embedding of CEA blocks. The payloads are identical to traditional top level CEA extension blocks, but the header is slightly different. This change allows the CEA parser to find a CEA block

[PATCH 4.19 226/271] perf/x86/amd/uncore: Set the thread mask for F17h L3 PMCs

2019-07-24 Thread Greg Kroah-Hartman
From: Kim Phillips commit 2f217d58a8a086d3399fecce39fb358848e799c4 upstream. Fill in the L3 performance event select register ThreadMask bitfield, to enable per hardware thread accounting. Signed-off-by: Kim Phillips Signed-off-by: Peter Zijlstra (Intel) Cc: Cc: Alexander Shishkin Cc:

Re: [PATCH REBASE v4 05/14] arm64, mm: Make randomization selected by generic topdown mmap layout

2019-07-24 Thread Alexandre Ghiti
On 7/24/19 7:11 PM, Luis Chamberlain wrote: On Wed, Jul 24, 2019 at 01:58:41AM -0400, Alexandre Ghiti wrote: diff --git a/mm/util.c b/mm/util.c index 0781e5575cb3..16f1e56e2996 100644 --- a/mm/util.c +++ b/mm/util.c @@ -321,7 +321,15 @@ unsigned long randomize_stack_top(unsigned long stack_top)

[PATCH 4.19 217/271] drm/nouveau/i2c: Enable i2c pads & busses during preinit

2019-07-24 Thread Greg Kroah-Hartman
From: Lyude Paul commit 7cb95eeea6706c790571042a06782e378b2561ea upstream. It turns out that while disabling i2c bus access from software when the GPU is suspended was a step in the right direction with: commit 342406e4fbba ("drm/nouveau/i2c: Disable i2c bus access after ->fini()") We also

[PATCH 4.19 218/271] padata: use smp_mb in padata_reorder to avoid orphaned padata jobs

2019-07-24 Thread Greg Kroah-Hartman
From: Daniel Jordan commit cf144f81a99d1a3928f90b0936accfd3f45c9a0a upstream. Testing padata with the tcrypt module on a 5.2 kernel... # modprobe tcrypt alg="pcrypt(rfc4106(gcm(aes)))" type=3 # modprobe tcrypt mode=211 sec=1 ...produces this splat: INFO: task modprobe:10075

[PATCH 4.19 254/271] parisc: Fix kernel panic due invalid values in IAOQ0 or IAOQ1

2019-07-24 Thread Greg Kroah-Hartman
From: Helge Deller commit 10835c854685393a921b68f529bf740fa7c9984d upstream. On parisc the privilege level of a process is stored in the lowest two bits of the instruction pointers (IAOQ0 and IAOQ1). On Linux we use privilege level 0 for the kernel and privilege level 3 for user-space. So

[PATCH 4.19 263/271] intel_th: msu: Fix single mode with disabled IOMMU

2019-07-24 Thread Greg Kroah-Hartman
From: Alexander Shishkin commit 918b8646497b5dba6ae82d4a7325f01b258972b9 upstream. Commit 4e0eaf239fb3 ("intel_th: msu: Fix single mode with IOMMU") switched the single mode code to use dma mapping pages obtained from the page allocator, but with IOMMU disabled, that may lead to using SWIOTLB

[PATCH 4.19 264/271] Bluetooth: Add SMP workaround Microsoft Surface Precision Mouse bug

2019-07-24 Thread Greg Kroah-Hartman
From: Szymon Janc commit 1d87b88ba26eabd4745e158ecfd87c93a9b51dc2 upstream. Microsoft Surface Precision Mouse provides bogus identity address when pairing. It connects with Static Random address but provides Public Address in SMP Identity Address Information PDU. Address has same value but type

[PATCH 4.19 266/271] blk-throttle: fix zero wait time for iops throttled group

2019-07-24 Thread Greg Kroah-Hartman
From: Konstantin Khlebnikov commit 3a10f999ffd464d01c5a05592a15470a3c4bbc36 upstream. After commit 991f61fe7e1d ("Blk-throttle: reduce tail io latency when iops limit is enforced") wait time could be zero even if group is throttled and cannot issue requests right now. As a result

[PATCH 4.19 216/271] kconfig: fix missing choice values in auto.conf

2019-07-24 Thread Greg Kroah-Hartman
From: Masahiro Yamada commit 8e2442a5f86e1f77b86401fce274a7f622740bc4 upstream. Since commit 00c864f8903d ("kconfig: allow all config targets to write auto.conf if missing"), Kconfig creates include/config/auto.conf in the defconfig stage when it is missing. Joonas Kylmälä reported incorrect

[PATCH 4.19 240/271] coda: pass the host file in vma->vm_file on mmap

2019-07-24 Thread Greg Kroah-Hartman
From: Jan Harkes commit 7fa0a1da3dadfd9216df7745a1331fdaa0940d1c upstream. Patch series "Coda updates". The following patch series is a collection of various fixes for Coda, most of which were collected from linux-fsdevel or linux-kernel but which have as yet not found their way upstream.

[PATCH 4.19 246/271] xfs: dont ever put nlink > 0 inodes on the unlinked list

2019-07-24 Thread Greg Kroah-Hartman
commit c4a6bf7f6cc7eb4cce120fb7eb1e1fb8b2d65e09 upstream. When XFS creates an O_TMPFILE file, the inode is created with nlink = 1, put on the unlinked list, and then the VFS sets nlink = 0 in d_tmpfile. If we crash before anything logs the inode (it's dirty incore but the vfs doesn't tell us it's

[PATCH 4.19 212/271] media: videobuf2-dma-sg: Prevent size from overflowing

2019-07-24 Thread Greg Kroah-Hartman
From: Sakari Ailus commit 14f28f5cea9e3998442de87846d1907a531b6748 upstream. buf->size is an unsigned long; casting that to int will lead to an overflow if buf->size exceeds INT_MAX. Fix this by changing the type to unsigned long instead. This is possible as the buf->size is always aligned to

Re: [PATCH v10 3/5] overlayfs: add __get xattr method

2019-07-24 Thread Amir Goldstein
On Wed, Jul 24, 2019 at 10:57 PM Mark Salyzyn wrote: > > Because of the overlayfs getxattr recursion, the incoming inode fails > to update the selinux sid resulting in avc denials being reported > against a target context of u:object_r:unlabeled:s0. This description is too brief for me to

[PATCH 4.19 241/271] include/asm-generic/bug.h: fix "cut here" for WARN_ON for __WARN_TAINT architectures

2019-07-24 Thread Greg Kroah-Hartman
From: Drew Davenport commit 6b15f678fb7d5ef54e089e6ace72f007fe6e9895 upstream. For architectures using __WARN_TAINT, the WARN_ON macro did not print out the "cut here" string. The other WARN_XXX macros would print "cut here" inside __warn_printk, which is not called for WARN_ON since it

[PATCH 4.19 242/271] xfs: fix pagecache truncation prior to reflink

2019-07-24 Thread Greg Kroah-Hartman
commit 4918ef4ea008cd2ff47eb852894e3f9b9047f4f3 upstream. Prior to remapping blocks, it is necessary to remove pages from the destination file's page cache. Unfortunately, the truncation is not aggressive enough -- if page size > block size, we'll end up zeroing subpage blocks instead of

[PATCH 4.19 269/271] net: mvmdio: allow up to four clocks to be specified for orion-mdio

2019-07-24 Thread Greg Kroah-Hartman
From: Josua Mayer commit 4aabed699c400810981d3dda170f05fa4d782905 upstream. Allow up to four clocks to be specified and enabled for the orion-mdio interface, which are required by the Armada 8k and defined in armada-cp110.dtsi. Fixes a hang in probing the mvmdio driver that was encountered on

Re: [PATCH v2 1/1] mm/memory-failure: Poison read receives SIGKILL instead of SIGBUS if mmaped more than once

2019-07-24 Thread Jane Chu
On 7/24/2019 4:43 PM, Naoya Horiguchi wrote: On Wed, Jul 24, 2019 at 04:33:23PM -0600, Jane Chu wrote: Mmap /dev/dax more than once, then read the poison location using address from one of the mappings. The other mappings due to not having the page mapped in will cause SIGKILLs delivered to

[PATCH 4.19 253/271] parisc: Ensure userspace privilege for ptraced processes in regset functions

2019-07-24 Thread Greg Kroah-Hartman
From: Helge Deller commit 34c32fc603311a72cb558e5e337555434f64c27b upstream. On parisc the privilege level of a process is stored in the lowest two bits of the instruction pointers (IAOQ0 and IAOQ1). On Linux we use privilege level 0 for the kernel and privilege level 3 for user-space. So

[PATCH 4.19 255/271] powerpc/32s: fix suspend/resume when IBATs 4-7 are used

2019-07-24 Thread Greg Kroah-Hartman
From: Christophe Leroy commit 6ecb78ef56e08d2119d337ae23cb951a640dc52d upstream. Previously, only IBAT1 and IBAT2 were used to map kernel linear mem. Since commit 63b2bc619565 ("powerpc/mm/32s: Use BATs for STRICT_KERNEL_RWX"), we may have all 8 BATs used for mapping kernel text. But the

[PATCH 4.19 259/271] mmc: sdhci-msm: fix mutex while in spinlock

2019-07-24 Thread Greg Kroah-Hartman
From: Jorge Ramirez-Ortiz commit 5e6b6651d22de109ebf48ca00d0373bc2c0cc080 upstream. mutexes can sleep and therefore should not be taken while holding a spinlock. move clk_get_rate (can sleep) outside the spinlock protected region. Fixes: 83736352e0ca ("mmc: sdhci-msm: Update DLL reset

[PATCH 4.19 258/271] powerpc/pseries: Fix oops in hotplug memory notifier

2019-07-24 Thread Greg Kroah-Hartman
From: Nathan Lynch commit 0aa82c482ab2ece530a6f44897b63b274bb43c8e upstream. During post-migration device tree updates, we can oops in pseries_update_drconf_memory() if the source device tree has an ibm,dynamic-memory-v2 property and the destination has a ibm,dynamic_memory (v1) property. The

[PATCH 4.19 271/271] dm bufio: fix deadlock with loop device

2019-07-24 Thread Greg Kroah-Hartman
From: Junxiao Bi commit bd293d071ffe65e645b4d8104f9d8fe15ea13862 upstream. When thin-volume is built on loop device, if available memory is low, the following deadlock can be triggered: One process P1 allocates memory with GFP_FS flag, direct alloc fails, memory reclaim invokes memory shrinker

[PATCH 4.19 270/271] dt-bindings: allow up to four clocks for orion-mdio

2019-07-24 Thread Greg Kroah-Hartman
From: Josua Mayer commit 80785f5a22e9073e2ded5958feb7f220e066d17b upstream. Armada 8040 needs four clocks to be enabled for MDIO accesses to work. Update the binding to allow the extra clock to be specified. Cc: sta...@vger.kernel.org Fixes: 6d6a331f44a1 ("dt-bindings: allow up to three clocks

[PATCH 4.19 257/271] powerpc/powernv/npu: Fix reference leak

2019-07-24 Thread Greg Kroah-Hartman
From: Greg Kurz commit 02c5f5394918b9b47ff4357b1b18335768cd867d upstream. Since 902bdc57451c, get_pci_dev() calls pci_get_domain_bus_and_slot(). This has the effect of incrementing the reference count of the PCI device, as explained in drivers/pci/search.c: * Given a PCI domain, bus, and

[PATCH 4.19 268/271] blkcg: update blkcg_print_stat() to handle larger outputs

2019-07-24 Thread Greg Kroah-Hartman
From: Tejun Heo commit f539da82f2158916e154d206054e0efd5df7ab61 upstream. Depending on the number of devices, blkcg stats can go over the default seqfile buf size. seqfile normally retries with a larger buffer but since the ->pd_stat() addition, blkcg_print_stat() doesn't tell seqfile that

[PATCH 4.19 256/271] powerpc/watchpoint: Restore NV GPRs while returning from exception

2019-07-24 Thread Greg Kroah-Hartman
From: Ravi Bangoria commit f474c28fbcbe42faca4eb415172c07d76adcb819 upstream. powerpc hardware triggers watchpoint before executing the instruction. To make trigger-after-execute behavior, kernel emulates the instruction. If the instruction is 'load something into non-volatile register',

[PATCH 4.19 261/271] mtd: rawnand: mtk: Correct low level time calculation of r/w cycle

2019-07-24 Thread Greg Kroah-Hartman
From: Xiaolei Li commit e1884ffddacc0424d7e785e6f8087bd12f7196db upstream. At present, the flow of calculating AC timing of read/write cycle in SDR mode is that: At first, calculate high hold time which is valid for both read and write cycle using the max value between tREH_min and tWH_min.

[PATCH 4.19 267/271] blk-iolatency: clear use_delay when io.latency is set to zero

2019-07-24 Thread Greg Kroah-Hartman
From: Tejun Heo commit 5de0073fcd50cc1f150895a7bb04d3cf8067b1d7 upstream. If use_delay was non-zero when the latency target of a cgroup was set to zero, it will stay stuck until io.latency is enabled on the cgroup again. This keeps readahead disabled for the cgroup impacting performance

[PATCH 4.19 260/271] eCryptfs: fix a couple type promotion bugs

2019-07-24 Thread Greg Kroah-Hartman
From: Dan Carpenter commit 0bdf8a8245fdea6f075a5fede833a5fcf1b3466c upstream. ECRYPTFS_SIZE_AND_MARKER_BYTES is type size_t, so if "rc" is negative that gets type promoted to a high positive value and treated as success. Fixes: 778aeb42a708 ("eCryptfs: Cleanup and optimize

[PATCH 4.19 262/271] mtd: spinand: read returns badly if the last page has bitflips

2019-07-24 Thread Greg Kroah-Hartman
From: liaoweixiong commit b83408b580eccf8d2797cd6cb9ae42c2a28656a7 upstream. In case of the last page containing bitflips (ret > 0), spinand_mtd_read() will return that number of bitflips for the last page while it should instead return max_bitflips like it does when the last page read returns

[PATCH 4.19 250/271] xfs: abort unaligned nowait directio early

2019-07-24 Thread Greg Kroah-Hartman
commit 1fdeaea4d92c69fb9f871a787af6ad00f32eeea7 upstream. Dave Chinner noticed that xfs_file_dio_aio_write returns EAGAIN without dropping the IOLOCK when its deciding not to wait, which means that we leak the IOLOCK there. Since we now make unaligned directio always wait, we have the

[PATCH 4.19 248/271] xfs: fix reporting supported extra file attributes for statx()

2019-07-24 Thread Greg Kroah-Hartman
commit 1b9598c8fb9965fff901c4caa21fed9644c34df3 upstream. statx(2) notes that any attribute that is not indicated as supported by stx_attributes_mask has no usable value. Commit 5f955f26f3d42d ("xfs: report crtime and attribute flags to statx") added support for informing userspace of extra file

[PATCH 4.19 251/271] gpu: ipu-v3: ipu-ic: Fix saturation bit offset in TPMEM

2019-07-24 Thread Greg Kroah-Hartman
From: Steve Longerbeam commit 3d1f62c686acdedf5ed9642b763f3808d6a47d1e upstream. The saturation bit was being set at bit 9 in the second 32-bit word of the TPMEM CSC. This isn't correct, the saturation bit is bit 42, which is bit 10 of the second word. Fixes: 1aa8ea0d2bd5d ("gpu: ipu-v3: Add

[PATCH 4.19 249/271] xfs: serialize unaligned dio writes against all other dio writes

2019-07-24 Thread Greg Kroah-Hartman
commit 2032a8a27b5cc0f578d37fa16fa2494b80a0d00a upstream. XFS applies more strict serialization constraints to unaligned direct writes to accommodate things like direct I/O layer zeroing, unwritten extent conversion, etc. Unaligned submissions acquire the exclusive iolock and wait for in-flight

[PATCH 4.19 213/271] KVM: x86/vPMU: refine kvm_pmu err msg when event creation failed

2019-07-24 Thread Greg Kroah-Hartman
From: Like Xu commit 6fc3977ccc5d3c22e851f2dce2d3ce2a0a843842 upstream. If a perf_event creation fails due to any reason of the host perf subsystem, it has no chance to log the corresponding event for guest which may cause abnormal sampling data in guest result. In debug mode, this message

[PATCH 4.19 252/271] crypto: caam - limit output IV to CBC to work around CTR mode DMA issue

2019-07-24 Thread Greg Kroah-Hartman
From: Ard Biesheuvel commit ed527b13d800dd515a9e6c582f0a73eca65b2e1b upstream. The CAAM driver currently violates an undocumented and slightly controversial requirement imposed by the crypto stack that a buffer referred to by the request structure via its virtual address may not be modified

[PATCH 4.19 214/271] arm64: tegra: Fix AGIC register range

2019-07-24 Thread Greg Kroah-Hartman
From: Jon Hunter commit ba24eee6686f6ed3738602b54d959253316a9541 upstream. The Tegra AGIC interrupt controller is an ARM GIC400 interrupt controller. Per the ARM GIC device-tree binding, the first address region is for the GIC distributor registers and the second address region is for the GIC

[PATCH 4.19 209/271] media: v4l2: Test type instead of cfg->type in v4l2_ctrl_new_custom()

2019-07-24 Thread Greg Kroah-Hartman
From: Boris Brezillon commit 07d89227a983df957a6a7c56f7c040cde9ac571f upstream. cfg->type can be overridden by v4l2_ctrl_fill() and the new value is stored in the local type var. Fix the tests to use this local var. Fixes: 0996517cf8ea ("V4L/DVB: v4l2: Add new control handling framework") Cc:

[PATCH 4.19 215/271] fs/proc/proc_sysctl.c: fix the default values of i_uid/i_gid on /proc/sys inodes.

2019-07-24 Thread Greg Kroah-Hartman
From: Radoslaw Burny commit 5ec27ec735ba0477d48c80561cc5e856f0c5dfaf upstream. Normally, the inode's i_uid/i_gid are translated relative to s_user_ns, but this is not a correct behavior for proc. Since sysctl permission check in test_perm is done against GLOBAL_ROOT_[UG]ID, it makes more sense

[PATCH 4.19 265/271] usb: Handle USB3 remote wakeup for LPM enabled devices correctly

2019-07-24 Thread Greg Kroah-Hartman
From: Lee, Chiasheng commit e244c4699f859cf7149b0781b1894c7996a8a1df upstream. With Link Power Management (LPM) enabled USB3 links transition to low power U1/U2 link states from U0 state automatically. Current hub code detects USB3 remote wakeups by checking if the software state still shows

[PATCH 4.19 244/271] xfs: dont overflow xattr listent buffer

2019-07-24 Thread Greg Kroah-Hartman
commit 3b50086f0c0d78c144d9483fa292c1509c931b70 upstream. For VFS listxattr calls, xfs_xattr_put_listent calls __xfs_xattr_put_listent twice if it sees an attribute "trusted.SGI_ACL_FILE": once for that name, and again for "system.posix_acl_access". Unfortunately, if we happen to run out of

[PATCH 4.19 247/271] xfs: reserve blocks for ifree transaction during log recovery

2019-07-24 Thread Greg Kroah-Hartman
commit 15a268d9f263ed3a0601a1296568241a5a3da7aa upstream. Log recovery frees all the inodes stored in the unlinked list, which can cause expansion of the free inode btree. The ifree code skips block reservations if it thinks there's a per-AG space reservation, but we don't set up the reservation

[PATCH 4.19 245/271] xfs: rename m_inotbt_nores to m_finobt_nores

2019-07-24 Thread Greg Kroah-Hartman
commit e1f6ca11381588e3ef138c10de60eeb34cb8466a upstream. Rename this flag variable to imply more strongly that it's related to the free inode btree (finobt) operation. No functional changes. Signed-off-by: Darrick J. Wong Reviewed-by: Christoph Hellwig Reviewed-by: Dave Chinner

[PATCH 4.19 243/271] xfs: flush removing page cache in xfs_reflink_remap_prep

2019-07-24 Thread Greg Kroah-Hartman
commit 2c307174ab77e34645e75e12827646e044d273c3 upstream. On a sub-page block size filesystem, fsx is failing with a data corruption after a series of operations involving copying a file with the destination offset beyond EOF of the destination of the file: 8093(157 mod 256): TRUNCATE DOWN

[PATCH 4.19 234/271] Btrfs: add missing inode version, ctime and mtime updates when punching hole

2019-07-24 Thread Greg Kroah-Hartman
From: Filipe Manana commit 179006688a7e888cbff39577189f2e034786d06a upstream. If the range for which we are punching a hole covers only part of a page, we end up updating the inode item but we skip the update of the inode's iversion, mtime and ctime. Fix that by ensuring we update those

[PATCH 4.19 228/271] intel_th: pci: Add Ice Lake NNPI support

2019-07-24 Thread Greg Kroah-Hartman
From: Alexander Shishkin commit 4aa5aed2b6f267592705a526f57518a5d715b769 upstream. This adds Ice Lake NNPI support to the Intel(R) Trace Hub. Signed-off-by: Alexander Shishkin Reviewed-by: Andy Shevchenko Cc: stable Link:

[PATCH 4.19 236/271] HID: wacom: generic: only switch the mode on devices with LEDs

2019-07-24 Thread Greg Kroah-Hartman
From: Aaron Armstrong Skomra commit d8e9806005f28bbb49899dab2068e3359e22ba35 upstream. Currently, the driver will attempt to set the mode on all devices with a center button, but some devices with a center button lack LEDs, and attempting to set the LEDs on devices without LEDs results in the

  1   2   3   4   5   6   7   8   9   10   >