[PATCH 4.19 091/118] ALSA: seq: Protect in-kernel ioctl calls with mutex

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit feb689025fbb6f0aa6297d3ddf97de945ea4ad32 ] ALSA OSS sequencer calls the ioctl function indirectly via snd_seq_kernel_client_ctl(). While we already applied the protection against races between the normal ioctls and writes via the client's ioctl_mutex, this code path was left unt

Re: [PATCH] io_uring: fix memory leak of UNIX domain socket inode

2019-06-13 Thread Jens Axboe
On 6/12/19 3:58 PM, Eric Biggers wrote: > From: Eric Biggers > > Opening and closing an io_uring instance leaks a UNIX domain socket > inode. This is because the ->file of the io_uring instance's internal > UNIX domain socket is set to point to the io_uring file, but then > sock_release() sees t

[PATCH 4.19 092/118] ARM: OMAP2+: pm33xx-core: Do not Turn OFF CEFUSE as PPA may be using it

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 72aff4ecf1cb85a3c6e6b42ccbda0bc631b090b3 ] This area is used to store keys by HSPPA in case of AM438x SOC. Leave it active. Signed-off-by: Kabir Sahane Signed-off-by: Andrew F. Davis Signed-off-by: Tony Lindgren Signed-off-by: Sasha Levin --- arch/arm/mach-omap2/pm33xx-core

[PATCH 4.19 090/118] drm/amd/display: Use plane->color_space for dpp if specified

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit a1e07ba89d49581471d64c48152dbe03b42bd025 ] [Why] The input color space for the plane was previously ignored even if it was set. If a limited range YUV format was given to DC then the wrong color transformation matrix was being used since DC assumed that it was full range instead

[PATCH 4.19 088/118] ARM: dts: imx6qdl: Specify IMX6QDL_CLK_IPG as "ipg" clock to SDMA

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit b14c872eebc501b9640b04f4a152df51d6eaf2fc ] Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX6QDL_CLK_SDMA re

[PATCH 4.19 089/118] PCI: rpadlpar: Fix leaked device_node references in add/remove paths

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit fb26228bfc4ce3951544848555c0278e2832e618 ] The find_dlpar_node() helper returns a device node with its reference incremented. Both the add and remove paths use this helper for find the appropriate node, but fail to release the reference when done. Annotate the find_dlpar_node()

[PATCH 4.19 084/118] ARM: dts: imx6sll: Specify IMX6SLL_CLK_IPG as "ipg" clock to SDMA

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit c5ed5daa65d5f665e666b76c3dbfa503066defde ] Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX6SLL_CLK_SDMA re

[PATCH 4.19 082/118] ARM: dts: imx53: Specify IMX5_CLK_IPG as "ahb" clock to SDMA

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 28c168018e0902c67eb9c60d0fc4c8aa166c4efe ] Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX5_CLK_SDMA resul

[PATCH 4.19 081/118] ARM: dts: imx50: Specify IMX5_CLK_IPG as "ahb" clock to SDMA

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit b7b4fda2636296471e29b78c2aa9535d7bedb7a0 ] Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX5_CLK_SDMA resul

[PATCH 4.19 083/118] ARM: dts: imx6sx: Specify IMX6SX_CLK_IPG as "ahb" clock to SDMA

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit cc839d0f8c284fcb7591780b568f13415bbb737c ] Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX6SL_CLK_SDMA res

[PATCH 4.19 087/118] ARM: dts: imx6sx: Specify IMX6SX_CLK_IPG as "ipg" clock to SDMA

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 8979117765c19edc3b01cc0ef853537bf93eea4b ] Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX6SX_CLK_SDMA res

[PATCH 4.19 079/118] soc: rockchip: Set the proper PWM for rk3288

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit bbdc00a7de24cc90315b1775fb74841373fe12f7 ] The rk3288 SoC has two PWM implementations available, the "old" implementation and the "new" one. You can switch between the two of them by flipping a bit in the grf. The "old" implementation is the default at chip power up but isn't t

[PATCH 4.19 080/118] ARM: dts: imx51: Specify IMX5_CLK_IPG as "ahb" clock to SDMA

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 918bbde8085ae147a43dcb491953e0dd8f3e9d6a ] Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX5_CLK_SDMA resul

[PATCH 4.19 069/118] vfio: Fix WARNING "do not call blocking ops when !TASK_RUNNING"

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 41be3e2618174fdf3361e49e64f2bf530f40c6b0 ] vfio_dev_present() which is the condition to wait_event_interruptible_timeout(), will call vfio_group_get_device and try to acquire the mutex group->device_lock. wait_event_interruptible_timeout() will set the state of the current task

