Re: [RFC 00/79] perf tools: Initial libperf separation

2019-07-24 Thread Song Liu
> On Jul 24, 2019, at 6:50 AM, Arnaldo Carvalho de Melo > wrote: > > Em Wed, Jul 24, 2019 at 07:42:50AM +, Song Liu escreveu: >>> On Jul 21, 2019, at 4:23 AM, Jiri Olsa wrote: > >>> we have long term goal to separate some of the perf functionality >>> into library. This patchset is init

Re: [PATCH v2] input: API for Setting a Timestamp from a Driver

2019-07-24 Thread Dmitry Torokhov
Hi Atif, On Thu, Jul 18, 2019 at 12:41:33PM -0700, Atif Niyaz wrote: > @@ -150,16 +143,19 @@ static void __evdev_flush_queue(struct evdev_client > *client, unsigned int type) > static void __evdev_queue_syn_dropped(struct evdev_client *client) > { > struct input_event ev; > - ktime_t

KASAN: use-after-free Read in tls_sk_proto_cleanup

2019-07-24 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:9e6dfe80 Add linux-next specific files for 20190724 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=16797ef060 kernel config: https://syzkaller.appspot.com/x/.config?x=6cbb8fc2cf2842d7

[PATCH v3 3/5] iio: imu: st_lsm6sdx: move register definitions to sensor_settings struct

2019-07-24 Thread Martin Kepplinger
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 Kepplinger --- drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h | 6 +

[PATCH v3 0/5] iio: imu: st_lsm6dsx: Add support for LSM9DS1

2019-07-24 Thread Martin Kepplinger
Resend 2 of Lorenzo's patches that this builds upon. They have been previously posted to linux-iio only: https://lore.kernel.org/linux-iio/cover.1563226641.git.lore...@kernel.org/ Then, add support for the LSM9DS1 accel/gyro unit in 3 simple steps. This is also only a resend and rebase of the v2:

fs/ceph/debugfs.c:297:2: warning: 'return' with a value, in function returning void

2019-07-24 Thread kbuild test robot
tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/torvalds/linux.git master head: bed38c3e2dca01b358a62b5e73b46e875742fd75 commit: 1a829ff2a6c37187ff8020488e84ec392cb94854 ceph: no need to check return value of debugfs_create functions date: 3 weeks ago config: x86_64-randconf

[PATCH v3 1/5] iio: imu: st_lsm6dsx: move odr_table in st_lsm6dsx_sensor_settings

2019-07-24 Thread Martin Kepplinger
From: Lorenzo Bianconi Move sensor odr table in st_lsm6dsx_sensor_settings in order to support sensors with different odr maps. This is a preliminary patch to add support for LSM9DS1 sensor to st_lsm6dsx driver Signed-off-by: Lorenzo Bianconi --- drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h |

[PATCH v3 2/5] iio: imu: st_lsm6dsx: move fs_table in st_lsm6dsx_sensor_settings

2019-07-24 Thread Martin Kepplinger
From: Lorenzo Bianconi Move fs_table in st_lsm6dsx_sensor_settings in order to support sensors with different gain maps. This is a preliminary patch to add support for LSM9DS1 sensor to st_lsm6dsx driver Signed-off-by: Lorenzo Bianconi --- drivers/iio/imu/st_lsm6dsx/st_lsm6dsx.h | 2 +

[PATCH v3 5/5] dt-bindings: iio: imu: st_lsm6dsx: add lsm9ds1 device bindings

2019-07-24 Thread Martin Kepplinger
Signed-off-by: Martin Kepplinger --- Documentation/devicetree/bindings/iio/imu/st_lsm6dsx.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/iio/imu/st_lsm6dsx.txt b/Documentation/devicetree/bindings/iio/imu/st_lsm6dsx.txt index 92b48f242356..fd1722fc93af 1

[PATCH v3 4/5] iio: imu: st_lsm6dsx: add support for accel/gyro unit of lsm9sd1

2019-07-24 Thread Martin Kepplinger
The LSM9DS1's accelerometer / gyroscope unit and it's magnetometer (separately supported in iio/magnetometer/st_magn*) are located on a separate i2c addresses on the bus. For the datasheet, see https://www.st.com/resource/en/datasheet/lsm9ds1.pdf Treat it just like the LSM6* devices and, despite

general protection fault in tls_trim_both_msgs

2019-07-24 Thread syzbot
Hello, syzbot found the following crash on: HEAD commit:9e6dfe80 Add linux-next specific files for 20190724 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=1046971fa0 kernel config: https://syzkaller.appspot.com/x/.config?x=6cbb8fc2cf2842d7

[PATCH] ASoC: Intel: Fix some acpi vs apci typo in somme comments

2019-07-24 Thread Christophe JAILLET
Fix some typo to have the filaname given in a comment match the real name of the file. Some 'acpi' have erroneously been written 'apci' Signed-off-by: Christophe JAILLET --- sound/soc/intel/common/soc-acpi-intel-bxt-match.c | 2 +- sound/soc/intel/common/soc-acpi-intel-byt-match.c | 2 +-

[PATCH v2] perf diff: Report noisy for cycles diff

2019-07-24 Thread Jin Yao
This patch prints the stddev and hist for the cycles diff of program block. It can help us to understand if the cycles diff is noisy or not. This patch is inspired by Andi Kleen's patch https://lwn.net/Articles/600471/ We create new option '-n or --noisy'. Example: perf record -b ./div perf rec

Re: [PATCH v3 1/3] mm: document zone device struct page field usage

2019-07-24 Thread Christoph Hellwig
On Wed, Jul 24, 2019 at 04:26:58PM -0700, Ralph Campbell wrote: > Struct page for ZONE_DEVICE private pages uses the page->mapping and > and page->index fields while the source anonymous pages are migrated to > device private memory. This is so rmap_walk() can find the page when > migrating the ZON

Re: [PATCH v3 2/5] OPP: Add function to look up required OPP's for a given OPP

2019-07-24 Thread Viresh Kumar
On 24-07-19, 20:46, Saravana Kannan wrote: > On Wed, Jul 24, 2019 at 7:58 PM Viresh Kumar wrote: > > On 23-07-19, 17:23, Saravana Kannan wrote: > > > I almost said "not sure. Let me just compare pointers". > > > I think (not sure) it has to do with the same OPP table being used to > > > create mu

[PATCH 4.19 114/271] libata: dont request sense data on !ZAC ATA devices

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit ca156e006add67e4beea7896be395160735e09b0 ] ZAC support added sense data requesting on error for both ZAC and ATA devices. This seems to cause erratic error handling behaviors on some SSDs where the device reports sense data availability and then delivers the wrong content making

