{"push_id":3076012281,"size":125,"distinct_size":0,"ref":"refs/heads/linaro/linux-linaro-lsk-v4.14","head":"014ab32c4b34d4c582d40b9ecfe5a043f893db47","before":"fcd6ddcefcac8da56fb3d5a4ef815ea115890d5c","commits":[{"sha":"90c68f716d57886f4e6f3ff7c7c07014b4254745","author":{"name":"Christophe Leroy","email":"4e2d3d12816ace76f1cfa36c1816509bd24cf089@c-s.fr"},"message":"powerpc/traps: restore recoverability of machine_check interrupts\n\n[ Upstream commit daf00ae71dad8aa05965713c62558aeebf2df48e ]\n\ncommit b96672dd840f (\"powerpc: Machine check interrupt is a non-\nmaskable interrupt\") added a call to nmi_enter() at the beginning of\nmachine check restart exception handler. Due to that, in_interrupt()\nalways returns true regardless of the state before entering the\nexception, and die() panics even when the system was not already in\ninterrupt.\n\nThis patch calls nmi_exit() before calling die() in order to restore\nthe interrupt state we had before calling nmi_enter()\n\nFixes: b96672dd840f (\"powerpc: Machine check interrupt is a non-maskable interrupt\")\nSigned-off-by: Christophe Leroy <christophe.leroy@c-s.fr>\nReviewed-by: Nicholas Piggin <npiggin@gmail.com>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/90c68f716d57886f4e6f3ff7c7c07014b4254745"},{"sha":"2b9aed7cb2e2dd48092ce1950a0c4bdd792a19d3","author":{"name":"Nicholas Piggin","email":"24829078df5003d9dd1dd871ca2aeb0b1cf95ef4@gmail.com"},"message":"powerpc/64/module: REL32 relocation range check\n\n[ Upstream commit b851ba02a6f3075f0f99c60c4bc30a4af80cf428 ]\n\nThe recent module relocation overflow crash demonstrated that we\nhave no range checking on REL32 relative relocations. This patch\nimplements a basic check, the same kernel that previously oopsed\nand rebooted now continues with some of these errors when loading\nthe module:\n\n  module_64: x_tables: REL32 527703503449812 out of range!\n\nPossibly other relocations (ADDR32, REL16, TOC16, etc.) should also have\noverflow checks.\n\nSigned-off-by: Nicholas Piggin <npiggin@gmail.com>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/2b9aed7cb2e2dd48092ce1950a0c4bdd792a19d3"},{"sha":"0b1f1204554e4ade5af9ea8d59ce6b59ef95e894","author":{"name":"Michael Ellerman","email":"864f124608374e06e4da1fa5d2e47ed839b95411@ellerman.id.au"},"message":"powerpc/mm: Fix page table dump to work on Radix\n\n[ Upstream commit 0d923962ab69c27cca664a2d535e90ef655110ca ]\n\nWhen we're running on Book3S with the Radix MMU enabled the page table\ndump currently prints the wrong addresses because it uses the wrong\nstart address.\n\nFix it to use PAGE_OFFSET rather than KERN_VIRT_START.\n\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/0b1f1204554e4ade5af9ea8d59ce6b59ef95e894"},{"sha":"211981e7e186dd3d9119a4f9f90633a677a2d58b","author":{"name":"Sam Bobroff","email":"5005bd85686edd02bd9a1854bd2a0bebf4ce34dd@linux.ibm.com"},"message":"powerpc/eeh: Fix possible null deref in eeh_dump_dev_log()\n\n[ Upstream commit f9bc28aedfb5bbd572d2d365f3095c1becd7209b ]\n\nIf an error occurs during an unplug operation, it's possible for\neeh_dump_dev_log() to be called when edev->pdn is null, which\ncurrently leads to dereferencing a null pointer.\n\nHandle this by skipping the error log for those devices.\n\nSigned-off-by: Sam Bobroff <sbobroff@linux.ibm.com>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/211981e7e186dd3d9119a4f9f90633a677a2d58b"},{"sha":"8c5800cdb75c354ec0224f0fbab9e4c604b065c0","author":{"name":"Miles Chen","email":"b187a429f4445a58d0c83c03f2ee85d69c8b3f0f@mediatek.com"},"message":"tty: check name length in tty_find_polling_driver()\n\n[ Upstream commit 33a1a7be198657c8ca26ad406c4d2a89b7162bcc ]\n\nThe issue is found by a fuzzing test.\nIf tty_find_polling_driver() recevies an incorrect input such as\n',,' or '0b', the len becomes 0 and strncmp() always return 0.\nIn this case, a null p->ops->poll_init() is called and it causes a kernel\npanic.\n\nFix this by checking name length against zero in tty_find_polling_driver().\n\n$echo ,, > /sys/module/kgdboc/parameters/kgdboc\n[   20.804451] WARNING: CPU: 1 PID: 104 at drivers/tty/serial/serial_core.c:457\nuart_get_baud_rate+0xe8/0x190\n[   20.804917] Modules linked in:\n[   20.805317] CPU: 1 PID: 104 Comm: sh Not tainted 4.19.0-rc7ajb #8\n[   20.805469] Hardware name: linux,dummy-virt (DT)\n[   20.805732] pstate: 20000005 (nzCv daif -PAN -UAO)\n[   20.805895] pc : uart_get_baud_rate+0xe8/0x190\n[   20.806042] lr : uart_get_baud_rate+0xc0/0x190\n[   20.806476] sp : ffffffc06acff940\n[   20.806676] x29: ffffffc06acff940 x28: 0000000000002580\n[   20.806977] x27: 0000000000009600 x26: 0000000000009600\n[   20.807231] x25: ffffffc06acffad0 x24: 00000000ffffeff0\n[   20.807576] x23: 0000000000000001 x22: 0000000000000000\n[   20.807807] x21: 0000000000000001 x20: 0000000000000000\n[   20.808049] x19: ffffffc06acffac8 x18: 0000000000000000\n[   20.808277] x17: 0000000000000000 x16: 0000000000000000\n[   20.808520] x15: ffffffffffffffff x14: ffffffff00000000\n[   20.808757] x13: ffffffffffffffff x12: 0000000000000001\n[   20.809011] x11: 0101010101010101 x10: ffffff880d59ff5f\n[   20.809292] x9 : ffffff880d59ff5e x8 : ffffffc06acffaf3\n[   20.809549] x7 : 0000000000000000 x6 : ffffff880d59ff5f\n[   20.809803] x5 : 0000000080008001 x4 : 0000000000000003\n[   20.810056] x3 : ffffff900853e6b4 x2 : dfffff9000000000\n[   20.810693] x1 : ffffffc06acffad0 x0 : 0000000000000cb0\n[   20.811005] Call trace:\n[   20.811214]  uart_get_baud_rate+0xe8/0x190\n[   20.811479]  serial8250_do_set_termios+0xe0/0x6f4\n[   20.811719]  serial8250_set_termios+0x48/0x54\n[   20.811928]  uart_set_options+0x138/0x1bc\n[   20.812129]  uart_poll_init+0x114/0x16c\n[   20.812330]  tty_find_polling_driver+0x158/0x200\n[   20.812545]  configure_kgdboc+0xbc/0x1bc\n[   20.812745]  param_set_kgdboc_var+0xb8/0x150\n[   20.812960]  param_attr_store+0xbc/0x150\n[   20.813160]  module_attr_store+0x40/0x58\n[   20.813364]  sysfs_kf_write+0x8c/0xa8\n[   20.813563]  kernfs_fop_write+0x154/0x290\n[   20.813764]  vfs_write+0xf0/0x278\n[   20.813951]  __arm64_sys_write+0x84/0xf4\n[   20.814400]  el0_svc_common+0xf4/0x1dc\n[   20.814616]  el0_svc_handler+0x98/0xbc\n[   20.814804]  el0_svc+0x8/0xc\n[   20.822005] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000\n[   20.826913] Mem abort info:\n[   20.827103]   ESR = 0x84000006\n[   20.827352]   Exception class = IABT (current EL), IL = 16 bits\n[   20.827655]   SET = 0, FnV = 0\n[   20.827855]   EA = 0, S1PTW = 0\n[   20.828135] user pgtable: 4k pages, 39-bit VAs, pgdp = (____ptrval____)\n[   20.828484] [0000000000000000] pgd=00000000aadee003, pud=00000000aadee003, pmd=0000000000000000\n[   20.829195] Internal error: Oops: 84000006 [#1] SMP\n[   20.829564] Modules linked in:\n[   20.829890] CPU: 1 PID: 104 Comm: sh Tainted: G        W         4.19.0-rc7ajb #8\n[   20.830545] Hardware name: linux,dummy-virt (DT)\n[   20.830829] pstate: 60000085 (nZCv daIf -PAN -UAO)\n[   20.831174] pc :           (null)\n[   20.831457] lr : serial8250_do_set_termios+0x358/0x6f4\n[   20.831727] sp : ffffffc06acff9b0\n[   20.831936] x29: ffffffc06acff9b0 x28: ffffff9008d7c000\n[   20.832267] x27: ffffff900969e16f x26: 0000000000000000\n[   20.832589] x25: ffffff900969dfb0 x24: 0000000000000000\n[   20.832906] x23: ffffffc06acffad0 x22: ffffff900969e160\n[   20.833232] x21: 0000000000000000 x20: ffffffc06acffac8\n[   20.833559] x19: ffffff900969df90 x18: 0000000000000000\n[   20.833878] x17: 0000000000000000 x16: 0000000000000000\n[   20.834491] x15: ffffffffffffffff x14: ffffffff00000000\n[   20.834821] x13: ffffffffffffffff x12: 0000000000000001\n[   20.835143] x11: 0101010101010101 x10: ffffff880d59ff5f\n[   20.835467] x9 : ffffff880d59ff5e x8 : ffffffc06acffaf3\n[   20.835790] x7 : 0000000000000000 x6 : ffffff880d59ff5f\n[   20.836111] x5 : c06419717c314100 x4 : 0000000000000007\n[   20.836419] x3 : 0000000000000000 x2 : 0000000000000000\n[   20.836732] x1 : 0000000000000001 x0 : ffffff900969df90\n[   20.837100] Process sh (pid: 104, stack limit = 0x(____ptrval____))\n[   20.837396] Call trace:\n[   20.837566]            (null)\n[   20.837816]  serial8250_set_termios+0x48/0x54\n[   20.838089]  uart_set_options+0x138/0x1bc\n[   20.838570]  uart_poll_init+0x114/0x16c\n[   20.838834]  tty_find_polling_driver+0x158/0x200\n[   20.839119]  configure_kgdboc+0xbc/0x1bc\n[   20.839380]  param_set_kgdboc_var+0xb8/0x150\n[   20.839658]  param_attr_store+0xbc/0x150\n[   20.839920]  module_attr_store+0x40/0x58\n[   20.840183]  sysfs_kf_write+0x8c/0xa8\n[   20.840183]  sysfs_kf_write+0x8c/0xa8\n[   20.840440]  kernfs_fop_write+0x154/0x290\n[   20.840702]  vfs_write+0xf0/0x278\n[   20.840942]  __arm64_sys_write+0x84/0xf4\n[   20.841209]  el0_svc_common+0xf4/0x1dc\n[   20.841471]  el0_svc_handler+0x98/0xbc\n[   20.841713]  el0_svc+0x8/0xc\n[   20.842057] Code: bad PC value\n[   20.842764] ---[ end trace a8835d7de79aaadf ]---\n[   20.843134] Kernel panic - not syncing: Fatal exception\n[   20.843515] SMP: stopping secondary CPUs\n[   20.844289] Kernel Offset: disabled\n[   20.844634] CPU features: 0x0,21806002\n[   20.844857] Memory Limit: none\n[   20.845172] ---[ end Kernel panic - not syncing: Fatal exception ]---\n\nSigned-off-by: Miles Chen <miles.chen@mediatek.com>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/8c5800cdb75c354ec0224f0fbab9e4c604b065c0"},{"sha":"6c2449a04c43faf8b6ca52cb11617c77fd3ee4dc","author":{"name":"Fabio Estevam","email":"679188261afeb60eb822cd934fd7b46a48ddd743@nxp.com"},"message":"ARM: imx_v6_v7_defconfig: Select CONFIG_TMPFS_POSIX_ACL\n\n[ Upstream commit 35d3cbe84544da74e39e1cec01374092467e3119 ]\n\nAndreas Müller reports:\n\n\"Fixes:\n\n| Sep 04 09:05:10 imx6qdl-variscite-som systemd-udevd[220]: Failed to apply ACL on /dev/v4l-subdev0: Operation not supported\n| Sep 04 09:05:10 imx6qdl-variscite-som systemd-udevd[224]: Failed to apply ACL on /dev/v4l-subdev1: Operation not supported\n| Sep 04 09:05:10 imx6qdl-variscite-som systemd-udevd[215]: Failed to apply ACL on /dev/v4l-subdev10: Operation not supported\n| Sep 04 09:05:10 imx6qdl-variscite-som systemd-udevd[228]: Failed to apply ACL on /dev/v4l-subdev2: Operation not supported\n| Sep 04 09:05:10 imx6qdl-variscite-som systemd-udevd[232]: Failed to apply ACL on /dev/v4l-subdev5: Operation not supported\n| Sep 04 09:05:10 imx6qdl-variscite-som systemd-udevd[217]: Failed to apply ACL on /dev/v4l-subdev11: Operation not supported\n| Sep 04 09:05:10 imx6qdl-variscite-som systemd-udevd[214]: Failed to apply ACL on /dev/dri/card1: Operation not supported\n| Sep 04 09:05:10 imx6qdl-variscite-som systemd-udevd[216]: Failed to apply ACL on /dev/v4l-subdev8: Operation not supported\n| Sep 04 09:05:10 imx6qdl-variscite-som systemd-udevd[226]: Failed to apply ACL on /dev/v4l-subdev9: Operation not supported\n\nand nasty follow-ups: Starting weston from sddm as unpriviledged user fails\nwith some hints on missing access rights.\"\n\nSelect the CONFIG_TMPFS_POSIX_ACL option to fix these issues.\n\nReported-by: Andreas Müller <schnitzeltony@gmail.com>\nSigned-off-by: Fabio Estevam <fabio.estevam@nxp.com>\nAcked-by: Otavio Salvador <otavio@ossystems.com.br>\nSigned-off-by: Shawn Guo <shawnguo@kernel.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/6c2449a04c43faf8b6ca52cb11617c77fd3ee4dc"},{"sha":"3374b0b15ec7c25aa98274aa95dbdea6d6d2af88","author":{"name":"Daniel Axtens","email":"cf1af486034ab0119a20f38a060e40da25f4cea3@axtens.net"},"message":"powerpc/nohash: fix undefined behaviour when testing page size support\n\n[ Upstream commit f5e284803a7206d43e26f9ffcae5de9626d95e37 ]\n\nWhen enumerating page size definitions to check hardware support,\nwe construct a constant which is (1U << (def->shift - 10)).\n\nHowever, the array of page size definitions is only initalised for\nvarious MMU_PAGE_* constants, so it contains a number of 0-initialised\nelements with def->shift == 0. This means we end up shifting by a\nvery large number, which gives the following UBSan splat:\n\n================================================================================\nUBSAN: Undefined behaviour in /home/dja/dev/linux/linux/arch/powerpc/mm/tlb_nohash.c:506:21\nshift exponent 4294967286 is too large for 32-bit type 'unsigned int'\nCPU: 0 PID: 0 Comm: swapper Not tainted 4.19.0-rc3-00045-ga604f927b012-dirty #6\nCall Trace:\n[c00000000101bc20] [c000000000a13d54] .dump_stack+0xa8/0xec (unreliable)\n[c00000000101bcb0] [c0000000004f20a8] .ubsan_epilogue+0x18/0x64\n[c00000000101bd30] [c0000000004f2b10] .__ubsan_handle_shift_out_of_bounds+0x110/0x1a4\n[c00000000101be20] [c000000000d21760] .early_init_mmu+0x1b4/0x5a0\n[c00000000101bf10] [c000000000d1ba28] .early_setup+0x100/0x130\n[c00000000101bf90] [c000000000000528] start_here_multiplatform+0x68/0x80\n================================================================================\n\nFix this by first checking if the element exists (shift != 0) before\nconstructing the constant.\n\nSigned-off-by: Daniel Axtens <dja@axtens.net>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/3374b0b15ec7c25aa98274aa95dbdea6d6d2af88"},{"sha":"4cb592436db9ff3ff394e6d8d951545a15fc66e8","author":{"name":"Christophe Leroy","email":"4e2d3d12816ace76f1cfa36c1816509bd24cf089@c-s.fr"},"message":"powerpc/mm: Don't report hugepage tables as memory leaks when using kmemleak\n\n[ Upstream commit 803d690e68f0c5230183f1a42c7d50a41d16e380 ]\n\nWhen a process allocates a hugepage, the following leak is\nreported by kmemleak. This is a false positive which is\ndue to the pointer to the table being stored in the PGD\nas physical memory address and not virtual memory pointer.\n\nunreferenced object 0xc30f8200 (size 512):\n  comm \"mmap\", pid 374, jiffies 4872494 (age 627.630s)\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n    00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................\n  backtrace:\n    [<e32b68da>] huge_pte_alloc+0xdc/0x1f8\n    [<9e0df1e1>] hugetlb_fault+0x560/0x8f8\n    [<7938ec6c>] follow_hugetlb_page+0x14c/0x44c\n    [<afbdb405>] __get_user_pages+0x1c4/0x3dc\n    [<b8fd7cd9>] __mm_populate+0xac/0x140\n    [<3215421e>] vm_mmap_pgoff+0xb4/0xb8\n    [<c148db69>] ksys_mmap_pgoff+0xcc/0x1fc\n    [<4fcd760f>] ret_from_syscall+0x0/0x38\n\nSee commit a984506c542e2 (\"powerpc/mm: Don't report PUDs as\nmemory leaks when using kmemleak\") for detailed explanation.\n\nTo fix that, this patch tells kmemleak to ignore the allocated\nhugepage table.\n\nSigned-off-by: Christophe Leroy <christophe.leroy@c-s.fr>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/4cb592436db9ff3ff394e6d8d951545a15fc66e8"},{"sha":"547d528ea395d104dcb31a18b2d51a285e0973aa","author":{"name":"Tomi Valkeinen","email":"e1ca4dbb8be1acaf20734fecd2da10ed1d46a9bb@ti.com"},"message":"drm/omap: fix memory barrier bug in DMM driver\n\n[ Upstream commit 538f66ba204944470a653a4cccc5f8befdf97c22 ]\n\nA DMM timeout \"timed out waiting for done\" has been observed on DRA7\ndevices. The timeout happens rarely, and only when the system is under\nheavy load.\n\nDebugging showed that the timeout can be made to happen much more\nfrequently by optimizing the DMM driver, so that there's almost no code\nbetween writing the last DMM descriptors to RAM, and writing to DMM\nregister which starts the DMM transaction.\n\nThe current theory is that a wmb() does not properly ensure that the\ndata written to RAM is observable by all the components in the system.\n\nThis DMM timeout has caused interesting (and rare) bugs as the error\nhandling was not functioning properly (the error handling has been fixed\nin previous commits):\n\n * If a DMM timeout happened when a GEM buffer was being pinned for\n   display on the screen, a timeout error would be shown, but the driver\n   would continue programming DSS HW with broken buffer, leading to\n   SYNCLOST floods and possible crashes.\n\n * If a DMM timeout happened when other user (say, video decoder) was\n   pinning a GEM buffer, a timeout would be shown but if the user\n   handled the error properly, no other issues followed.\n\n * If a DMM timeout happened when a GEM buffer was being released, the\n   driver does not even notice the error, leading to crashes or hang\n   later.\n\nThis patch adds wmb() and readl() calls after the last bit is written to\nRAM, which should ensure that the execution proceeds only after the data\nis actually in RAM, and thus observable by DMM.\n\nThe read-back should not be needed. Further study is required to understand\nif DMM is somehow special case and read-back is ok, or if DRA7's memory\nbarriers do not work correctly.\n\nSigned-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>\nSigned-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/547d528ea395d104dcb31a18b2d51a285e0973aa"},{"sha":"18490ea7607c1c136b385075219e65760a656f05","author":{"name":"John Garry","email":"8160036f9c092dfaa3b5fdb2cee4498fd919cf3a@huawei.com"},"message":"drm/hisilicon: hibmc: Do not carry error code in HiBMC framebuffer pointer\n\n[ Upstream commit 331d880b35a76b5de0eec8cbcecbf615d758a5f9 ]\n\nIn hibmc_drm_fb_create(), when the call to hibmc_framebuffer_init() fails\nwith error, do not store the error code in the HiBMC device frame-buffer\npointer, as this will be later checked for non-zero value in\nhibmc_fbdev_destroy() when our intention is to check for a valid function\npointer.\n\nThis fixes the following crash:\n[    9.699791] Unable to handle kernel NULL pointer dereference at virtual address 000000000000001a\n[    9.708672] Mem abort info:\n[    9.711489]   ESR = 0x96000004\n[    9.714570]   Exception class = DABT (current EL), IL = 32 bits\n[    9.720551]   SET = 0, FnV = 0\n[    9.723631]   EA = 0, S1PTW = 0\n[    9.726799] Data abort info:\n[    9.729702]   ISV = 0, ISS = 0x00000004\n[    9.733573]   CM = 0, WnR = 0\n[    9.736566] [000000000000001a] user address but active_mm is swapper\n[    9.742987] Internal error: Oops: 96000004 [#1] PREEMPT SMP\n[    9.748614] Modules linked in:\n[    9.751694] CPU: 16 PID: 293 Comm: kworker/16:1 Tainted: G        W         4.19.0-rc4-next-20180920-00001-g9b0012c #322\n[    9.762681] Hardware name: Huawei Taishan 2280 /D05, BIOS Hisilicon D05 IT21 Nemo 2.0 RC0 04/18/2018\n[    9.771915] Workqueue: events work_for_cpu_fn\n[    9.776312] pstate: 60000005 (nZCv daif -PAN -UAO)\n[    9.781150] pc : drm_mode_object_put+0x0/0x20\n[    9.785547] lr : hibmc_fbdev_fini+0x40/0x58\n[    9.789767] sp : ffff00000af1bcf0\n[    9.793108] x29: ffff00000af1bcf0 x28: 0000000000000000\n[    9.798473] x27: 0000000000000000 x26: ffff000008f66630\n[    9.803838] x25: 0000000000000000 x24: ffff0000095abb98\n[    9.809203] x23: ffff8017db92fe00 x22: ffff8017d2b13000\n[    9.814568] x21: ffffffffffffffea x20: ffff8017d2f80018\n[    9.819933] x19: ffff8017d28a0018 x18: ffffffffffffffff\n[    9.825297] x17: 0000000000000000 x16: 0000000000000000\n[    9.830662] x15: ffff0000092296c8 x14: ffff00008939970f\n[    9.836026] x13: ffff00000939971d x12: ffff000009229940\n[    9.841391] x11: ffff0000085f8fc0 x10: ffff00000af1b9a0\n[    9.846756] x9 : 000000000000000d x8 : 6620657a696c6169\n[    9.852121] x7 : ffff8017d3340580 x6 : ffff8017d4168000\n[    9.857486] x5 : 0000000000000000 x4 : ffff8017db92fb20\n[    9.862850] x3 : 0000000000002690 x2 : ffff8017d3340480\n[    9.868214] x1 : 0000000000000028 x0 : 0000000000000002\n[    9.873580] Process kworker/16:1 (pid: 293, stack limit = 0x(____ptrval____))\n[    9.880788] Call trace:\n[    9.883252]  drm_mode_object_put+0x0/0x20\n[    9.887297]  hibmc_unload+0x1c/0x80\n[    9.890815]  hibmc_pci_probe+0x170/0x3c8\n[    9.894773]  local_pci_probe+0x3c/0xb0\n[    9.898555]  work_for_cpu_fn+0x18/0x28\n[    9.902337]  process_one_work+0x1e0/0x318\n[    9.906382]  worker_thread+0x228/0x450\n[    9.910164]  kthread+0x128/0x130\n[    9.913418]  ret_from_fork+0x10/0x18\n[    9.917024] Code: a94153f3 a8c27bfd d65f03c0 d503201f (f9400c01)\n[    9.923180] ---[ end trace 2695ffa0af5be375 ]---\n\nFixes: d1667b86795a (\"drm/hisilicon/hibmc: Add support for frame buffer\")\nSigned-off-by: John Garry <john.garry@huawei.com>\nReviewed-by: Xinliang Liu <z.liuxinliang@hisilicon.com>\nSigned-off-by: Xinliang Liu <z.liuxinliang@hisilicon.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/18490ea7607c1c136b385075219e65760a656f05"},{"sha":"27f612940d5cf7b5d4bae316c4dd6dfead6a6ec6","author":{"name":"Nicholas Mc Guire","email":"1f1947151fff46847c7ab253c8b8ee2fc7e63b14@osadl.org"},"message":"media: pci: cx23885: handle adding to list failure\n\n[ Upstream commit c5d59528e24ad22500347b199d52b9368e686a42 ]\n\naltera_hw_filt_init() which calls append_internal() assumes\nthat the node was successfully linked in while in fact it can\nsilently fail. So the call-site needs to set return to -ENOMEM\non append_internal() returning NULL and exit through the err path.\n\nFixes: 349bcf02e361 (\"[media] Altera FPGA based CI driver module\")\n\nSigned-off-by: Nicholas Mc Guire <hofrat@osadl.org>\nSigned-off-by: Hans Verkuil <hans.verkuil@cisco.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/27f612940d5cf7b5d4bae316c4dd6dfead6a6ec6"},{"sha":"e56c482e4e7f4d39a851ebceb7652be59d248208","author":{"name":"Lucas Stach","email":"48c9e973d8f86eb0cdae200124c5925db7587c4e@pengutronix.de"},"message":"media: coda: don't overwrite h.264 profile_idc on decoder instance\n\n[ Upstream commit 1f32061e843205f6fe8404d5100d5adcec334e75 ]\n\nOn a decoder instance, after the profile has been parsed from the stream\n__v4l2_ctrl_s_ctrl() is called to notify userspace about changes in the\nread-only profile control. This ends up calling back into the CODA driver\nwhere a missing check on the s_ctrl caused the profile information that has\njust been parsed from the stream to be overwritten with the default\nbaseline profile.\n\nLater on the driver fails to enable frame reordering, based on the wrong\nprofile information.\n\nFixes: 347de126d1da (media: coda: add read-only h.264 decoder\n                     profile/level controls)\n\nSigned-off-by: Lucas Stach <l.stach@pengutronix.de>\nReviewed-by: Philipp Zabel <p.zabel@pengutronix.de>\nSigned-off-by: Hans Verkuil <hans.verkuil@cisco.com>\nSigned-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/e56c482e4e7f4d39a851ebceb7652be59d248208"},{"sha":"806be82cd255646c8fa872529447be1289c12c6c","author":{"name":"Dengcheng Zhu","email":"f1dc036443bd76c254ad3c59d629999f4170bb66@wavecomp.com"},"message":"MIPS: kexec: Mark CPU offline before disabling local IRQ\n\n[ Upstream commit dc57aaf95a516f70e2d527d8287a0332c481a226 ]\n\nAfter changing CPU online status, it will not be sent any IPIs such as in\n__flush_cache_all() on software coherency systems. Do this before disabling\nlocal IRQ.\n\nSigned-off-by: Dengcheng Zhu <dzhu@wavecomp.com>\nSigned-off-by: Paul Burton <paul.burton@mips.com>\nPatchwork: https://patchwork.linux-mips.org/patch/20571/\nCc: pburton@wavecomp.com\nCc: ralf@linux-mips.org\nCc: linux-mips@linux-mips.org\nCc: rachel.mozes@intel.com\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/806be82cd255646c8fa872529447be1289c12c6c"},{"sha":"f386e1e50e35ea51c6bd977eb4808c2f429a54df","author":{"name":"Joel Stanley","email":"4816dabf8db1bc6cac35b3a24cab2ff844b5b0c7@jms.id.au"},"message":"powerpc/boot: Ensure _zimage_start is a weak symbol\n\n[ Upstream commit ee9d21b3b3583712029a0db65a4b7c081d08d3b3 ]\n\nWhen building with clang crt0's _zimage_start is not marked weak, which\nbreaks the build when linking the kernel image:\n\n $ objdump -t arch/powerpc/boot/crt0.o |grep _zimage_start$\n 0000000000000058 g       .text  0000000000000000 _zimage_start\n\n ld: arch/powerpc/boot/wrapper.a(crt0.o): in function '_zimage_start':\n (.text+0x58): multiple definition of '_zimage_start';\n arch/powerpc/boot/pseries-head.o:(.text+0x0): first defined here\n\nClang requires the .weak directive to appear after the symbol is\ndeclared. The binutils manual says:\n\n This directive sets the weak attribute on the comma separated list of\n symbol names. If the symbols do not already exist, they will be\n created.\n\nSo it appears this is different with clang. The only reference I could\nsee for this was an OpenBSD mailing list post[1].\n\nChanging it to be after the declaration fixes building with Clang, and\nstill works with GCC.\n\n $ objdump -t arch/powerpc/boot/crt0.o |grep _zimage_start$\n 0000000000000058  w      .text\t0000000000000000 _zimage_start\n\nReported to clang as https://bugs.llvm.org/show_bug.cgi?id=38921\n\n[1] https://groups.google.com/forum/#!topic/fa.openbsd.tech/PAgKKen2YCY\n\nSigned-off-by: Joel Stanley <joel@jms.id.au>\nReviewed-by: Nick Desaulniers <ndesaulniers@google.com>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/f386e1e50e35ea51c6bd977eb4808c2f429a54df"},{"sha":"983721397fe0a6b2a5937da74b43d4bc0bbb13fe","author":{"name":"Rashmica Gupta","email":"7c7908f246e3c843a2f4c2e4e52ed15aa16cad0a@gmail.com"},"message":"powerpc/memtrace: Remove memory in chunks\n\n[ Upstream commit 3f7daf3d7582dc6628ac40a9045dd1bbd80c5f35 ]\n\nWhen hot-removing memory release_mem_region_adjustable() splits iomem\nresources if they are not the exact size of the memory being\nhot-deleted. Adding this memory back to the kernel adds a new resource.\n\nEg a node has memory 0x0 - 0xfffffffff. Hot-removing 1GB from\n0xf40000000 results in the single resource 0x0-0xfffffffff being split\ninto two resources: 0x0-0xf3fffffff and 0xf80000000-0xfffffffff.\n\nWhen we hot-add the memory back we now have three resources:\n0x0-0xf3fffffff, 0xf40000000-0xf7fffffff, and 0xf80000000-0xfffffffff.\n\nThis is an issue if we try to remove some memory that overlaps\nresources. Eg when trying to remove 2GB at address 0xf40000000,\nrelease_mem_region_adjustable() fails as it expects the chunk of memory\nto be within the boundaries of a single resource. We then get the\nwarning: \"Unable to release resource\" and attempting to use memtrace\nagain gives us this error: \"bash: echo: write error: Resource\ntemporarily unavailable\"\n\nThis patch makes memtrace remove memory in chunks that are always the\nsame size from an address that is always equal to end_of_memory -\nn*size, for some n. So hotremoving and hotadding memory of different\nsizes will now not attempt to remove memory that spans multiple\nresources.\n\nSigned-off-by: Rashmica Gupta <rashmica.g@gmail.com>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/983721397fe0a6b2a5937da74b43d4bc0bbb13fe"},{"sha":"f9cb913a7959321bf491b824e5f207a2520cd412","author":{"name":"Huacai Chen","email":"bddc6ef64099649954804bf58f2e4dee9b3b798f@lemote.com"},"message":"MIPS/PCI: Call pcie_bus_configure_settings() to set MPS/MRRS\n\n[ Upstream commit 2794f688b2c336e0da85e9f91fed33febbd9f54a ]\n\nCall pcie_bus_configure_settings() on MIPS, like for other platforms.\nThe function pcie_bus_configure_settings() makes sure the MPS (Max\nPayload Size) across the bus is uniform and provides the ability to\ntune the MRSS (Max Read Request Size) and MPS (Max Payload Size) to\nhigher performance values. Some devices will not operate properly if\nthese aren't set correctly because the firmware doesn't always do it.\n\nSigned-off-by: Huacai Chen <chenhc@lemote.com>\nSigned-off-by: Paul Burton <paul.burton@mips.com>\nPatchwork: https://patchwork.linux-mips.org/patch/20649/\nCc: Ralf Baechle <ralf@linux-mips.org>\nCc: James Hogan <jhogan@kernel.org>\nCc: linux-mips@linux-mips.org\nCc: Fuxin Zhang <zhangfx@lemote.com>\nCc: Zhangjin Wu <wuzhangjin@gmail.com>\nCc: Huacai Chen <chenhuacai@gmail.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/f9cb913a7959321bf491b824e5f207a2520cd412"},{"sha":"4d0df50d740ecfd8ca7831c739e5c98c7466a94a","author":{"name":"Phil Elwell","email":"e888d2bd6f13f82caa51a37c03d034c76f661ba3@raspberrypi.org"},"message":"sc16is7xx: Fix for multi-channel stall\n\n[ Upstream commit 8344498721059754e09d30fe255a12dab8fb03ef ]\n\nThe SC16IS752 is a dual-channel device. The two channels are largely\nindependent, but the IRQ signals are wired together as an open-drain,\nactive low signal which will be driven low while either of the\nchannels requires attention, which can be for significant periods of\ntime until operations complete and the interrupt can be acknowledged.\nIn that respect it is should be treated as a true level-sensitive IRQ.\n\nThe kernel, however, needs to be able to exit interrupt context in\norder to use I2C or SPI to access the device registers (which may\ninvolve sleeping).  Therefore the interrupt needs to be masked out or\npaused in some way.\n\nThe usual way to manage sleeping from within an interrupt handler\nis to use a threaded interrupt handler - a regular interrupt routine\ndoes the minimum amount of work needed to triage the interrupt before\nwaking the interrupt service thread. If the threaded IRQ is marked as\nIRQF_ONESHOT the kernel will automatically mask out the interrupt\nuntil the thread runs to completion. The sc16is7xx driver used to\nuse a threaded IRQ, but a patch switched to using a kthread_worker\nin order to set realtime priorities on the handler thread and for\nother optimisations. The end result is non-threaded IRQ that\nschedules some work then returns IRQ_HANDLED, making the kernel\nthink that all IRQ processing has completed.\n\nThe work-around to prevent a constant stream of interrupts is to\nmark the interrupt as edge-sensitive rather than level-sensitive,\nbut interpreting an active-low source as a falling-edge source\nrequires care to prevent a total cessation of interrupts. Whereas\nan edge-triggering source will generate a new edge for every interrupt\ncondition a level-triggering source will keep the signal at the\ninterrupting level until it no longer requires attention; in other\nwords, the host won't see another edge until all interrupt conditions\nare cleared. It is therefore vital that the interrupt handler does not\nexit with an outstanding interrupt condition, otherwise the kernel\nwill not receive another interrupt unless some other operation causes\nthe interrupt state on the device to be cleared.\n\nThe existing sc16is7xx driver has a very simple interrupt \"thread\"\n(kthread_work job) that processes interrupts on each channel in turn\nuntil there are no more. If both channels are active and the first\nchannel starts interrupting while the handler for the second channel\nis running then it will not be detected and an IRQ stall ensues. This\ncould be handled easily if there was a shared IRQ status register, or\na convenient way to determine if the IRQ had been deasserted for any\nlength of time, but both appear to be lacking.\n\nAvoid this problem (or at least make it much less likely to happen)\nby reducing the granularity of per-channel interrupt processing\nto one condition per iteration, only exiting the overall loop when\nboth channels are no longer interrupting.\n\nSigned-off-by: Phil Elwell <phil@raspberrypi.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/4d0df50d740ecfd8ca7831c739e5c98c7466a94a"},{"sha":"3e59ed2e314373c6c91599b027e95b607f5cb584","author":{"name":"Marco Felsch","email":"43df7b5eee4ab13b86a82edbc58b423fb2a490b3@pengutronix.de"},"message":"media: tvp5150: fix width alignment during set_selection()\n\n[ Upstream commit bd24db04101f45a9c1d874fe21b0c7eab7bcadec ]\n\nThe driver ignored the width alignment which exists due to the UYVY\ncolorspace format. Fix the width alignment and make use of the the\nprovided v4l2 helper function to set the width, height and all\nalignments in one.\n\nFixes: 963ddc63e20d (\"[media] media: tvp5150: Add cropping support\")\n\nSigned-off-by: Marco Felsch <m.felsch@pengutronix.de>\nSigned-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/3e59ed2e314373c6c91599b027e95b607f5cb584"},{"sha":"d3835bb8fa6758b4f38da3741e206192a6340f90","author":{"name":"Breno Leitao","email":"a10246ea2c3600c1725f8dc718f81b30cd4d07c5@debian.org"},"message":"powerpc/selftests: Wait all threads to join\n\n[ Upstream commit 693b31b2fc1636f0aa7af53136d3b49f6ad9ff39 ]\n\nTest tm-tmspr might exit before all threads stop executing, because it just\nwaits for the very last thread to join before proceeding/exiting.\n\nThis patch makes sure that all threads that were created will join before\nproceeding/exiting.\n\nThis patch also guarantees that the amount of threads being created is equal\nto thread_num.\n\nSigned-off-by: Breno Leitao <leitao@debian.org>\nSigned-off-by: Michael Ellerman <mpe@ellerman.id.au>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/d3835bb8fa6758b4f38da3741e206192a6340f90"},{"sha":"442b54290c782f22a848941064625cad3e263f39","author":{"name":"Alexandru Ardelean","email":"685557f6b7c225d86b536740313ed51b24843a58@analog.com"},"message":"staging:iio:ad7606: fix voltage scales\n\n[ Upstream commit 4ee033301c898dd0835d035d0e0eb768a3d35da1 ]\n\nFixes commit 17be2a2905a6ec9aa27cd59521495e2f490d2af0 (\"staging: iio:\nad7606: replace range/range_available with corresponding scale\").\n\nThe AD7606 devices don't have a 2.5V voltage range, they have 5V & 10V\nvoltage range, which is selectable via the `gpio_range` descriptor.\n\nThe scales also seem to have been miscomputed, because when they were\napplied to the raw values, the results differ from the expected values.\nAfter checking the ADC transfer function in the datasheet, these were\nre-computed.\n\nSigned-off-by: Alexandru Ardelean <alexandru.ardelean@analog.com>\nSigned-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>\nSigned-off-by: Sasha Levin <sashal@kernel.org>\nSigned-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>","distinct":false,"url":"https://api.github.com/repos/Jackeagle/kernel-msm-4.4/commits/442b54290c782f22a848941064625cad3e263f39"}]}
{"actor":{"display_login":"blissgerrit"}}