[PATCH 4.19 078/118] clk: rockchip: Turn on "aclk_dmac1" for suspend on rk3288

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 57a20248ef3e429dc822f0774bc4e00136c46c83 ] Experimentally it can be seen that going into deep sleep (specifically setting PMU_CLR_DMA and PMU_CLR_BUS in RK3288_PMU_PWRMODE_CON1) appears to fail unless "aclk_dmac1" is on. The failure is that the system never signals that it made

Re: [PATCH] PCI: aardvark: Fix PCI_EXP_RTCTL conf register writing

2019-06-13 Thread Lorenzo Pieralisi
On Wed, May 22, 2019 at 11:33:49PM +0200, Remi Pommarel wrote: > PCI_EXP_RTCTL is used to activate PME interrupt only, so writing into it > should not modify other interrupts' mask (such as ISR0). > > Fixes: 6302bf3ef78d ("PCI: Init PCIe feature bits for managed host bridge > alloc") > Signed-off

[PATCH 4.19 085/118] ARM: dts: imx7d: Specify IMX7D_CLK_IPG as "ipg" clock to SDMA

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 412b032a1dc72fc9d1c258800355efa6671b6315 ] Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX7D_CLK_SDMA resu

[PATCH 4.19 086/118] ARM: dts: imx6ul: Specify IMX6UL_CLK_IPG as "ipg" clock to SDMA

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 7b3132ecefdd1fcdf6b86e62021d0e55ea8034db ] Since 25aaa75df1e6 SDMA driver uses clock rates of "ipg" and "ahb" clock to determine if it needs to configure the IP block as operating at 1:1 or 1:2 clock ratio (ACR bit in SDMAARM_CONFIG). Specifying both clocks as IMX6UL_CLK_SDMA res

[PATCH 4.19 035/118] f2fs: fix to avoid panic in f2fs_remove_inode_page()

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 8b6810f8acfe429fde7c7dad4714692cc5f75651 ] As Jungyeon reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203219 - Overview When mounting the attached crafted image and running program, I got this error. Additionally, it hangs on sync after running the program.

Re: [PATCH v17 03/15] arm64: Introduce prctl() options to control the tagged user addresses ABI

2019-06-13 Thread Vincenzo Frascino
On 13/06/2019 16:57, Catalin Marinas wrote: > On Thu, Jun 13, 2019 at 04:45:54PM +0100, Vincenzo Frascino wrote: >> On 13/06/2019 16:35, Catalin Marinas wrote: >>> On Thu, Jun 13, 2019 at 12:16:59PM +0100, Dave P Martin wrote: On Wed, Jun 12, 2019 at 01:43:20PM +0200, Andrey Konovalov wrote:

Re: [PATCH 2/3] mmc: sdhci: sdhci-pci-o2micro: Check if controller supports 8-bit width

2019-06-13 Thread Adrian Hunter
On 12/06/19 6:08 PM, Raul Rangel wrote: > On Wed, Jun 12, 2019 at 04:09:47PM +0300, Adrian Hunter wrote: >> On 10/06/19 9:53 PM, Raul E Rangel wrote: >>> The O2 controller supports 8-bit EMMC access. mmc_select_bus_width() >>> will be used to determine if the MMC supports 8-bit or 4-bit access. >>

[PATCH 4.19 043/118] configfs: fix possible use-after-free in configfs_register_group

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 35399f87e271f7cf3048eab00a421a6519ac8441 ] In configfs_register_group(), if create_default_group() failed, we forget to unlink the group. It will left a invalid item in the parent list, which may trigger the use-after-free issue seen below: BUG: KASAN: use-after-free in __list_a

[PATCH 4.19 068/118] nfsd: avoid uninitialized variable warning

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 0ab88ca4bcf18ba21058d8f19220f60afe0d34d8 ] clang warns that 'contextlen' may be accessed without an initialization: fs/nfsd/nfs4xdr.c:2911:9: error: variable 'contextlen' is uninitialized when used here [-Werror,-Wuninitialized]

[PATCH 4.19 077/118] soc: mediatek: pwrap: Zero initialize rdata in pwrap_init_cipher

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 89e28da82836530f1ac7a3a32fecc31f22d79b3e ] When building with -Wsometimes-uninitialized, Clang warns: drivers/soc/mediatek/mtk-pmic-wrap.c:1358:6: error: variable 'rdata' is used uninitialized whenever '||' condition is true [-Werror,-Wsometimes-uninitialized] If pwrap_write re

[PATCH 4.19 044/118] uml: fix a boot splat wrt use of cpu_all_mask

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 689a58605b63173acb0a8cf954af6a8f60440c93 ] Memory: 509108K/542612K available (3835K kernel code, 919K rwdata, 1028K rodata, 129K init, 211K bss, 33504K reserved, 0K cma-reserved) NR_IRQS: 15 clocksource: timer: mask: 0x max_cycles: 0x1cd42e205, max_idle_ns: 8815