[PATCH 4.19 116/271] xsk: Properly terminate assignment in xskq_produce_flush_desc

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit f7019b7b0ad14bde732b8953161994edfc384953 ] Clang warns: In file included from net/xdp/xsk_queue.c:10: net/xdp/xsk_queue.h:292:2: warning: expression result unused [-Wunused-value] WRITE_ONCE(q->ring->producer, q->prod_tail); ^~

[PATCH 4.19 112/271] perf tools: Increase MAX_NR_CPUS and MAX_CACHES

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 9f94c7f947e919c343b30f080285af53d0fa9902 ] Attempting to profile 1024 or more CPUs with perf causes two errors: perf record -a [ perf record: Woken up X times to write data ] way too many cpu caches.. [ perf record: Captured and wrote X MB perf.data (X samples) ] perf

[PATCH 4.19 111/271] ath10k: fix PCIE device wake up failed

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 011d4111c8c602ea829fa4917af1818eb0500a90 ] Observed PCIE device wake up failed after ~120 iterations of soft-reboot test. The error message is "ath10k_pci :01:00.0: failed to wake up device : -110" The call trace as below: ath10k_pci_probe -> ath10k_pci_force_wake -> ath10k_

[PATCH 4.19 082/271] ipoib: correcly show a VF hardware address

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 64d701c608fea362881e823b666327f5d28d7ffd ] in the case of IPoIB with SRIOV enabled hardware ip link show command incorrecly prints 0 instead of a VF hardware address. Before: 11: ib1: mtu 2044 qdisc pfifo_fast state UP mode DEFAULT group default qlen 256 link/infiniband 80:

[PATCH 4.19 109/271] ipvs: fix tinfo memory leak in start_sync_thread

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 5db7c8b9f9fc2aeec671ae3ca6375752c162e0e7 ] syzkaller reports for memory leak in start_sync_thread [1] As Eric points out, kthread may start and stop before the threadfn function is called, so there is no chance the data (tinfo in our case) to be released in thread. Fix this by

[PATCH 4.19 106/271] mt7601u: do not schedule rx_tasklet when the device has been disconnected

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 4079e8ccabc3b6d1b503f2376123cb515d14921f ] Do not schedule rx_tasklet when the usb dongle is disconnected. Moreover do not grub rx_lock in mt7601u_kill_rx since usb_poison_urb can run concurrently with urb completion and we can unlink urbs from rx ring in any order. This patch fi

[PATCH 4.19 118/271] rslib: Fix handling of of caller provided syndrome

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit ef4d6a8556b637ad27c8c2a2cff1dda3da38e9a9 ] Check if the syndrome provided by the caller is zero, and act accordingly. Signed-off-by: Ferdinand Blomqvist Signed-off-by: Thomas Gleixner Link: https://lkml.kernel.org/r/20190620141039.9874-6-ferdinand.blomqv...@gmail.com Signed-o

[PATCH 4.19 120/271] crypto: serpent - mark __serpent_setkey_sbox noinline

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 473971187d6727609951858c63bf12b0307ef015 ] The same bug that gcc hit in the past is apparently now showing up with clang, which decides to inline __serpent_setkey_sbox: crypto/serpent_generic.c:268:5: error: stack frame size of 2112 bytes in function '__serpent_setkey' [-Werror

[PATCH 4.19 103/271] media: hdpvr: fix locking and a missing msleep

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 6bc5a4a1927556ff9adce1aa95ea408c95453225 ] This driver has three locking issues: - The wait_event_interruptible() condition calls hdpvr_get_next_buffer(dev) which uses a mutex, which is not allowed. Rewrite with list_empty_careful() that doesn't need locking. - In hdpvr_rea

