[PATCH 5.1 065/121] mdesc: fix a missing-check bug in get_vdev_port_node_info()

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 80caf43549e7e41a695c6d1e11066286538b336f ] In get_vdev_port_node_info(), 'node_info->vdev_port.name' is allcoated by kstrdup_const(), and it returns NULL when fails. So 'node_info->vdev_port.name' should be checked. Signed-off-by: Gen Zhang Signed-off-by: David S. Miller Signe

[PATCH 5.1 038/121] dmaengine: sprd: Fix the incorrect start for 2-stage destination channels

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 3d626a97f0303e9c30d063434b749de3f0f91fb5 ] The 2-stage destination channel will be triggered by source channel automatically, which means we should not trigger it by software request. Signed-off-by: Eric Long Signed-off-by: Baolin Wang Signed-off-by: Vinod Koul Signed-off-by:

[PATCH 4.14 35/51] s390/qeth: fix VLAN attribute in bridge_hostnotify udev event

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 335726195e460cb6b3f795b695bfd31f0ea70ef0 ] Enabling sysfs attribute bridge_hostnotify triggers a series of udev events for the MAC addresses of all currently connected peers. In case no VLAN is set for a peer, the device reports the corresponding MAC addresses with VLAN ID 4096.

[PATCH 5.1 041/121] ARC: [plat-hsdk]: Add missing multicast filter bins number to GMAC node

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit ecc906a11c2a0940e1a380debd8bd5bc09faf454 ] GMAC controller on HSDK boards supports 256 Hash Table size so we need to add the multicast filter bins property. This allows for the Hash filter to work properly using stmmac driver. Cc: Joao Pinto Cc: Rob Herring Cc: Mark Rutland C

[PATCH 5.1 071/121] drm/arm/hdlcd: Actually validate CRTC modes

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit b96151edced4edb6a18aa89a5fa02c7066efff45 ] Rather than allowing any old mode through, then subsequently refusing unmatchable clock rates in atomic_check when it's too late to back out and pick a different mode, let's do that validation up-front where it will cause unsupported mod

[PATCH 5.1 081/121] tests: fix pidfd-test compilation

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 1fcd0eb356ad56c4e405f06e31dd9fde2109d5ab ] Define __NR_pidfd_send_signal if it isn't to prevent a potential compilation error. To make pidfd-test compile on all arches, irrespective of whether or not syscall numbers are assigned, define the syscall number to -1. If it isn't defi

[PATCH 5.1 086/121] hwmon: (pmbus/core) Treat parameters as paged if on multiple pages

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 4a60570dce658e3f8885bbcf852430b99f65aca5 ] Some chips have attributes which exist on more than one page but the attribute is not presently marked as paged. This causes the attributes to be generated with the same label, which makes it impossible for userspace to tell them apart.

[PATCH 5.1 095/121] can: purge socket error queue on sock destruct

2019-06-24 Thread Greg Kroah-Hartman
From: Willem de Bruijn commit fd704bd5ee749d560e86c4f1fd2ef486d8abf7cf upstream. CAN supports software tx timestamps as of the below commit. Purge any queued timestamp packets on socket destroy. Fixes: 51f31cabe3ce ("ip: support for TX timestamps on UDP and RAW sockets") Reported-by: syzbot+a90

[PATCH 5.1 084/121] s390/qeth: fix VLAN attribute in bridge_hostnotify udev event

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 335726195e460cb6b3f795b695bfd31f0ea70ef0 ] Enabling sysfs attribute bridge_hostnotify triggers a series of udev events for the MAC addresses of all currently connected peers. In case no VLAN is set for a peer, the device reports the corresponding MAC addresses with VLAN ID 4096.

[PATCH 5.1 097/121] powerpc/bpf: use unsigned division instruction for 64-bit operations

2019-06-24 Thread Greg Kroah-Hartman
From: Naveen N. Rao commit 758f2046ea040773ae8ea7f72dd3bbd8fa984501 upstream. BPF_ALU64 div/mod operations are currently using signed division, unlike BPF_ALU32 operations. Fix the same. DIV64 and MOD64 overflow tests pass with this fix. Fixes: 156d0e290e969c ("powerpc/ebpf/jit: Implement JIT c

[PATCH 5.1 091/121] ovl: fix bogus -Wmaybe-unitialized warning

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 1dac6f5b0ed2601be21bb4e27a44b0c3e667b7f4 ] gcc gets a bit confused by the logic in ovl_setup_trap() and can't figure out whether the local 'trap' variable in the caller was initialized or not: fs/overlayfs/super.c: In function 'ovl_fill_super': fs/overlayfs/super.c:1333:4: error

[PATCH 5.1 082/121] s390/qeth: handle limited IPv4 broadcast in L3 TX path

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 72c87976c5abbf8a834ad85f10d03c0cd58b985c ] When selecting the cast type of a neighbourless IPv4 skb (eg. on a raw socket), qeth_l3 falls back to the packet's destination IP address. For this case we should classify traffic sent to 255.255.255.255 as broadcast. This fixes DHCP req

[PATCH 5.1 094/121] can: flexcan: fix timeout when set small bitrate

2019-06-24 Thread Greg Kroah-Hartman
From: Joakim Zhang commit 247e5356a709eb49a0d95ff2a7f07dac05c8252c upstream. Current we can meet timeout issue when setting a small bitrate like 1 as follows on i.MX6UL EVK board (ipg clock = 66MHZ, per clock = 30MHZ): | root@imx6ul7d:~# ip link set can0 up type can bitrate 1 A link ch