[PATCH 4.19 041/118] f2fs: fix to do checksum even if inode page is uptodate

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit b42b179bda9ff11075a6fc2bac4d9e400513679a ] As Jungyeon reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203221 - Overview When mounting the attached crafted image and running program, this error is reported. The image is intentionally fuzzed from a normal f2f

[PATCH 4.19 040/118] f2fs: fix to do sanity check on valid block count of segment

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit e95bcdb2fefa129f37bd9035af1d234ca92ee4ef ] As Jungyeon reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203233 - Overview When mounting the attached crafted image and running program, following errors are reported. Additionally, it hangs on sync after running

[PATCH 4.19 042/118] percpu: remove spurious lock dependency between percpu and sched

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 198790d9a3aeaef5792d33a560020861126edc22 ] In free_percpu() we sometimes call pcpu_schedule_balance_work() to queue a work item (which does a wakeup) while holding pcpu_lock. This creates an unnecessary lock dependency between pcpu_lock and the scheduler's pi_lock. There are oth

Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets

2019-06-13 Thread Andy Lutomirski
On Wed, Jun 12, 2019 at 6:50 PM Nadav Amit wrote: > > > On Jun 12, 2019, at 6:30 PM, Andy Lutomirski wrote: > > > > On Wed, Jun 12, 2019 at 1:27 PM Andy Lutomirski wrote: > >>> On Jun 12, 2019, at 12:55 PM, Dave Hansen wrote: > >>> > On 6/12/19 10:08 AM, Marius Hillenbrand wrote: > Th

[PATCH 4.19 039/118] f2fs: fix to use inline space only if inline_xattr is enable

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 622927f3b8809206f6da54a6a7ed4df1a7770fce ] With below mkfs and mount option: MKFS_OPTIONS -- -O extra_attr -O project_quota -O inode_checksum -O flexible_inline_xattr -O inode_crtime -f MOUNT_OPTIONS -- -o noinline_xattr We may miss xattr data with below testcase: - mkdir dir

[PATCH 4.19 066/118] fuse: retrieve: cap requested size to negotiated max_write

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 7640682e67b33cab8628729afec8ca92b851394f ] FUSE filesystem server and kernel client negotiate during initialization phase, what should be the maximum write size the client will ever issue. Correspondingly the filesystem server then queues sys_read calls to read requests with buff

PC speaker

2019-06-13 Thread R.F. Burns
Is it possible to write a kernel module which, when loaded, will blow the PC speaker?

[PATCH 4.19 065/118] nvmem: sunxi_sid: Support SID on A83T and H5

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit da75b8909756160b8e785104ba421a20b756c975 ] The device tree binding already lists compatible strings for these two SoCs. They don't have the defect as seen on the H3, and the size and register layout is the same as the A64. Furthermore, the driver does not include nvmem cell defin

[PATCH 4.19 058/118] PCI: designware-ep: Use aligned ATU window for raising MSI interrupts

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 6b7330303a8186fb211357e6d379237fe9d2ece1 ] Certain platforms like K2G reguires the outbound ATU window to be aligned. The alignment size is already present in mem->page_size. Use the alignment size present in mem->page_size to configure an aligned ATU window. In order to raise an

[PATCH 4.19 063/118] ALSA: hda - Register irq handler after the chip initialization

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit f495222e28275222ab6fd93813bd3d462e16d340 ] Currently the IRQ handler in HD-audio controller driver is registered before the chip initialization. That is, we have some window opened between the azx_acquire_irq() call and the CORB/RIRB setup. If an interrupt is triggered in this

[PATCH 4.19 064/118] nvmem: core: fix read buffer in place

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 2fe518fecb3a4727393be286db9804cd82ee2d91 ] When the bit_offset in the cell is zero, the pointer to the msb will not be properly initialized (ie, will still be pointing to the first byte in the buffer). This being the case, if there are bits to clear in the msb, those will be lef

[PATCH 4.19 060/118] nvme-pci: shutdown on timeout during deletion

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 9dc1a38ef1925d23c2933c5867df816386d92ff8 ] We do not restart a controller in a deleting state for timeout errors. When in this state, unblock potential request dispatchers with failed completions by shutting down the controller on timeout detection. Reported-by: Yufen Yu Signed

[PATCH 4.19 059/118] nvme-pci: unquiesce admin queue on shutdown

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit c8e9e9b7646ebe1c5066ddc420d7630876277eb4 ] Just like IO queues, the admin queue also will not be restarted after a controller shutdown. Unquiesce this queue so that we do not block request dispatch on a permanently disabled controller. Reported-by: Yufen Yu Signed-off-by: Keith