[PATCH 4.19 108/271] mt7601u: fix possible memory leak when the device is disconnected

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 23377c200b2eb48a60d0f228b2a2e75ed6ee6060 ] When the device is disconnected while passing traffic it is possible to receive out of order urbs causing a memory leak since the skb linked to the current tx urb is not removed. Fix the issue deallocating the skb cleaning up the tx ring

[PATCH 4.19 104/271] net: stmmac: sun8i: force select external PHY when no internal one

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 0fec7e72ae1391bb2d7527efb54fe6ae88acabce ] The PHY selection bit also exists on SoCs without an internal PHY; if it's set to 1 (internal PHY, default value) then the MAC will not make use of any PHY on such SoCs. This problem appears when adapting for H6, which has no real inter

[PATCH 4.19 085/271] ACPICA: Clear status of GPEs on first direct enable

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 44758bafa53602f2581a6857bb20b55d4d8ad5b2 ] ACPI GPEs (other than the EC one) can be enabled in two situations. First, the GPEs with existing _Lxx and _Exx methods are enabled implicitly by ACPICA during system initialization. Second, the GPEs without these methods (like GPEs lis

[PATCH 4.19 086/271] EDAC/sysfs: Fix memory leak when creating a csrow object

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 585fb3d93d32dbe89e718b85009f9c322cc554cd ] In edac_create_csrow_object(), the reference to the object is not released when adding the device to the device hierarchy fails (device_add()). This may result in a memory leak. Signed-off-by: Pan Bian Signed-off-by: Borislav Petkov R

[PATCH 4.19 122/271] wil6210: drop old event after wmi_call timeout

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 1a276003111c0404f6bfeffe924c5a21f482428b ] This change fixes a rare race condition of handling WMI events after wmi_call expires. wmi_recv_cmd immediately handles an event when reply_buf is defined and a wmi_call is waiting for the event. However, in case the wmi_call has alread

[PATCH 4.19 084/271] blk-iolatency: only account submitted bios

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit a3fb01ba5af066521f3f3421839e501bb2c71805 ] As is, iolatency recognizes done_bio and cleanup as ending paths. If a request is marked REQ_NOWAIT and fails to get a request, the bio is cleaned up via rq_qos_cleanup() and ended in bio_wouldblock_error(). This results in underflowing

[PATCH 4.19 087/271] nvme: fix possible io failures when removing multipathed ns

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 2181e455612a8db2761eabbf126640552a451e96 ] When a shared namespace is removed, we call blk_cleanup_queue() when the device can still be accessed as the current path and this can result in submission to a dying queue. Hence, direct_make_request() called by our mpath device may fai

[PATCH 4.19 131/271] ath10k: destroy sdio workqueue while remove sdio module

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 3ed39f8e747a7aafeec07bb244f2c3a1bdca5730 ] The workqueue need to flush and destory while remove sdio module, otherwise it will have thread which is not destory after remove sdio modules. Tested with QCA6174 SDIO with firmware WLAN.RMH.4.4.1-7-QCARMSWP-1. Signed-off-by: Wen

[PATCH 4.19 135/271] bpf: fix uapi bpf_prog_info fields alignment

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 0472301a28f6cf53a6bc5783e48a2d0bbff4682f ] Merge commit 1c8c5a9d38f60 ("Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net-next") undid the fix from commit 36f9814a494 ("bpf: fix uapi hole for 32 bit compat applications") by taking the gpl_compatible 1-bit field defini

[PATCH 4.19 139/271] net: usb: asix: init MAC address buffers

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 78226f6eaac80bf30256a33a4926c194ceefdf36 ] This is for fixing bug KMSAN: uninit-value in ax88772_bind Tested by https://groups.google.com/d/msg/syzkaller-bugs/aFQurGotng4/eB_HlNhhCwAJ Reported-by: syzbot+8a3fc6674bbc3978e...@syzkaller.appspotmail.com syzbot found the following

[PATCH 4.19 141/271] bpf, libbpf, smatch: Fix potential NULL pointer dereference

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 33bae185f74d49a0d7b1bfaafb8e959efce0f243 ] Based on the following report from Smatch, fix the potential NULL pointer dereference check: tools/lib/bpf/libbpf.c:3493 bpf_prog_load_xattr() warn: variable dereferenced before check 'attr' (see line 3483) 3479 int bpf_prog_lo

[PATCH 4.19 140/271] rxrpc: Fix oops in tracepoint

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 99f0eae653b2db64917d0b58099eb51e300b311d ] If the rxrpc_eproto tracepoint is enabled, an oops will be cause by the trace line that rxrpc_extract_header() tries to emit when a protocol error occurs (typically because the packet is short) because the call argument is NULL. Fix thi

[PATCH 4.19 142/271] selftests: bpf: fix inlines in test_lwt_seg6local

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 11aca65ec4db09527d3e9b6b41a0615b7da4386b ] Selftests are reporting this failure in test_lwt_seg6local.sh: + ip netns exec ns2 ip -6 route add fb00::6 encap bpf in obj test_lwt_seg6local.o sec encap_srh dev veth2 Error fetching program/map! Failed to parse eBPF program: Operatio

[PATCH 4.19 136/271] perf stat: Make metric event lookup more robust

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 145c407c808352acd625be793396fd4f33c794f8 ] After setting up metric groups through the event parser, the metricgroup code looks them up again in the event list. Make sure we only look up events that haven't been used by some other metric. The data structures currently cannot hand