[PATCH 5.1 072/121] drm/arm/hdlcd: Allow a bit of clock tolerance

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 1c810739097fdeb31b393b67a0a1e3d7ffdd9f63 ] On the Arm Juno platform, the HDLCD pixel clock is constrained to 250KHz resolution in order to avoid the tiny System Control Processor spending aeons trying to calculate exact PLL coefficients. This means that modes like my oddball 1600

[PATCH 5.1 093/121] can: xilinx_can: use correct bittiming_const for CAN FD core

2019-06-24 Thread Greg Kroah-Hartman
From: Anssi Hannula commit 904044dd8fff43e289c11a2f90fa532e946a1d8b upstream. Commit 9e5f1b273e6a ("can: xilinx_can: add support for Xilinx CAN FD core") added a new can_bittiming_const structure for CAN FD cores that support larger values for tseg1, tseg2, and sjw than previous Xilinx CAN cores

[PATCH 5.1 096/121] riscv: mm: synchronize MMU after pte change

2019-06-24 Thread Greg Kroah-Hartman
From: ShihPo Hung commit bf587caae305ae3b4393077fb22c98478ee55755 upstream. Because RISC-V compliant implementations can cache invalid entries in TLB, an SFENCE.VMA is necessary after changes to the page table. This patch adds an SFENCE.vma for the vmalloc_fault path. Signed-off-by: ShihPo Hung

[PATCH 5.1 083/121] s390/qeth: check dst entry before use

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 0cd6783d3c7d40be165d1f3c811cedf0e3dfcdf1 ] While qeth_l3 uses netif_keep_dst() to hold onto the dst, a skb's dst may still have been obsoleted (via dst_dev_put()) by the time that we end up using it. The dst then points to the loopback interface, which means the neighbour lookup

[PATCH 5.1 088/121] nvme: Fix u32 overflow in the number of namespace list calculation

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit c8e8c77b3bdbade6e26e8e76595f141ede12b692 ] The Number of Namespaces (nn) field in the identify controller data structure is defined as u32 and the maximum allowed value in NVMe specification is 0xFFFEUL. This change fixes the possible overflow of the DIV_ROUND_UP() operation

[PATCH 5.1 073/121] nvmet: fix data_len to 0 for bdev-backed write_zeroes

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 3562f5d9f21e7779ae442a45197fed6cb247fd22 ] The WRITE ZEROES command has no data transfer so that we need to initialize the struct (nvmet_req *req)->data_len to 0x0. While (nvmet_req *req)->transfer_len is initialized in nvmet_req_init(), data_len will be initialized by nowhere w

[PATCH 5.1 098/121] ARM: imx: cpuidle-imx6sx: Restrict the SW2ISO increase to i.MX6SX

2019-06-24 Thread Greg Kroah-Hartman
From: Fabio Estevam commit b25af2ff7c07bd19af74e3f64ff82e2880d13d81 upstream. Since commit 1e434b703248 ("ARM: imx: update the cpu power up timing setting on i.mx6sx") some characters loss is noticed on i.MX6ULL UART as reported by Christoph Niedermaier. The intention of such commit was to incr

[PATCH 5.1 089/121] ovl: detect overlapping layers

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 146d62e5a5867fbf84490d82455718bfb10fe824 ] Overlapping overlay layers are not supported and can cause unexpected behavior, but overlayfs does not currently check or warn about these configurations. User is not supposed to specify the same directory for upper and lower dirs or fo

[PATCH 5.1 101/121] ARM: dts: am57xx-idk: Remove support for voltage switching for SD card

2019-06-24 Thread Greg Kroah-Hartman
From: Faiz Abbas commit 88a748419b84187fd1da05637b8e5928b04a1e06 upstream. If UHS speed modes are enabled, a compatible SD card switches down to 1.8V during enumeration. If after this a software reboot/crash takes place and on-chip ROM tries to enumerate the SD card, the difference in IO voltage

[PATCH 5.1 100/121] ARM: dts: dra76x: Update MMC2_HS200_MANUAL1 iodelay values

2019-06-24 Thread Greg Kroah-Hartman
From: Faiz Abbas commit c3c0b70cd3f801bded7a548198ee1c9851a0ca82 upstream. Update the MMC2_HS200_MANUAL1 iodelay values to match with the latest dra76x data manual[1]. The new iodelay values will have better marginality and should prevent issues in corner cases. Also this particular pinctrl-arr

[PATCH 5.1 092/121] btrfs: start readahead also in seed devices

2019-06-24 Thread Greg Kroah-Hartman
From: Naohiro Aota commit c4e0540d0ad49c8ceab06cceed1de27c4fe29f6e upstream. Currently, btrfs does not consult seed devices to start readahead. As a result, if readahead zone is added to the seed devices, btrfs_reada_wait() indefinitely wait for the reada_ctl to finish. You can reproduce the hu

[PATCH 5.1 105/121] ovl: make i_ino consistent with st_ino in more cases

2019-06-24 Thread Greg Kroah-Hartman
From: Amir Goldstein commit 6dde1e42f497b2d4e22466f23019016775607947 upstream. Relax the condition that overlayfs supports nfs export, to require that i_ino is consistent with st_ino/d_ino. It is enough to require that st_ino and d_ino are consistent. This fixes the failure of xfstest generic/