[PATCH 4.19 061/118] netfilter: nf_flow_table: check ttl value in flow offload data path

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 33cc3c0cfa64c86b6c4bbee86997aea638534931 ] nf_flow_offload_ip_hook() and nf_flow_offload_ipv6_hook() do not check ttl value. So, ttl value overflow may occur. Fixes: 97add9f0d66d ("netfilter: flow table support for IPv4") Fixes: 0995210753a2 ("netfilter: flow table support for I

[PATCH 4.19 062/118] netfilter: nf_flow_table: fix netdev refcnt leak

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 26a302afbe328ecb7507cae2035d938e6635131b ] flow_offload_alloc() calls nf_route() to get a dst_entry. Internally, nf_route() calls ip_route_output_key() that allocates a dst_entry and holds it. So, a dst_entry should be released by dst_release() if nf_route() is successful. Other

[PATCH 4.19 038/118] f2fs: fix to avoid panic in dec_valid_block_count()

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 5e159cd349bf3a31fb7e35c23a93308eb30f4f71 ] As Jungyeon reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203209 - Overview When mounting the attached crafted image and running program, I got this error. Additionally, it hangs on sync after the this script. The

Re: [PATCH v3] drm/msm/adreno: Add A540 support

2019-06-13 Thread Jordan Crouse
On Tue, Jun 11, 2019 at 11:54:00AM -0700, Jeffrey Hugo wrote: > The A540 is a derivative of the A530, and is found in the MSM8998 SoC. > > Signed-off-by: Jeffrey Hugo This looks correct and more importantly, it seems to work, so there is that. Thanks for doing this; this fills in a sizable gap i

[PATCH 4.19 049/118] netfilter: nf_flow_table: fix missing error check for rhashtable_insert_fast

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 43c8f131184faf20c07221f3e09724611c6525d8 ] rhashtable_insert_fast() may return an error value when memory allocation fails, but flow_offload_add() does not check for errors. This patch just adds missing error checking. Fixes: ac2a5e23 ("netfilter: add generic flow table infr

Re: infinite loop in read_hpet from ktime_get_boot_fast_ns

2019-06-13 Thread Jason A. Donenfeld
Hey Arnd, On Thu, Jun 13, 2019 at 5:40 PM Arnd Bergmann wrote: > A seqlock is a very cheap synchronization primitive, I would actually > guess that this is faster than most implementations of sched_clock() > that access a hardware register for reading the time. It appears to me that ktime_get_co

[PATCH 4.19 055/118] blk-mq: move cancel of requeue_work into blk_mq_release

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit fbc2a15e3433058582e5635aabe48a3011a644a8 ] With holding queue's kobject refcount, it is safe for driver to schedule requeue. However, blk_mq_kick_requeue_list() may be called after blk_sync_queue() is done because of concurrent requeue activities, then requeue work may not be com

[PATCH 4.19 057/118] misc: pci_endpoint_test: Fix test_reg_bar to be updated in pci_endpoint_test

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 8f220664570e755946db1282f48e07f26e1f2cb4 ] commit 834b90519925 ("misc: pci_endpoint_test: Add support for PCI_ENDPOINT_TEST regs to be mapped to any BAR") while adding test_reg_bar in order to map PCI_ENDPOINT_TEST regs to be mapped to any BAR failed to update test_reg_bar in pci

[PATCH 4.19 037/118] f2fs: fix to clear dirty inode in error path of f2fs_iget()

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 546d22f070d64a7b96f57c9772085d3a5e6d ] As Jungyeon reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203217 - Overview When mounting the attached crafted image and running program, I got this error. Additionally, it hangs on sync after running the program.

[PATCH 4.19 052/118] netfilter: nf_tables: fix base chain stat rcu_dereference usage

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit edbd82c5fba009f68d20b5db585be1e667c605f6 ] Following splat gets triggered when nfnetlink monitor is running while xtables-nft selftests are running: net/netfilter/nf_tables_api.c:1272 suspicious rcu_dereference_check() usage! other info that might help us debug this: 1 lock hel

[PATCH 4.19 050/118] netfilter: nf_conntrack_h323: restore boundary check correctness

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit f5e85ce8e733c2547827f6268136b70b802eabdb ] Since commit bc7d811ace4a ("netfilter: nf_ct_h323: Convert CHECK_BOUND macro to function"), NAT traversal for H.323 doesn't work, failing to parse H323-UserInformation. nf_h323_error_boundary() compares contents of the bitstring, not the

[PATCH 4.19 051/118] mips: Make sure dt memory regions are valid

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 93fa5b280761a4dbb14c5330f260380385ab2b49 ] There are situations when memory regions coming from dts may be too big for the platform physical address space. This especially concerns XPA-capable systems. Bootloader may determine more than 4GB memory available and pass it to the ker

[PATCH 4.19 053/118] watchdog: imx2_wdt: Fix set_timeout for big timeout values

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit b07e228eee69601addba98b47b1a3850569e5013 ] The documentated behavior is: if max_hw_heartbeat_ms is implemented, the minimum of the set_timeout argument and max_hw_heartbeat_ms should be used. This patch implements this behavior. Previously only the first 7bits were used and the i