[PATCH 4.19 144/271] gpiolib: Fix references to gpiod_[gs]et_*value_cansleep() variants

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 3285170f28a850638794cdfe712eb6d93e51e706 ] Commit 372e722ea4dd4ca1 ("gpiolib: use descriptors internally") renamed the functions to use a "gpiod" prefix, and commit 79a9becda8940deb ("gpiolib: export descriptor-based GPIO interface") introduced the "raw" variants, but both change

[PATCH 4.19 158/271] net: mvmdio: defer probe of orion-mdio if a clock is not ready

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 433a06d7d74e677c40b1148c70c48677ff62fb6b ] Defer probing of the orion-mdio interface when getting a clock returns EPROBE_DEFER. This avoids locking up the Armada 8k SoC when mdio is used before all clocks have been enabled. Signed-off-by: Josua Mayer Reviewed-by: Andrew Lunn S

[PATCH 4.19 160/271] floppy: fix div-by-zero in setup_format_params

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit f3554aeb991214cbfafd17d55e2bfddb50282e32 ] This fixes a divide by zero error in the setup_format_params function of the floppy driver. Two consecutive ioctls can trigger the bug: The first one should set the drive geometry with such .sect and .rate values for the F_SECT_PER_TRAC

[PATCH 4.19 155/271] gtp: fix Illegal context switch in RCU read-side critical section.

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 3f167e1921865b379a9becf03828e7202c7b4917 ] ipv4_pdp_add() is called in RCU read-side critical section. So GFP_KERNEL should not be used in the function. This patch make ipv4_pdp_add() to use GFP_ATOMIC instead of GFP_KERNEL. Test commands: gtp-link add gtp1 & gtp-tunnel add gtp1

[PATCH 4.19 159/271] iavf: fix dereference of null rx_buffer pointer

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 9fe06a51287b2d41baef7ece94df34b5abf19b90 ] A recent commit efa14c3985828d ("iavf: allow null RX descriptors") added a null pointer sanity check on rx_buffer, however, rx_buffer is being dereferenced before that check, which implies a null pointer dereference bug can potentially o

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

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit a2bed90704c68d3763bf24decb1b781a45395de8 ] Current gtp_newlink() could be called after unregister_pernet_subsys(). gtp_newlink() uses gtp_net but it can be destroyed by unregister_pernet_subsys(). So unregister_pernet_subsys() should be called after rtnl_link_unregister(). Test

[PATCH 4.19 124/271] bcache: check CACHE_SET_IO_DISABLE in allocator code

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit e775339e1ae1205b47d94881db124c11385e597c ] If CACHE_SET_IO_DISABLE of a cache set flag is set by too many I/O errors, currently allocator routines can still continue allocate space which may introduce inconsistent metadata state. This patch checkes CACHE_SET_IO_DISABLE bit in fo

[PATCH 4.19 153/271] Bluetooth: validate BLE connection interval updates

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit c49a8682fc5d298d44e8d911f4fa14690ea9485e ] Problem: The Linux Bluetooth stack yields complete control over the BLE connection interval to the remote device. The Linux Bluetooth stack provides access to the BLE connection interval min and max values through /sys/kernel/debug/blue

[PATCH 4.19 152/271] gtp: add missing gtp_encap_disable_sock() in gtp_encap_enable()

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit e30155fd23c9c141cbe7d99b786e10a83a328837 ] If an invalid role is sent from user space, gtp_encap_enable() will fail. Then, it should call gtp_encap_disable_sock() but current code doesn't. It makes memory leak. Fixes: 91ed81f9abc7 ("gtp: support SGSN-side tunnels") Signed-off-by

[PATCH 4.19 147/271] Bluetooth: Add new 13d3:3491 QCA_ROME device

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 44d34af2e4cfd0c5357182f8b43f3e0a1fe30a2e ] Without the QCA ROME setup routine this adapter fails to establish a SCO connection. T: Bus=01 Lev=01 Prnt=01 Port=08 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 ProdID=3

[PATCH 4.19 146/271] Bluetooth: hci_bcsp: Fix memory leak in rx_skb

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 4ce9146e0370fcd573f0372d9b4e5a22567c ] Syzkaller found that it is possible to provoke a memory leak by never freeing rx_skb in struct bcsp_struct. Fix by freeing in bcsp_close() Signed-off-by: Tomas Bortoli Reported-by: syzbot+98162c885993b72f1...@syzkaller.appspotmail.com

[PATCH 4.19 150/271] perf tests: Fix record+probe_libc_inet_pton.sh for powerpc64

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit bff5a556c149804de29347a88a884d25e4e4e3a2 ] 'probe libc's inet_pton & backtrace it with ping' testcase sometimes fails on powerpc because distro ping binary does not have symbol information and thus it prints "[unknown]" function name in the backtrace. Accept "[unknown]" as valid

[PATCH 4.19 151/271] Bluetooth: Check state in l2cap_disconnect_rsp

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 28261da8a26f4915aa257d12d506c6ba179d961f ] Because of both sides doing L2CAP disconnection at the same time, it was possible to receive L2CAP Disconnection Response with CID that was already freed. That caused problems if CID was already reused and L2CAP Connection Request with s