[PATCH 5.1 074/121] kbuild: tar-pkg: enable communication with jobserver

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit a6e0487709ded7cd1ba0c390d9771e5cb76a8453 ] The buildtar script might want to invoke a make, so tell the parent make to pass the jobserver token pipe to the subcommand by prefixing the command with a +. This addresses the issue seen here: /bin/sh ../scripts/package/buildtar ta

[PATCH 5.1 090/121] ovl: dont fail with disconnected lower NFS

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 9179c21dc6ed1c993caa5fe4da876a6765c26af7 ] NFS mounts can be disconnected from fs root. Don't fail the overlapping layer check because of this. The check is not authoritative anyway, since topology can change during or after the check. Reported-by: Antti Antinoja Signed-off-b

[PATCH 5.1 103/121] arm64: ssbd: explicitly depend on

2019-06-24 Thread Greg Kroah-Hartman
From: Anisse Astier commit adeaa21a4b6954e878f3f7d1c5659ed9c1fe567a upstream. Fix ssbd.c which depends implicitly on asm/ptrace.h including linux/prctl.h (through for example linux/compat.h, then linux/time.h, linux/seqlock.h, linux/spinlock.h and linux/irqflags.h), and uses PR_SPEC* defines. T

[PATCH 5.1 102/121] arm64/sve: should not depend on

2019-06-24 Thread Greg Kroah-Hartman
From: Anisse Astier commit 35341ca0614ab13e1ef34ad4f29a39e15ef31fa8 upstream. Pulling linux/prctl.h into asm/ptrace.h in the arm64 UAPI headers causes userspace build issues for any program (e.g. strace and qemu) that includes both and when using musl libc: | error: redefinition of 'struct

[PATCH 5.1 099/121] ARM: mvebu_v7_defconfig: fix Ethernet on Clearfog

2019-06-24 Thread Greg Kroah-Hartman
From: Jan Kundrát commit cc538ca4308372e81b824be08561c466b1d73b72 upstream. Compared to kernel 5.0, patches merged for 5.1 added support for A38x' PHY guarded by a config option which was not enabled by default. As a result, there was no eth1 and eth2 on a Solid Run Clearfog Base. Ensure that A

[PATCH 5.1 104/121] KVM: x86/mmu: Allocate PAE root array when using SVMs 32-bit NPT

2019-06-24 Thread Greg Kroah-Hartman
From: Sean Christopherson commit b6b80c78af838bef17501416d5d383fedab0010a upstream. SVM's Nested Page Tables (NPT) reuses x86 paging for the host-controlled page walk. For 32-bit KVM, this means PAE paging is used even when TDP is enabled, i.e. the PAE root array needs to be allocated. Fixes:

[PATCH 5.1 106/121] drm/vmwgfx: Use the backdoor port if the HB port is not available

2019-06-24 Thread Greg Kroah-Hartman
From: Thomas Hellstrom commit cc0ba0d8624f210995924bb57a8b181ce8976606 upstream. The HB port may not be available for various reasons. Either it has been disabled by a config option or by the hypervisor for other reasons. In that case, make sure we have a backup plan and use the backdoor port in

[PATCH 5.1 037/121] dmaengine: sprd: Add validation of current descriptor in irq handler

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 58152b0e573e5581c4b9ef7cf06d2e9fafae27d4 ] When user terminates one DMA channel to free all its descriptors, but at the same time one transaction interrupt was triggered possibly, now we should not handle this interrupt by validating if the 'schan->cur_desc' was set as NULL to av

[PATCH 5.1 035/121] dmaengine: mediatek-cqdma: sleeping in atomic context

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 069b3c4214f27b130d0642f32438560db30f452e ] The mtk_cqdma_poll_engine_done() function takes a true/false parameter where true means it's called from atomic context. There are a couple places where it was set to false but it's actually in atomic context so it should be true. All

[PATCH 5.1 087/121] arm64: Silence gcc warnings about arch ABI drift

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit ebcc5928c5d925b1c8d968d9c89cdb0d0186db17 ] Since GCC 9, the compiler warns about evolution of the platform-specific ABI, in particular relating for the marshaling of certain structures involving bitfields. The kernel is a standalone binary, and of course nobody would be so stupi

[PATCH 5.1 085/121] hwmon: (core) add thermal sensors only if dev->of_node is present

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit c41dd48e21fae3e55b3670ccf2eb562fc1f6a67d ] Drivers may register to hwmon and request for also registering with the thermal subsystem (HWMON_C_REGISTER_TZ). However, some of these driver, e.g. marvell phy, may be probed from Device Tree or being dynamically allocated, and in the l

[PATCH 5.1 039/121] dmaengine: sprd: Fix block length overflow

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 89d03b3c126d683f7b2cd5b07178493993d12448 ] The maximum value of block length is 0x, so if the configured transfer length is more than 0x, that will cause block length overflow to lead a configuration error. Thus we can set block length as the maximum burst length to av

[PATCH 5.1 032/121] ARC: fix build warnings

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 89c92142f75eb80064f5b9f484b1b4d81790 ] | arch/arc/mm/tlb.c:914:2: warning: variable length array 'pd0' is used [-Wvla] | arch/arc/include/asm/cmpxchg.h:95:29: warning: value computed is not used [-Wunused-value] Signed-off-by: Vineet Gupta Signed-off-by: Sasha Levin ---

Re: [PATCH v1] OPP: Fix crashing when current OPP has unsupportable voltage

2019-06-24 Thread Dmitry Osipenko
24.06.2019 10:18, Viresh Kumar пишет: > On 23-06-19, 20:50, Dmitry Osipenko wrote: >> Fix NULL dereference caused by a typo in the code. In particular it >> happens when CPU is running on a frequency which has unsupportable voltage >> (by regulator) defined in the OPP table and a custom set_opp() c