[PATCH 4.19 056/118] iommu/vt-d: Set intel_iommu_gfx_mapped correctly

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit cf1ec4539a50bdfe688caad4615ca47646884316 ] The intel_iommu_gfx_mapped flag is exported by the Intel IOMMU driver to indicate whether an IOMMU is used for the graphic device. In a virtualized IOMMU environment (e.g. QEMU), an include-all IOMMU is used for graphic device. This flag

[PATCH 4.19 048/118] mmc: mmci: Prevent polling for busy detection in IRQ context

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 8520ce1e17799b220ff421d4f39438c9c572ade3 ] The IRQ handler, mmci_irq(), loops until all status bits have been cleared. However, the status bit signaling busy in variant->busy_detect_flag, may be set even if busy detection isn't monitored for the current request. This may be the

[PATCH 4.19 046/118] PCI: dwc: Free MSI IRQ page in dw_pcie_free_msi()

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit dc69a3d567941784c3d00e1d0834582b42b0b3e7 ] To avoid a memory leak, free the page allocated for MSI IRQ in dw_pcie_free_msi(). Signed-off-by: Jisheng Zhang Signed-off-by: Lorenzo Pieralisi Signed-off-by: Bjorn Helgaas Acked-by: Gustavo Pimentel Signed-off-by: Sasha Levin ---

[PATCH 4.19 047/118] ovl: do not generate duplicate fsnotify events for "fake" path

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit d989903058a83e8536cc7aadf9256a47d5c173fe ] Overlayfs "fake" path is used for stacked file operations on underlying files. Operations on files with "fake" path must not generate fsnotify events with path data, because those events have already been generated at overlayfs layer an

[PATCH 4.19 036/118] f2fs: fix to do sanity check on free nid

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 626bcf2b7ce87211dba565f2bfa7842ba5be5c1b ] As Jungyeon reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203225 - Overview When mounting the attached crafted image and unmounting it, following errors are reported. Additionally, it hangs on sync after unmounting

[PATCH 4.19 045/118] PCI: dwc: Free MSI in dw_pcie_host_init() error path

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 9e2b5de5604a6ff2626c51e77014d92c9299722c ] If we ever did MSI-related initializations, we need to call dw_pcie_free_msi() in the error code path. Remove the IS_ENABLED(CONFIG_PCI_MSI) check for MSI init because pci_msi_enabled() already has a stub for !CONFIG_PCI_MSI. Signed-of

Re: [PATCH 1/4] media: cxd2820r: don't check retval after our own assignemt

2019-06-13 Thread Wolfram Sang
> In the title/subject: > > media: cxd2820r: don't check retval after our own assignemt > > s/assignemt/assignment/ Eeeks, in deed :( Shall I resend? Sorry for the noise. signature.asc Description: PGP signature

[PATCH 4.19 012/118] mm/cma.c: fix the bitmap status to show failed allocation reason

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 2b59e01a3aa665f751d1410b99fae9336bd424e1 ] Currently one bit in cma bitmap represents number of pages rather than one page, cma->count means cma size in pages. So to find available pages via find_next_zero_bit()/find_next_bit() we should use cma size not in pages but in bits alth

[PATCH 4.19 015/118] mm/slab.c: fix an infinite loop in leaks_show()

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 745e10146c31b1c6ed3326286704ae251b17f663 ] "cat /proc/slab_allocators" could hang forever on SMP machines with kmemleak or object debugging enabled due to other CPUs running do_drain() will keep making kmemleak_object or debug_objects_cache dirty and unable to escape the first lo

[PATCH 4.19 011/118] initramfs: free initrd memory if opening /initrd.image fails

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 54c7a8916a887f357088f99e9c3a7720cd57d2c8 ] Patch series "initramfs tidyups". I've spent some time chasing down behavior in initramfs and found plenty of opportunity to improve the code. A first stab on that is contained in this series. This patch (of 7): We free the initrd me

[PATCH 4.19 014/118] mm/cma_debug.c: fix the break condition in cma_maxchunk_get()

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit f0fd50504a54f5548eb666dc16ddf8394e44e4b7 ] If not find zero bit in find_next_zero_bit(), it will return the size parameter passed in, so the start bit should be compared with bitmap_maxno rather than cma->count. Although getting maxchunk is working fine due to zero value of orde

[PATCH 4.19 006/118] ARM: prevent tracing IPI_CPU_BACKTRACE

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit be167862ae7dd85c56d385209a4890678e1b0488 ] Patch series "compiler: allow all arches to enable CONFIG_OPTIMIZE_INLINING", v3. This patch (of 11): When function tracing for IPIs is enabled, we get a warning for an overflow of the ipi_types array with the IPI_CPU_BACKTRACE type as