[PATCH 4.19 161/271] floppy: fix out-of-bounds read in next_valid_format

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 5635f897ed83fd539df78e98ba69ee91592f9bb8 ] This fixes a global out-of-bounds read access in the next_valid_format function of the floppy driver. The values from autodetect field of the struct floppy_drive_params are used as indices for the floppy_type array in the next_valid_for

[PATCH 4.19 165/271] scsi: NCR5380: Reduce goto statements in NCR5380_select()

2019-07-24 Thread Greg Kroah-Hartman
From: Finn Thain commit 6a162836997c10bbefb7c7ca772201cc45c0e4a6 upstream. Replace a 'goto' statement with a simple 'return' where possible. This improves readability. No functional change. Tested-by: Michael Schmitz Signed-off-by: Finn Thain Signed-off-by: Martin K. Petersen Signed-off-by:

[PATCH 4.19 164/271] xen: let alloc_xenballooned_pages() fail if not enough memory free

2019-07-24 Thread Greg Kroah-Hartman
From: Juergen Gross commit a1078e821b605813b63bf6bca414a85f804d5c66 upstream. Instead of trying to allocate pages with GFP_USER in add_ballooned_pages() check the available free memory via si_mem_available(). GFP_USER is far less limiting memory exhaustion than the test via si_mem_available().

[PATCH 4.19 163/271] floppy: fix out-of-bounds read in copy_buffer

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit da99466ac243f15fbba65bd261bfc75ffa1532b6 ] This fixes a global out-of-bounds read access in the copy_buffer function of the floppy driver. The FDDEFPRM ioctl allows one to set the geometry of a disk. The sect and head fields (unsigned int) of the floppy_drive structure are used

[PATCH 4.19 128/271] bcache: fix potential deadlock in cached_def_free()

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 7e865eba00a3df2dc8c4746173a8ca1c1c7f042e ] When enable lockdep and reboot system with a writeback mode bcache device, the following potential deadlock warning is reported by lockdep engine. [ 101.536569][ T401] kworker/2:2/401 is trying to acquire lock: [ 101.538575][ T401]