[PATCH 5.1 080/121] udmabuf: actually unmap the scatterlist

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 283f1e383e91d96fe652fad549537ae15cf31d60 ] unmap_udmabuf fails to actually unmap the scatterlist, leaving dangling mappings around. Fixes: fbb0de795078 ("Add udmabuf misc device") Signed-off-by: Lucas Stach Link: http://patchwork.freedesktop.org/patch/msgid/20190604202331.1748

[PATCH 5.1 067/121] net: ethernet: mediatek: Use hw_feature to judge if HWLRO is supported

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 9e4f56f1a7f3287718d0083b5cb85298dc05a5fd ] Should hw_feature as hardware capability flags to check if hardware LRO got support. Signed-off-by: Mark Lee Signed-off-by: Sean Wang Signed-off-by: David S. Miller Signed-off-by: Sasha Levin --- drivers/net/ethernet/mediatek/mtk_e

RE: [PATCH v4 3/5] net: macb: add support for c45 PHY

2019-06-24 Thread Parshuram Raju Thombare
>However, it seems from that comment that you're not talking about real >hardware. Is there no real hardware out there supporting 10G mode with >these proposed driver changes yet? I think there are some 10GBaseT PHY out there, but I don't have any test setup with those. This patch is tested on emu

[PATCH 5.1 078/121] scsi: smartpqi: unlock on error in pqi_submit_raid_request_synchronous()

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit cc8f52609bb4177febade24d11713e20c0893b0a ] We need to drop the "ctrl_info->sync_request_sem" lock before returning. Fixes: 6c223761eb54 ("smartpqi: initial commit of Microsemi smartpqi driver") Signed-off-by: Dan Carpenter Acked-by: Don Brace Signed-off-by: Martin K. Petersen

[PATCH 5.1 075/121] scripts/checkstack.pl: Fix arm64 wrong or unknown architecture

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 4f45d62a52297b10ded963412a158685647ecdec ] The following error occurs for the `make ARCH=arm64 checkstack` case: aarch64-linux-gnu-objdump -d vmlinux $(find . -name '*.ko') | \ perl ./scripts/checkstack.pl arm64 wrong or unknown architecture "arm64" As suggested by Masahiro Yam

[PATCH 5.1 118/121] mac80211: handle deauthentication/disassociation from TDLS peer

2019-06-24 Thread Greg Kroah-Hartman
From: Yu Wang commit 79c92ca42b5a3e0ea172ea2ce8df8e125af237da upstream. When receiving a deauthentication/disassociation frame from a TDLS peer, a station should not disconnect the current AP, but only disable the current TDLS link if it's enabled. Without this change, a TDLS issue can be repro

[PATCH 5.1 109/121] staging: erofs: add requirements field in superblock

2019-06-24 Thread Greg Kroah-Hartman
From: Gao Xiang commit 5efe5137f05bbb4688890620934538c005e7d1d6 upstream. There are some backward incompatible features pending for months, mainly due to on-disk format expensions. However, we should ensure that it cannot be mounted with old kernels. Otherwise, it will causes unexpected behavio

[PATCH 5.1 076/121] net: phylink: avoid reducing support mask

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 77316763321ee4050f0576ffd472183aa90dcb30 ] Avoid reducing the support mask as a result of the interface type selected for SFP modules, or when setting the link settings through ethtool - this should only change when the supported link modes of the hardware combination change. Si

[PATCH 5.1 110/121] Bluetooth: Align minimum encryption key size for LE and BR/EDR connections

2019-06-24 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 Signed-off-by

[PATCH 5.1 108/121] binder: fix possible UAF when freeing buffer

2019-06-24 Thread Greg Kroah-Hartman
From: Todd Kjos commit a370003cc301d4361bae20c9ef615f89bf8d1e8a upstream. There is a race between the binder driver cleaning up a completed transaction via binder_free_transaction() and a user calling binder_ioctl(BC_FREE_BUFFER) to release a buffer. It doesn't matter which is first but they nee

[PATCH 5.1 070/121] drm/arm/mali-dp: Add a loop around the second set CVAL and try 5 times

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 6a88e0c14813d00f8520d0e16cd4136c6cf8b4d4 ] This patch trying to fix monitor freeze issue caused by drm error 'flip_done timed out' on LS1028A platform. this set try is make a loop around the second setting CVAL and try like 5 times before giveing up. Signed-off-by: Wen He Signe

[PATCH 5.1 077/121] scsi: ufs: Check that space was properly alloced in copy_query_response

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit 1c90836f70f9a8ef7b7ad9e1fdd8961903e6ced6 ] struct ufs_dev_cmd is the main container that supports device management commands. In the case of a read descriptor request, we assume that the proper space was allocated in dev_cmd to hold the returning descriptor. This is no longer tr

[PATCH 5.1 079/121] net: ipvlan: Fix ipvlan device tso disabled while NETIF_F_IP_CSUM is set

2019-06-24 Thread Greg Kroah-Hartman
[ Upstream commit ceae266bf0ae6564ac16d086bf749a096fa90ded ] There's some NICs, such as hinic, with NETIF_F_IP_CSUM and NETIF_F_TSO on but NETIF_F_HW_CSUM off. And ipvlan device features will be NETIF_F_TSO on with NETIF_F_IP_CSUM and NETIF_F_IP_CSUM both off as IPVLAN_FEATURES only care about NET