[PATCH 4.19 013/118] mm: page_mkclean vs MADV_DONTNEED race

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 024eee0e83f0df52317be607ca521e0fc572aa07 ] MADV_DONTNEED is handled with mmap_sem taken in read mode. We call page_mkclean without holding mmap_sem. MADV_DONTNEED implies that pages in the region are unmapped and subsequent access to the pages in that range is handled as a new

[PATCH 4.19 025/118] drm/bridge: adv7511: Fix low refresh rate selection

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 67793bd3b3948dc8c8384b6430e036a30a0ecb43 ] The driver currently sets register 0xfb (Low Refresh Rate) based on the value of mode->vrefresh. Firstly, this field is specified to be in Hz, but the magic numbers used by the code are Hz * 1000. This essentially leads to the low refres

[PATCH 4.19 028/118] bpf: fix undefined behavior in narrow load handling

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit e2f7fc0ac6957cabff4cecf6c721979b571af208 ] Commit 31fd85816dbe ("bpf: permits narrower load from bpf program context fields") made the verifier add AND instructions to clear the unwanted bits with a mask when doing a narrow load. The mask is computed with (1 << size * 8) - 1

[PATCH 4.19 010/118] mm/cma.c: fix crash on CMA allocation if bitmap allocation fails

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 1df3a339074e31db95c4790ea9236874b13ccd87 ] f022d8cb7ec7 ("mm: cma: Don't crash on allocation if CMA area can't be activated") fixes the crash issue when activation fails via setting cma->count as 0, same logic exists if bitmap allocation fails. Link: http://lkml.kernel.org/r/201

[PATCH 4.19 033/118] f2fs: fix to avoid panic in do_recover_data()

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 22d61e286e2d9097dae36f75ed48801056b77cac ] As Jungyeon reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203227 - Overview When mounting the attached crafted image, following errors are reported. Additionally, it hangs on sync after trying to mount it. The imag

[PATCH 4.19 027/118] drm/nouveau/kms/gv100-: fix spurious window immediate interlocks

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit d2434e4d942c32cadcbdbcd32c58f35098f3b604 ] Cursor position updates were accidentally causing us to attempt to interlock window with window immediate, and without a matching window immediate update, NVDisplay could hang forever in some circumstances. Fixes suspend/resume on (at l

[PATCH 4.19 034/118] f2fs: fix to avoid panic in f2fs_inplace_write_data()

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 05573d6ccf702df549a7bdeabef31e4753df1a90 ] As Jungyeon reported in bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=203239 - Overview When mounting the attached crafted image and running program, following errors are reported. Additionally, it hangs on sync after running

[PATCH 4.19 008/118] hugetlbfs: on restore reserve error path retain subpool reservation

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 0919e1b69ab459e06df45d3ba6658d281962db80 ] When a huge page is allocated, PagePrivate() is set if the allocation consumed a reservation. When freeing a huge page, PagePrivate is checked. If set, it indicates the reservation should be restored. PagePrivate being set at free huge

[PATCH 4.19 030/118] pwm: meson: Use the spin-lock only to protect register modifications

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit f173747fffdf037c791405ab4f1ec0eb392fc48e ] Holding the spin-lock for all of the code in meson_pwm_apply() can result in a "BUG: scheduling while atomic". This can happen because clk_get_rate() (which is called from meson_pwm_calc()) may sleep. Only hold the spin-lock when modifyi

[PATCH 4.19 031/118] mailbox: stm32-ipcc: check invalid irq

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 68a1c8485cf83734d4da9d81cd3b5d2ae7c0339b ] On failure of_irq_get() returns a negative value or zero, which is not handled as an error in the existing implementation. Instead of using this API, use platform_get_irq() that returns exclusively a negative value on failure. Also, do n

[PATCH 4.19 032/118] ntp: Allow TAI-UTC offset to be set to zero

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit fdc6bae940ee9eb869e493990540098b8c0fd6ab ] The ADJ_TAI adjtimex mode sets the TAI-UTC offset of the system clock. It is typically set by NTP/PTP implementations and it is automatically updated by the kernel on leap seconds. The initial value is zero (which applications may interp

[PATCH 4.19 029/118] EDAC/mpc85xx: Prevent building as a module

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 2b8358a951b1e2a534a54924cd8245e58a1c5fb8 ] The mpc85xx EDAC driver can be configured as a module but then fails to build because it uses two unexported symbols: ERROR: ".pci_find_hose_for_OF_device" [drivers/edac/mpc85xx_edac_mod.ko] undefined! ERROR: ".early_find_capabilit

[PATCH 4.19 009/118] mem-hotplug: fix node spanned pages when we have a node with only ZONE_MOVABLE

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 299c83dce9ea3a79bb4b5511d2cb996b6b8e5111 ] 342332e6a925 ("mm/page_alloc.c: introduce kernelcore=mirror option") and later patches rewrote the calculation of node spanned pages. e506b99696a2 ("mem-hotplug: fix node spanned pages when we have a movable node"), but the current code