[PATCH 4.19 121/271] crypto: asymmetric_keys - select CRYPTO_HASH where needed

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 90acc0653d2bee203174e66d519fbaaa513502de ] Build testing with some core crypto options disabled revealed a few modules that are missing CRYPTO_HASH: crypto/asymmetric_keys/x509_public_key.o: In function `x509_get_sig_params': x509_public_key.c:(.text+0x4c7): undefined reference

[PATCH 4.19 176/271] crypto: chacha20poly1305 - fix atomic sleep when using async algorithm

2019-07-24 Thread Greg Kroah-Hartman
From: Eric Biggers commit 7545b6c2087f4ef0287c8c9b7eba6a728c67ff8e upstream. Clear the CRYPTO_TFM_REQ_MAY_SLEEP flag when the chacha20poly1305 operation is being continued from an async completion callback, since sleeping may not be allowed in that context. This is basically the same bug that w

[PATCH 4.19 129/271] net: hns3: fix a -Wformat-nonliteral compile warning

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 18d219b783da61a6cc77581f55fc4af2fa16bc36 ] When setting -Wformat=2, there is a compiler warning like this: hclge_main.c:xxx:x: warning: format not a string literal and no format arguments [-Wformat-nonliteral] strs[i].desc); ^~~~ This patch adds missing format parameter "%s" to

[PATCH 4.19 179/271] crypto: crypto4xx - block ciphers should only accept complete blocks

2019-07-24 Thread Greg Kroah-Hartman
From: Christian Lamparter commit 0f7a81374060828280fcfdfbaa162cb559017f9f upstream. The hardware automatically zero pads incomplete block ciphers blocks without raising any errors. This is a screw-up. This was noticed by CONFIG_CRYPTO_MANAGER_EXTRA_TESTS tests that sent a incomplete blocks and e

[PATCH 4.19 162/271] floppy: fix invalid pointer dereference in drive_name

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 9b04609b784027968348796a18f601aed9db3789 ] This fixes the invalid pointer dereference in the drive_name function of the floppy driver. The native_format field of the struct floppy_drive_params is used as floppy_type array index in the drive_name function. Thus, the field should

[PATCH 4.19 181/271] crypto: ccp/gcm - use const time tag comparison.

2019-07-24 Thread Greg Kroah-Hartman
From: Cfir Cohen commit 538a5a072e6ef04377b180ee9b3ce5bae0a85da4 upstream. Avoid leaking GCM tag through timing side channel. Fixes: 36cf515b9bbe ("crypto: ccp - Enable support for AES GCM on v5 CCPs") Cc: # v4.12+ Signed-off-by: Cfir Cohen Acked-by: Gary R Hook Signed-off-by: Herbert Xu Si

Re: [PATCH v5 01/10] iommu/vt-d: Don't switch off swiotlb if use direct dma

2019-07-24 Thread Christoph Hellwig
Looks good: Reviewed-by: Christoph Hellwig

[PATCH 4.19 130/271] net: hns3: add some error checking in hclge_tm module

2019-07-24 Thread Greg Kroah-Hartman
[ Upstream commit 04f25edb48c441fc278ecc154c270f16966cbb90 ] When hdev->tx_sch_mode is HCLGE_FLAG_VNET_BASE_SCH_MODE, the hclge_tm_schd_mode_vnet_base_cfg calls hclge_tm_pri_schd_mode_cfg with vport->vport_id as pri_id, which is used as index for hdev->tm_info.tc_info, it will cause out of bound a

[PATCH 4.19 178/271] crypto: crypto4xx - fix blocksize for cfb and ofb

2019-07-24 Thread Greg Kroah-Hartman
From: Christian Lamparter commit 70c4997f34b6c6888b3ac157adec49e01d0df2d5 upstream. While the hardware consider them to be blockciphers, the reference implementation defines them as streamciphers. Do the right thing and set the blocksize to 1. This was found by CONFIG_CRYPTO_MANAGER_EXTRA_TESTS

[PATCH 4.19 185/271] bcache: Revert "bcache: free heap cache_set->flush_btree in bch_journal_free"

2019-07-24 Thread Greg Kroah-Hartman
From: Coly Li commit ba82c1ac1667d6efb91a268edb13fc9cdaecec9b upstream. This reverts commit 6268dc2c4703aabfb0b35681be709acf4c2826c6. This patch depends on commit c4dc2497d50d ("bcache: fix high CPU occupancy during journal") which is reverted in previous patch. So revert this one too. Fixes:

[PATCH 4.19 183/271] Revert "bcache: set CACHE_SET_IO_DISABLE in bch_cached_dev_error()"

2019-07-24 Thread Greg Kroah-Hartman
From: Coly Li commit 695277f16b3a102fcc22c97fdf2de77c7b19f0b3 upstream. This reverts commit 6147305c73e4511ca1a975b766b97a779d442567. Although this patch helps the failed bcache device to stop faster when too many I/O errors detected on corresponding cached device, setting CACHE_SET_IO_DISABLE

[PATCH 4.19 182/271] crypto: crypto4xx - fix a potential double free in ppc4xx_trng_probe

2019-07-24 Thread Greg Kroah-Hartman
From: Wen Yang commit 95566aa75cd6b3b404502c06f66956b5481194b3 upstream. There is a possible double free issue in ppc4xx_trng_probe(): 85: dev->trng_base = of_iomap(trng, 0); 86: of_node_put(trng); ---> released here 87: if (!dev->trng_base) 88: goto err_out; ..

[PATCH 4.19 191/271] Input: synaptics - whitelist Lenovo T580 SMBus intertouch

2019-07-24 Thread Greg Kroah-Hartman
From: Nick Black commit 1976d7d200c5a32e72293a2ada36b7b7c9d6dd6e upstream. Adds the Lenovo T580 to the SMBus intertouch list for Synaptics touchpads. I've tested with this for a week now, and it seems a great improvement. It's also nice to have the complaint gone from dmesg. Signed-off-by: Nick

[PATCH 4.19 184/271] bcache: Revert "bcache: fix high CPU occupancy during journal"

2019-07-24 Thread Greg Kroah-Hartman
From: Coly Li commit 249a5f6da57c28a903c75d81505d58ec8c10030d upstream. This reverts commit c4dc2497d50d9c6fb16aa0d07b6a14f3b2adb1e0. This patch enlarges a race between normal btree flush code path and flush_btree_write(), which causes deadlock when journal space is exhausted. Reverts this patc

[PATCH 4.19 168/271] scsi: core: Fix race on creating sense cache

2019-07-24 Thread Greg Kroah-Hartman
From: Ming Lei commit f9b0530fa02e0c73f31a49ef743e8f44eb8e32cc upstream. When scsi_init_sense_cache(host) is called concurrently from different hosts, each code path may find that no cache has been created and allocate a new one. The lack of locking can lead to potentially overriding a cache all

[PATCH 4.19 190/271] Input: alps - dont handle ALPS cs19 trackpoint-only device

2019-07-24 Thread Greg Kroah-Hartman
From: Hui Wang commit 7e4935ccc3236751e5fe4bd6846f86e46bb2e427 upstream. On a latest Lenovo laptop, the trackpoint and 3 buttons below it don't work at all, when we move the trackpoint or press those 3 buttons, the kernel will print out: "Rejected trackstick packet from non DualPoint device" Th

[PATCH 4.19 188/271] bcache: destroy dc->writeback_write_wq if failed to create dc->writeback_thread

2019-07-24 Thread Greg Kroah-Hartman
From: Coly Li commit f54d801dda14942dbefa00541d10603015b7859c upstream. Commit 9baf30972b55 ("bcache: fix for gc and write-back race") added a new work queue dc->writeback_write_wq, but forgot to destroy it in the error condition when creating dc->writeback_thread failed. This patch destroys dc

[PATCH 4.19 169/271] scsi: megaraid_sas: Fix calculation of target ID

2019-07-24 Thread Greg Kroah-Hartman
From: Shivasharan S commit c8f96df5b8e633056b7ebf5d52a9d6fb1b156ce3 upstream. In megasas_get_target_prop(), driver is incorrectly calculating the target ID for devices with channel 1 and 3. Due to this, firmware will either fail the command (if there is no device with the target id sent from dr

[PATCH 4.19 201/271] pNFS: Fix a typo in pnfs_update_layout

2019-07-24 Thread Greg Kroah-Hartman
From: Trond Myklebust commit 400417b05f3ec0531544ca5f94e64d838d8b8849 upstream. We're supposed to wait for the outstanding layout count to go to zero, but that got lost somehow. Fixes: d03360aaf5cca ("pNFS: Ensure we return the error if someone...") Reported-by: Anna Schumaker Signed-off-by: T

[PATCH 4.19 198/271] iwlwifi: fix RF-Kill interrupt while FW load for gen2 devices

2019-07-24 Thread Greg Kroah-Hartman
From: Emmanuel Grumbach commit ed3e4c6d3cd8f093a3636cb05492429fe2af228d upstream. Newest devices have a new firmware load mechanism. This mechanism is called the context info. It means that the driver doesn't need to load the sections of the firmware. The driver rather prepares a place in DRAM,

[PATCH 4.19 199/271] NFSv4: Handle the special Linux file open access mode

2019-07-24 Thread Greg Kroah-Hartman
From: Trond Myklebust commit 44942b4e457beda00981f616402a1a791e8c616e upstream. According to the open() manpage, Linux reserves the access mode 3 to mean "check for read and write permission on the file and return a file descriptor that can't be used for reading or writing." Currently, the NFSv

[PATCH 4.19 193/271] regulator: s2mps11: Fix buck7 and buck8 wrong voltages

2019-07-24 Thread Greg Kroah-Hartman
From: Krzysztof Kozlowski commit 16da0eb5ab6ef2dd1d33431199126e63db9997cc upstream. On S2MPS11 device, the buck7 and buck8 regulator voltages start at 750 mV, not 600 mV. Using wrong minimal value caused shifting of these regulator values by 150 mV (e.g. buck7 usually configured to v1.35 V was

[PATCH 4.19 194/271] arm64: tegra: Update Jetson TX1 GPU regulator timings

2019-07-24 Thread Greg Kroah-Hartman
From: Jon Hunter commit ece6031ece2dd64d63708cfe1088016cee5b10c0 upstream. The GPU regulator enable ramp delay for Jetson TX1 is set to 1ms which not sufficient because the enable ramp delay has been measured to be greater than 1ms. Furthermore, the downstream kernels released by NVIDIA for Jets

[PATCH 4.19 195/271] iwlwifi: pcie: dont service an interrupt that was masked

2019-07-24 Thread Greg Kroah-Hartman
From: Emmanuel Grumbach commit 3b57a10ca14c619707398dc58fe5ece18c95b20b upstream. Sometimes the register status can include interrupts that were masked. We can, for example, get the RF-Kill bit set in the interrupt status register although this interrupt was masked. Then if we get the ALIVE inte

[PATCH 4.19 171/271] scsi: mac_scsi: Fix pseudo DMA implementation, take 2

2019-07-24 Thread Greg Kroah-Hartman
From: Finn Thain commit 78ff751f8e6a9446e9fb26b2bff0b8d3f8974cbd upstream. A system bus error during a PDMA transfer can mess up the calculation of the transfer residual (the PDMA handshaking hardware lacks a byte counter). This results in data corruption. The algorithm in this patch anticipate

[PATCH 4.19 205/271] raid5-cache: Need to do start() part job after adding journal device

2019-07-24 Thread Greg Kroah-Hartman
From: Xiao Ni commit d9771f5ec46c282d518b453c793635dbdc3a2a94 upstream. commit d5d885fd514f ("md: introduce new personality funciton start()") splits the init job to two parts. The first part run() does the jobs that do not require the md threads. The second part start() does the jobs that requi

[PATCH 4.19 221/271] 9p/xen: Add cleanup path in p9_trans_xen_init

2019-07-24 Thread Greg Kroah-Hartman
From: YueHaibing commit 80a316ff16276b36d0392a8f8b2f63259857ae98 upstream. If xenbus_register_frontend() fails in p9_trans_xen_init, we should call v9fs_unregister_trans() to do cleanup. Link: http://lkml.kernel.org/r/20190430143933.19368-1-yuehaib...@huawei.com Cc: sta...@vger.kernel.org Fixes

[PATCH 4.19 172/271] crypto: ghash - fix unaligned memory access in ghash_setkey()

2019-07-24 Thread Greg Kroah-Hartman
From: Eric Biggers commit 5c6bc4dfa515738149998bb0db2481a4fdead979 upstream. Changing ghash_mod_init() to be subsys_initcall made it start running before the alignment fault handler has been installed on ARM. In kernel builds where the keys in the ghash test vectors happened to be misaligned in

[PATCH 4.19 220/271] xen/events: fix binding user event channels to cpus

2019-07-24 Thread Greg Kroah-Hartman
From: Juergen Gross commit bce5963bcb4f9934faa52be323994511d59fd13c upstream. When binding an interdomain event channel to a vcpu via IOCTL_EVTCHN_BIND_INTERDOMAIN not only the event channel needs to be bound, but the affinity of the associated IRQi must be changed, too. Otherwise the IRQ and th

[PATCH 4.19 208/271] ALSA: hda/realtek: apply ALC891 headset fixup to one Dell machine

2019-07-24 Thread Greg Kroah-Hartman
From: Hui Wang commit 4b4e0e32e4b09274dbc9d173016c1a026f44608c upstream. Without this patch, the headset-mic and headphone-mic don't work. Cc: Signed-off-by: Hui Wang Signed-off-by: Takashi Iwai Signed-off-by: Greg Kroah-Hartman --- sound/pci/hda/patch_realtek.c |5 + 1 file chang

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

2019-07-24 Thread Greg Kroah-Hartman
From: Elena Petrova commit 1d4aaf16defa86d2665ae7db0259d6cb07e2091f upstream. The sha1-ce finup implementation for ARM64 produces wrong digest for empty input (len=0). Expected: da39a3ee..., result: 67452301... (initial value of SHA internal state). The error is in sha1_ce_finup: for empty data

[PATCH 4.19 204/271] ASoC: dapm: Adapt for debugfs API change

2019-07-24 Thread Greg Kroah-Hartman
From: Mark Brown commit ceaea851b9ea75f9ea2bbefb53ff0d4b27cd5a6e upstream. Back in ff9fb72bc07705c (debugfs: return error values, not NULL) the debugfs APIs were changed to return error pointers rather than NULL pointers on error, breaking the error checking in ASoC. Update the code to use IS_ER

[PATCH 4.19 207/271] ALSA: hda/realtek - Fixed Headphone Mic cant record on Dell platform

2019-07-24 Thread Greg Kroah-Hartman
From: Kailang Yang commit fbc571290d9f7bfe089c50f4ac4028dd98ebfe98 upstream. It assigned to wrong model. So, The headphone Mic can't work. Fixes: 3f640970a414 ("ALSA: hda - Fix headset mic detection problem for several Dell laptops") Signed-off-by: Kailang Yang Cc: Signed-off-by: Takashi Iwa

[PATCH 4.19 170/271] scsi: mac_scsi: Increase PIO/PDMA transfer length threshold

2019-07-24 Thread Greg Kroah-Hartman
From: Finn Thain commit 7398cee4c3e6aea1ba07a6449e5533ecd0b92cdd upstream. Some targets introduce delays when handshaking the response to certain commands. For example, a disk may send a 96-byte response to an INQUIRY command (or a 24-byte response to a MODE SENSE command) too slowly. Apparentl

[PATCH 4.19 225/271] perf/x86/amd/uncore: Do not set ThreadMask and SliceMask for non-L3 PMCs

2019-07-24 Thread Greg Kroah-Hartman
From: Kim Phillips commit 16f4641166b10e199f0d7b68c2c5f004fef0bda3 upstream. The following commit: d7cbbe49a930 ("perf/x86/amd/uncore: Set ThreadMask and SliceMask for L3 Cache perf events") enables L3 PMC events for all threads and slices by writing 1's in 'ChL3PmcCfg' (L3 PMC PERF_CTL) re

[PATCH 4.19 222/271] 9p/virtio: Add cleanup path in p9_virtio_init

2019-07-24 Thread Greg Kroah-Hartman
From: YueHaibing commit d4548543fc4ece56c6f04b8586f435fb4fd84c20 upstream. KASAN report this: BUG: unable to handle kernel paging request at a0097000 PGD 3870067 P4D 3870067 PUD 3871063 PMD 2326e2067 PTE 0 Oops: [#1 CPU: 0 PID: 5340 Comm: modprobe Not tainted 5.1.0-rc7+ #25 Hardwar

[PATCH 4.19 237/271] HID: wacom: generic: Correct pad syncing

2019-07-24 Thread Greg Kroah-Hartman
From: Aaron Armstrong Skomra commit d4b8efeb46d99a5d02e7f88ac4eaccbe49370770 upstream. Only sync the pad once per report, not once per collection. Also avoid syncing the pad on battery reports. Fixes: f8b6a74719b5 ("HID: wacom: generic: Support multiple tools per report") Cc: # v4.17+ Signed-o

[PATCH 4.19 229/271] PCI: hv: Fix a use-after-free bug in hv_eject_device_work()

2019-07-24 Thread Greg Kroah-Hartman
From: Dexuan Cui commit 4df591b20b80cb77920953812d894db259d85bd7 upstream. Fix a use-after-free in hv_eject_device_work(). Fixes: 05f151a73ec2 ("PCI: hv: Fix a memory leak in hv_eject_device_work()") Signed-off-by: Dexuan Cui Signed-off-by: Lorenzo Pieralisi Reviewed-by: Michael Kelley Cc: s

[PATCH 4.19 230/271] PCI: Do not poll for PME if the device is in D3cold

2019-07-24 Thread Greg Kroah-Hartman
From: Mika Westerberg commit 000dd5316e1c756a1c028f22e01d06a38249dd4d upstream. PME polling does not take into account that a device that is directly connected to the host bridge may go into D3cold as well. This leads to a situation where the PME poll thread reads from a config space of a device

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

[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: https://lore.kernel.org/r/20190621161930.60785-5-alexander.shish...@l

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

[PATCH 4.19 235/271] IB/mlx5: Report correctly tag matching rendezvous capability

2019-07-24 Thread Greg Kroah-Hartman
From: Danit Goldberg commit 89705e92700170888236555fe91b45e4c1bb0985 upstream. Userspace expects the IB_TM_CAP_RC bit to indicate that the device supports RC transport tag matching with rendezvous offload. However the firmware splits this into two capabilities for eager and rendezvous tag matchi

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