[PATCH 5.1 121/121] x86/resctrl: Dont stop walking closids when a locksetup group is found

2019-06-24 Thread Greg Kroah-Hartman
From: James Morse commit 87d3aa28f345bea77c396855fa5d5fec4c24461f upstream. When a new control group is created __init_one_rdt_domain() walks all the other closids to calculate the sets of used and unused bits. If it discovers a pseudo_locksetup group, it breaks out of the loop. This means any

[PATCH 5.1 119/121] nl80211: fix station_info pertid memory leak

2019-06-24 Thread Greg Kroah-Hartman
From: Andy Strohman commit f77bf4863dc2218362f4227d56af4a5f3f08830c upstream. When dumping stations, memory allocated for station_info's pertid member will leak if the nl80211 header cannot be added to the sk_buff due to insufficient tail room. I noticed this leak in the kmalloc-2048 cache. Cc

[PATCH 5.1 111/121] Bluetooth: Fix regression with minimum encryption key size alignment

2019-06-24 Thread Greg Kroah-Hartman
From: Marcel Holtmann commit 693cd8ce3f882524a5d06f7800dd8492411877b3 upstream. When trying to align the minimum encryption key size requirement for Bluetooth connections, it turns out doing this in a central location in the HCI connection handling code is not possible. Original Bluetooth versi

Re: [PATCH v4 2/5] net: macb: add support for sgmii MAC-PHY interface

2019-06-24 Thread Russell King - ARM Linux admin
On Mon, Jun 24, 2019 at 10:14:41AM +, Parshuram Raju Thombare wrote: > >> >I still don't think this makes much sense, splitting the interface > >> > configuration between here and below. > >> Do you mean splitting mac_config in two *_configure functions ? > >> This was done as per Andrew's sugg

[PATCH 5.1 114/121] fs/namespace: fix unprivileged mount propagation

2019-06-24 Thread Greg Kroah-Hartman
From: Christian Brauner commit d728cf79164bb38e9628d15276e636539f857ef1 upstream. When propagating mounts across mount namespaces owned by different user namespaces it is not possible anymore to move or umount the mount in the less privileged mount namespace. Here is a reproducer: sudo mount

Re: [PATCH RFC 11/14] arm64: Move the ASID allocator code in a separate file

2019-06-24 Thread Will Deacon
On Mon, Jun 24, 2019 at 12:35:35AM +0800, Guo Ren wrote: > On Fri, Jun 21, 2019 at 10:16 PM Catalin Marinas > wrote: > > > > On Wed, Jun 19, 2019 at 07:51:03PM +0800, Guo Ren wrote: > > > On Wed, Jun 19, 2019 at 4:54 PM Julien Grall wrote: > > > > On 6/19/19 9:07 AM, Guo Ren wrote: > > > > > Move

[PATCH 5.1 113/121] x86/vdso: Prevent segfaults due to hoisted vclock reads