[PATCH 4.19 020/118] mfd: intel-lpss: Set the device in reset state when init

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit dad06532292d77f37fbe831a02948a593500f682 ] In virtualized setup, when system reboots due to warm reset interrupt storm is seen. Call Trace: dump_stack+0x70/0xa5 __report_bad_irq+0x2e/0xc0 note_interrupt+0x248/0x290 ? add_interrupt_randomness+0x30/0x220 handle_irq_event_percpu+0

[PATCH 4.19 021/118] drm/nouveau/disp/dp: respect sink limits when selecting failsafe link configuration

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 13d03e9daf70dab032c03dc172e75bb98ad899c4 ] Where possible, we want the failsafe link configuration (one which won't hang the OR during modeset because of not enough bandwidth for the mode) to also be supported by the sink. This prevents "link rate unsupported by sink" messages w

[PATCH 4.19 022/118] mfd: twl6040: Fix device init errors for ACCCTL register

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 48171d0ea7caccf21c9ee3ae75eb370f2a756062 ] I noticed that we can get a -EREMOTEIO errors on at least omap4 duovero: twl6040 0-004b: Failed to write 2d = 19: -121 And then any following register access will produce errors. There 2d offset above is register ACCCTL that gets writ

[PATCH 4.19 024/118] drm/nouveau/kms/gf119-gp10x: push HeadSetControlOutputResource() mthd when encoders change

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit a0b694d0af21c9993d1a39a75fd814bd48bf7eb4 ] HW has error checks in place which check that pixel depth is explicitly provided on DP, while HDMI has a "default" setting that we use. In multi-display configurations with identical modelines, but different protocols (HDMI + DP, in thi

[ANNOUNCE] trace-cmd v2.8

2019-06-13 Thread Steven Rostedt
Finally, after a long time, trace-cmd version 2.8 is released! This will give us a path to release KernelShark 1.0 (after we fix a few more bugs). http://trace-cmd.org Enjoy! -- Steve Features since 2.7: o Restructure of the source directory layout o Loading of plugins from build direct

[PATCH 4.19 023/118] perf/x86/intel: Allow PEBS multi-entry in watermark mode

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit c7a286577d7592720c2f179aadfb325a1ff48c95 ] This patch fixes a restriction/bug introduced by: 583feb08e7f7 ("perf/x86/intel: Fix handling of wakeup_events for multi-entry PEBS") The original patch prevented using multi-entry PEBS when wakeup_events != 0. However given that w

Re: [RFC 00/10] Process-local memory allocations for hiding KVM secrets

2019-06-13 Thread Dave Hansen
On 6/13/19 9:13 AM, Andy Lutomirski wrote: >> It might make sense to use it for kmap_atomic() for debug purposes, as >> it ensures that other users can no longer access the same mapping >> through the linear map. However, it does come at quite a big cost, as we >> need to shoot down the TLB of all

[PATCH 4.19 026/118] objtool: Dont use ignore flag for fake jumps

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit e6da9567959e164f82bc81967e0d5b10dee870b4 ] The ignore flag is set on fake jumps in order to keep add_jump_destinations() from setting their jump_dest, since it already got set when the fake jump was created. But using the ignore flag is a bit of a hack. It's normally used to sk

[PATCH 4.19 019/118] mfd: tps65912-spi: Add missing of table registration

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 9e364e87ad7f2c636276c773d718cda29d62b741 ] MODULE_DEVICE_TABLE(of, should be called to complete DT OF mathing mechanism and register it. Before this patch: modinfo drivers/mfd/tps65912-spi.ko | grep alias alias: spi:tps65912 After this patch: modinfo drivers/mfd/tps65

[PATCH 4.19 018/118] drivers: thermal: tsens: Dont print error message on -EPROBE_DEFER

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit fc7d18cf6a923cde7f5e7ba2c1105bb106d3e29a ] We print a calibration failure message on -EPROBE_DEFER from nvmem/qfprom as follows: [3.003090] qcom-tsens 4a9000.thermal-sensor: version: 1.4 [3.005376] qcom-tsens 4a9000.thermal-sensor: tsens calibration failed [3.113248]

[PATCH 4.19 017/118] thermal: rcar_gen3_thermal: disable interrupt in .remove

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 63f55fcea50c25ae5ad45af92d08dae3b84534c2 ] Currently IRQ remains enabled after .remove, later if device is probed, IRQ is requested before .thermal_init, this may cause IRQ function be called before device is initialized. this patch disables interrupt in .remove, to ensure irq f

[PATCH 4.19 016/118] kernel/sys.c: prctl: fix false positive in validate_prctl_map()

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit a9e73998f9d705c94a8dca9687633adc0f24a19a ] While validating new map we require the @start_data to be strictly less than @end_data, which is fine for regular applications (this is why this nit didn't trigger for that long). These members are set from executable loaders such as el

[PATCH 4.19 007/118] mm/hmm: select mmu notifier when selecting HMM

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 734fb89968900b5c5f8edd5038bd4cdeab8c61d2 ] To avoid random config build issue, select mmu notifier when HMM is selected. In any cases when HMM get selected it will be by users that will also wants the mmu notifier. Link: http://lkml.kernel.org/r/20190403193318.16478-2-jgli...@r

[PATCH 4.19 000/118] 4.19.51-stable review

2019-06-13 Thread Greg Kroah-Hartman
This is the start of the stable review cycle for the 4.19.51 release. There are 118 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Sat 15 Jun 2019 07:54:44 AM UTC. Anything re

[PATCH 4.19 005/118] drm/pl111: Initialize clock spinlock early

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 3e01ae2612bdd7975c74ec7123d7f8f5e6eed795 ] The following warning is seen on systems with broken clock divider. INFO: trying to register non-static key. the code is fine but needs lockdep annotation. turning off the locking correctness validator. CPU: 0 PID: 1 Comm: swapper Not t

[PATCH 4.19 004/118] ipc: prevent lockup on alloc_msg and free_msg

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit d6a2946a88f524a47cc9b79279667137899db807 ] msgctl10 of ltp triggers the following lockup When CONFIG_KASAN is enabled on large memory SMP systems, the pages initialization can take a long time, if msgctl10 requests a huge block memory, and it will block rcu scheduler, so release

[PATCH 4.19 002/118] fs/fat/file.c: issue flush after the writeback of FAT

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit bd8309de0d60838eef6fb575b0c4c7e95841cf73 ] fsync() needs to make sure the data & meta-data of file are persistent after the return of fsync(), even when a power-failure occurs later. In the case of fat-fs, the FAT belongs to the meta-data of file, so we need to issue a flush aft

[PATCH 4.19 001/118] rapidio: fix a NULL pointer dereference when create_workqueue() fails

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 23015b22e47c5409620b1726a677d69e5cd032ba ] In case create_workqueue fails, the fix releases resources and returns -ENOMEM to avoid NULL pointer dereference. Signed-off-by: Kangjie Lu Acked-by: Alexandre Bounine Cc: Matt Porter Signed-off-by: Andrew Morton Signed-off-by: Linu

[PATCH 4.19 003/118] sysctl: return -EINVAL if val violates minmax

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit e260ad01f0aa9e96b5386d5cd7184afd949dc457 ] Currently when userspace gives us a values that overflow e.g. file-max and other callers of __do_proc_doulongvec_minmax() we simply ignore the new value and leave the current value untouched. This can be problematic as it gives the ill

[PATCH 4.14 64/81] PCI: rcar: Fix a potential NULL pointer dereference

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit f0d14edd2ba43b995bef4dd5da5ffe0ae19321a1 ] In case __get_free_pages() fails and returns NULL, fix the return value to -ENOMEM and release resources to avoid dereferencing a NULL pointer. Signed-off-by: Kangjie Lu Signed-off-by: Lorenzo Pieralisi Reviewed-by: Ulrich Hecht Revi

[PATCH 4.14 73/81] ARM: dts: exynos: Always enable necessary APIO_1V8 and ABB_1V8 regulators on Arndale Octa

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 5ab99cf7d5e96e3b727c30e7a8524c976bd3723d ] The PVDD_APIO_1V8 (LDO2) and PVDD_ABB_1V8 (LDO8) regulators were turned off by Linux kernel as unused. However they supply critical parts of SoC so they should be always on: 1. PVDD_APIO_1V8 supplies SYS pins (gpx[0-3], PSHOLD), HDMI l

Re: [PATCH 2/2] nbd: add support for nbd as root device

2019-06-13 Thread Roman Stratiienko
> I don't doubt you have a good reason to want it, I'm just not clear on why an > initramfs isn't an option? You have this special kernel with your special > option, and you manage to get these things to boot your special kernel right? > So why is a initramfs with a tiny nbd-client binary in there

[PATCH 4.14 70/81] gpio: gpio-omap: add check for off wake capable gpios

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit da38ef3ed10a09248e13ae16530c2c6d448dc47d ] We are currently assuming all GPIOs are non-wakeup capable GPIOs as we not configuring the bank->non_wakeup_gpios like we used to earlier with platform_data. Let's add omap_gpio_is_off_wakeup_capable() to make the handling clearer while

[PATCH 4.14 71/81] dmaengine: idma64: Use actual device for DMA transfers

2019-06-13 Thread Greg Kroah-Hartman
[ Upstream commit 5ba846b1ee0792f5a596b9b0b86d6e8cdebfab06 ] Intel IOMMU, when enabled, tries to find the domain of the device, assuming it's a PCI one, during DMA operations, such as mapping or unmapping. Since we are splitting the actual PCI device to couple of children via MFD framework (see dr

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