2019-06-24 Thread Greg Kroah-Hartman
From: Andy Lutomirski commit ff17bbe0bb405ad8b36e55815d381841f9fdeebc upstream. GCC 5.5.0 sometimes cleverly hoists reads of the pvclock and/or hvclock pages before the vclock mode checks. This creates a path through vclock_gettime() in which no vclock is enabled at all (due to disabled TSC on

[PATCH 5.1 117/121] {nl,mac}80211: allow 4addr AP operation on crypto controlled devices

2019-06-24 Thread Greg Kroah-Hartman
From: Manikanta Pubbisetty commit 33d915d9e8ce811d8958915ccd18d71a66c7c495 upstream. As per the current design, in the case of sw crypto controlled devices, it is the device which advertises the support for AP/VLAN iftype based on it's ability to tranmsit packets encrypted in software (In VLAN f

[PATCH 5.1 116/121] mac80211: drop robust management frames from unknown TA

2019-06-24 Thread Greg Kroah-Hartman
From: Johannes Berg commit 588f7d39b3592a36fb7702ae3b8bdd9be4621e2f upstream. When receiving a robust management frame, drop it if we don't have rx->sta since then we don't have a security association and thus couldn't possibly validate the frame. Cc: sta...@vger.kernel.org Signed-off-by: Johan

[PATCH 5.1 120/121] mac80211: Do not use stack memory with scatterlist for GMAC

2019-06-24 Thread Greg Kroah-Hartman
From: Jouni Malinen commit a71fd9dac23613d96ba3c05619a8ef4fd6cdf9b9 upstream. ieee80211_aes_gmac() uses the mic argument directly in sg_set_buf() and that does not allow use of stack memory (e.g., BUG_ON() is hit in sg_set_buf() with CONFIG_DEBUG_SG). BIP GMAC TX side is fine for this since it c

[PATCH 5.1 115/121] cfg80211: fix memory leak of wiphy device name

2019-06-24 Thread Greg Kroah-Hartman
From: Eric Biggers commit 4f488fbca2a86cc7714a128952eead92cac279ab upstream. In wiphy_new_nm(), if an error occurs after dev_set_name() and device_initialize() have already been called, it's necessary to call put_device() (via wiphy_free()) to avoid a memory leak. Reported-by: syzbot+7fddca2257

[PATCH 5.1 107/121] drm/i915: Dont clobber M/N values during fastset check

2019-06-24 Thread Greg Kroah-Hartman
From: Ville Syrjälä commit 475df5d0f3eb2d031e4505f84d8fba75baaf2e80 upstream. We're now calling intel_pipe_config_compare(..., true) uncoditionally which means we're always going clobber the calculated M/N values with the old values if the fuzzy M/N check passes. That causes problems because the

[PATCH 5.1 112/121] SMB3: retry on STATUS_INSUFFICIENT_RESOURCES instead of failing write

2019-06-24 Thread Greg Kroah-Hartman
From: Steve French commit 8d526d62db907e786fd88948c75d1833d82bd80e upstream. Some servers such as Windows 10 will return STATUS_INSUFFICIENT_RESOURCES as the number of simultaneous SMB3 requests grows (even though the client has sufficient credits). Return EAGAIN on STATUS_INSUFFICIENT_RESOURCE

linux-next: manual merge of the akpm-current tree with the tip tree

2019-06-24 Thread Stephen Rothwell
Hi all, Today's linux-next merge of the akpm-current tree got a conflict in: lib/debugobjects.c between commit: d5f34153e526 ("debugobjects: Move printk out of db->lock critical sections") from the tip tree and commit: 8b6b497dfb11 ("lib/debugobjects.c: move printk out of db lock critic

Re: [PATCH] ACPI / LPSS: Don't skip late system PM ops for hibernate on BYT/CHT

2019-06-24 Thread Rafael J. Wysocki
On Saturday, May 25, 2019 7:31:20 AM CEST Robert R. Howell wrote: > On 5/16/19 5:11 AM, Rafael J. Wysocki wrote: > > > > On Thursday, April 25, 2019 6:38:34 PM CEST Robert R. Howell wrote: > >> On 4/24/19 1:20 AM, Rafael J. Wysocki wrote: > >> > >>> On Tue, Apr 23, 2019 at 10:03 PM Robert R. Howel

Re: [RFC 3/5] livepatch: Allow to distinguish different version of system state changes

2019-06-24 Thread Nicolai Stange
Petr Mladek writes: > --- > include/linux/livepatch.h | 2 ++ > kernel/livepatch/core.c | 8 > kernel/livepatch/state.c | 40 +++- > kernel/livepatch/state.h | 9 + > 4 files changed, 58 insertions(+), 1 deletion(-) > create mode 10064

Re: [PATCH v3 1/2] ceph: fix buffer length handling in virtual xattrs

2019-06-24 Thread Jeff Layton
On Mon, 2019-06-24 at 12:00 +0200, Ilya Dryomov wrote: > On Fri, Jun 21, 2019 at 4:18 PM Jeff Layton wrote: > > The convention with xattrs is to not store the termination with string > > data, given that it returns the length. This is how setfattr/getfattr > > operate. > > > > Most of ceph's virt

[PATCH] linux-next: ktest: Fix typo in ktest.pl

2019-06-24 Thread Masanari Iida
This patch fix some spelling typo in ktest.pl Signed-off-by: Masanari Iida --- tools/testing/ktest/config-bisect.pl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/testing/ktest/config-bisect.pl b/tools/testing/ktest/config-bisect.pl index 72525426654b..6fd86493531

RE: [PATCH v4 2/5] net: macb: add support for sgmii MAC-PHY interface

2019-06-24 Thread Parshuram Raju Thombare
>> >Sorry, this reply doesn't answer my question. I'm not asking about >> >bp->speed and bp->duplex. I'm asking: >> >1) why you are initialising bp->phy_interface here >> >2) you to consider the impact that has on the mac_config() implementation >> > you are proposing >> > because I think it's b

Re: [PATCH 0/3] rtc: pcf8563: Fix unhandled interrupt storm

2019-06-24 Thread Chen-Yu Tsai
On Fri, Jun 21, 2019 at 12:22 AM Alexandre Belloni wrote: > > On 04/06/2019 12:23:34+0800, Chen-Yu Tsai wrote: > > From: Chen-Yu Tsai > > > > Hi everyone, > > > > While bringing up my Pine H64, I encountered an interrupt storm from the > > pcf8563 RTC. The RTC chip's interrupt line is shared with

Re: [PATCH 05/13] vfs: don't parse "silent" option

2019-06-24 Thread David Howells
Miklos Szeredi wrote: > What I'm saying is that with a new interface the rules need not follow > the rules of the old interface, because at the start no one is using > the new interface, so no chance of breaking anything. Er. No. That's not true, since the old interface comes through the new on

Re: [PATCH 1/4] block: add zone open, close and finish support

2019-06-24 Thread Matias Bjørling
On 6/22/19 2:51 AM, Damien Le Moal wrote: Matias, Some comments inline below. On 2019/06/21 22:07, Matias Bjørling wrote: From: Ajay Joshi Zoned block devices allows one to control zone transitions by using explicit commands. The available transitions are: * Open zone: Transition a zone

Re: x86: Spurious vectors not handled robustly

2019-06-24 Thread Thomas Gleixner
On Mon, 24 Jun 2019, Jan Kiszka wrote: > On 24.06.19 12:09, Thomas Gleixner wrote: > > If it is a vectored one it _IS_ acked. > > > > inc_irq_stat(irq_spurious_count); > > > > /* see sw-dev-man vol 3, chapter 7.4.13.5 */ > > pr_info("spurious APIC interrupt through vector %0

Re: x86: Spurious vectors not handled robustly

2019-06-24 Thread Jan Kiszka
On 24.06.19 12:09, Thomas Gleixner wrote: Jan, On Mon, 24 Jun 2019, Jan Kiszka wrote: probably since "x86: Avoid building unused IRQ entry stubs" (2414e021ac8d), the kernel can no longer tell spurious IRQs by the APIC apart from spuriously triggered unused vectors. Err. It does. We've manag

Re: [RFC PATCH] arm64: dts: fsl: wandboard: Add a device tree for the PICO-PI-IMX8M

2019-06-24 Thread Daniel Baluta
Hi Andra, Few comments inline. On Thu, Jun 20, 2019 at 4:35 PM Andra Danciu wrote: > > From: Richard Hu > > The current level of support yields a working console and is able to boot > userspace from an initial ramdisk copied via u-boot in RAM. > > Additional subsystems that are active : >

Re: [PATCH v2] modules: fix BUG when load module with rodata=n

2019-06-24 Thread Jessica Yu
+++ Yang Yingliang [20/06/19 10:18 +0800]: When loading a module with rodata=n, it causes an executing NX-protected page BUG. [ 32.379191] kernel tried to execute NX-protected page - exploit attempt? (uid: 0) [ 32.382917] BUG: unable to handle page fault for address: c0005000 [ 32

Re: [PATCH v4 13/16] PM / devfreq: tegra: Support Tegra30

2019-06-24 Thread Dmitry Osipenko
24.06.2019 10:34, MyungJoo Ham пишет: >> >> A question: >> >> Does this driver support Tegra20 as well? >> I'm asking this because ARCH_TEGRA includes ARCH_TEGRA_2x_SOC >> according to /drivers/soc/tegra/Kconfig. >> > > For this matter, how about updating your 13/16 patch as follows? > > --- > d

Re: [PATCH 0/3] rtc: pcf8563: Fix unhandled interrupt storm

2019-06-24 Thread Alexandre Belloni
On 24/06/2019 18:34:29+0800, Chen-Yu Tsai wrote: > On Fri, Jun 21, 2019 at 12:22 AM Alexandre Belloni > wrote: > > > > On 04/06/2019 12:23:34+0800, Chen-Yu Tsai wrote: > > > From: Chen-Yu Tsai > > > > > > Hi everyone, > > > > > > While bringing up my Pine H64, I encountered an interrupt storm fro

Re: Linux 4.19 and GCC 9

2019-06-24 Thread Ignat Korchagin
Hi Greg, > > For us it seems applying the following 4 mainline patches makes 4.19.x > > branch perf compile with GCC-9: > > > > 4d0f16d059ddb91424480d88473f7392f24aebdc: perf ui helpline: Use > > strlcpy() as a shorter form of strncpy() + explicit set nul > > b6313899f4ed2e76b8375cf8069556f5b94fbf

Re: [PATCH 05/13] vfs: don't parse "silent" option

2019-06-24 Thread Miklos Szeredi
On Mon, Jun 24, 2019 at 12:36 PM David Howells wrote: > > Miklos Szeredi wrote: > > > What I'm saying is that with a new interface the rules need not follow > > the rules of the old interface, because at the start no one is using > > the new interface, so no chance of breaking anything. > > Er. N

Re: [PATCH] drivers: Adjust scope for CONFIG_HAS_IOMEM before devm_platform_ioremap_resource()

2019-06-24 Thread Bartosz Golaszewski
pon., 24 cze 2019 o 12:05 Enrico Weigelt, metux IT consult napisał(a): > > On 24.06.19 10:29, Bartosz Golaszewski wrote: > > pt., 14 cze 2019 o 18:50 Markus Elfring napisał(a): > >> > >> From: Markus Elfring > >> Date: Fri, 14 Jun 2019 17:45:13 +0200 > >> > >> Move the preprocessor statement “#i

Re: [PATCH] ACPI / LPSS: Don't skip late system PM ops for hibernate on BYT/CHT

2019-06-24 Thread Hans de Goede
Hi Rafael, Sorry for the long delay. I haven't dropped this issue on the floor, I hope that you are still able to follow up here. Can you please test the appended patch instead of the previous one? I have found some inconsistencies in the handling of hibernation in the ACPI PM domain and

Re: [PATCH] drivers: Adjust scope for CONFIG_HAS_IOMEM before devm_platform_ioremap_resource()

2019-06-24 Thread Markus Elfring
>> +++ b/drivers/base/platform.c >> @@ -78,6 +78,7 @@ struct resource *platform_get_resource(struct >> platform_device *dev, >> return NULL; >> } >> EXPORT_SYMBOL_GPL(platform_get_resource); >> +#ifdef CONFIG_HAS_IOMEM >> >> /** >> * devm_platform_ioremap_resource - call devm_ioremap_

Re: [PATCH 05/13] vfs: don't parse "silent" option

2019-06-24 Thread Miklos Szeredi
On Mon, Jun 24, 2019 at 12:44 PM Miklos Szeredi wrote: > > On Mon, Jun 24, 2019 at 12:36 PM David Howells wrote: > > > > Miklos Szeredi wrote: > > > > > What I'm saying is that with a new interface the rules need not follow > > > the rules of the old interface, because at the start no one is usi

Re: PREEMPT_RT_FULL on x86-32 machine

2019-06-24 Thread Pavel Machek
Hi! > >Is full preemption supposed to work on x86-32 machines? > > > >Because it does not work for me. It crashes early in boot, no messages > >make it to console. Similar configuration for x86-64 boots ok. > > > > Maybe you can also tell which version(s) you tried, and in which > configuration(s

Re: WARNING: ODEBUG bug in netdev_freemem (2)

2019-06-24 Thread Dmitry Vyukov
On Mon, Jun 24, 2019 at 11:34 AM Thomas Gleixner wrote: > > On Mon, 24 Jun 2019, syzbot wrote: > > > Hello, > > > > syzbot found the following crash on: > > > > HEAD commit:fd6b99fa Merge branch 'akpm' (patches from Andrew) > > git tree: upstream > > console output: https://syzkaller.app

[PATCH] clk: imx8mm: Switch to platform driver

2019-06-24 Thread Abel Vesa
In order to make the clock provider a platform driver all the data and code needs to be outside of .init section. Signed-off-by: Abel Vesa --- drivers/clk/imx/clk-imx8mm.c | 52 +--- 1 file changed, 34 insertions(+), 18 deletions(-) diff --git a/drivers/c

Re: [PATCH] kernel/isolation: Asset that a housekeeping CPU comes up at boot time

2019-06-24 Thread Qais Yousef
On 06/01/19 21:39, Nicholas Piggin wrote: > With the change to allow the boot CPU0 to be isolated, it is possible > to specify command line options that result in no housekeeping CPU > online at boot. > > An 8 CPU system booted with "nohz_full=0-6 maxcpus=4", for example. > > It is not easily pos

Re: PREEMPT_RT_FULL on x86-32 machine

2019-06-24 Thread Jan Kiszka
On 24.06.19 12:53, Pavel Machek wrote: Hi! Is full preemption supposed to work on x86-32 machines? Because it does not work for me. It crashes early in boot, no messages make it to console. Similar configuration for x86-64 boots ok. Maybe you can also tell which version(s) you tried, and in

Re: [PATCHv3 21/23] arm64: dts: qcom: qcs404: Add tsens controller

2019-06-24 Thread Amit Kucheria
On Wed, Mar 20, 2019 at 6:50 PM Amit Kucheria wrote: > > qcs404 has a single TSENS IP block with 10 sensors. The calibration data > is stored in an eeprom (qfprom) that is accessed through the nvmem > framework. We add the qfprom node to allow the tsens sensors to be > calibrated correctly. > > Si

linux-next: build failure after merge of the akpm-current tree

2019-06-24 Thread Stephen Rothwell
Hi Andrew, After merging the akpm-current tree, today's linux-next build (arm multi_v7_defconfig) failed like this: mm/util.c: In function '__account_locked_vm': mm/util.c:372:2: error: implicit declaration of function 'lockdep_assert_held_exclusive'; did you mean 'lockdep_assert_held_once'? [-

Re: drivers: Adjust scope for CONFIG_HAS_IOMEM before devm_platform_ioremap_resource()

2019-06-24 Thread Markus Elfring
> In its current form it makes the code even less readable. This can be your development opinion. > The #ifdef should actually be one line lower I suggested that the conditional compilation can contain also a blank line together with a comment block. > and touch the comment instead of the EXP

Re: [PATCH v3 1/2] ceph: fix buffer length handling in virtual xattrs

2019-06-24 Thread Ilya Dryomov
On Mon, Jun 24, 2019 at 12:26 PM Jeff Layton wrote: > > On Mon, 2019-06-24 at 12:00 +0200, Ilya Dryomov wrote: > > On Fri, Jun 21, 2019 at 4:18 PM Jeff Layton wrote: > > > The convention with xattrs is to not store the termination with string > > > data, given that it returns the length. This is

[PATCH] mm/kasan: Add shadow memory validation in ksize()

2019-06-24 Thread Marco Elver
ksize() has been unconditionally unpoisoning the whole shadow memory region associated with an allocation. This can lead to various undetected bugs, for example, double-kzfree(). kzfree() uses ksize() to determine the actual allocation size, and subsequently zeroes the memory. Since ksize() used t

hello

2019-06-24 Thread eddy william
Mijn naam is Eddy William. Ik ben van beroep advocaat. Ik wil je aanbieden nabestaanden van mijn cliënt. Je ervaart de som van ($ 14,2 miljoen) dollars die mijn cliënt voor zijn overlijden op de bank heeft achtergelaten. Mijn klant is een burger van jouw land die stierf in auto-ongeluk met zijn vr

Re: [PATCH 3/3] module: Properly propagate MODULE_STATE_COMING failure

2019-06-24 Thread Peter Zijlstra
On Mon, Jun 24, 2019 at 11:18:46AM +0200, Peter Zijlstra wrote: > Now that notifiers got unbroken; use the proper interface to handle > notifier errors and propagate them. > > There were already MODULE_STATE_COMING notifiers that failed; notably: > > - jump_label_module_notifier() > - tracepoin

Re: [PATCH v3] mtd: spi-nor: fix nor->addr_width when its value configured from SFDP does not match the actual width

2019-06-24 Thread Vignesh Raghavendra
On 22/06/19 5:19 PM, tudor.amba...@microchip.com wrote: > Hi, Liu, > > On 03/31/2019 10:42 AM, Liu Xiang wrote: > >> Some is25lp256 get BFPT_DWORD1_ADDRESS_BYTES_3_ONLY from BFPT table for >> address width. But in actual fact the flash can support 4-byte address. >> So we should fix it. > > I

Re: [PATCH v1 1/6] ASoC: sgtl5000: Fix definition of VAG Ramp Control

2019-06-24 Thread Marcel Ziswiler
On Wed, 2019-06-19 at 10:00 +, Oleksandr Suvorov wrote: > > > > From: Marcel Ziswiler > > Sent: Thursday, June 13, 2019 12:05 > > To: feste...@gmail.com; Oleksandr Suvorov > > Cc: Igor Opaniuk; linux-kernel@vger.kernel.org; > > alsa-de...@alsa-project.o

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