{"push_id":1413110103,"size":5,"distinct_size":5,"ref":"refs/heads/master","head":"697ed8d03909140d95484d46d277a4e46d89b0e5","before":"77079b133f242d3e3710c9b89ed54458307e54ff","commits":[{"sha":"24c66dfd569c4744fc43aea638155ad2dc1499d8","author":{"name":"Russell King","email":"8640768d851c67eb4c0e8bfcf2aabcc8010b9372@armlinux.org.uk"},"message":"ARM: fix backtrace\n\nRecent kernels have changed their behaviour to be more inconsistent\nwhen handling printk continuations.  With todays kernels, the output\nlooks sane on the console, but dmesg splits individual printk()s which\ndo not have the KERN_CONT prefix into separate lines.\n\nSince the assembly code is not trivial to add the KERN_CONT, and we\nideally want to avoid using KERN_CONT (as multiple printk()s can race\nbetween different threads), convert the assembly dumping the register\nvalues to C code, and have the C code build the output a line at a\ntime before dumping to the console.\n\nThis avoids the KERN_CONT issue, and also avoids situations where the\noutput is intermixed with other console activity.\n\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/24c66dfd569c4744fc43aea638155ad2dc1499d8"},{"sha":"544457fa278216c5fcea6a16e9b2ee8aadaca0ca","author":{"name":"Nicolas Pitre","email":"821418b0a29e813296bdaa58f6aecc4445fd1b69@linaro.org"},"message":"ARM: 8624/1: proc-v7m.S: fix init section name\n\nThere is no .text.init sections.\n\nSigned-off-by: Nicolas Pitre <nico@linaro.org>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/544457fa278216c5fcea6a16e9b2ee8aadaca0ca"},{"sha":"256ff1cf6b44cba9c9c2059f4516259e9319a808","author":{"name":"Marek Szyprowski","email":"4d0ab7dac85d754388f4be3549f400e336faa58a@samsung.com"},"message":"ARM: 8628/1: dma-mapping: preallocate DMA-debug hash tables in core_initcall\n\nfs_initcall is definitely too late to initialize DMA-debug hash tables,\nbecause some drivers might get probed and use DMA mapping framework\nalready in core_initcall. Late initialization of DMA-debug results in\nfalse warning about accessing memory, that was not allocated, like this\none:\n------------[ cut here ]------------\nWARNING: CPU: 5 PID: 1 at lib/dma-debug.c:1104 check_unmap+0xa1c/0xe50\nexynos-sysmmu 10a60000.sysmmu: DMA-API: device driver tries to free DMA memory it has not allocated [device\naddress=0x000000006ebd0000] [size=16384 bytes]\nModules linked in:\nCPU: 5 PID: 1 Comm: swapper/0 Not tainted 4.9.0-rc5-00028-g39dde3d-dirty #44\nHardware name: SAMSUNG EXYNOS (Flattened Device Tree)\n[<c0119dd4>] (unwind_backtrace) from [<c01122bc>] (show_stack+0x20/0x24)\n[<c01122bc>] (show_stack) from [<c062714c>] (dump_stack+0x84/0xa0)\n[<c062714c>] (dump_stack) from [<c0132560>] (__warn+0x14c/0x180)\n[<c0132560>] (__warn) from [<c01325dc>] (warn_slowpath_fmt+0x48/0x50)\n[<c01325dc>] (warn_slowpath_fmt) from [<c06814f8>] (check_unmap+0xa1c/0xe50)\n[<c06814f8>] (check_unmap) from [<c06819c4>] (debug_dma_unmap_page+0x98/0xc8)\n[<c06819c4>] (debug_dma_unmap_page) from [<c076c3e8>] (exynos_iommu_domain_free+0x158/0x380)\n[<c076c3e8>] (exynos_iommu_domain_free) from [<c0764a30>] (iommu_domain_free+0x34/0x60)\n[<c0764a30>] (iommu_domain_free) from [<c011f168>] (release_iommu_mapping+0x30/0xb8)\n[<c011f168>] (release_iommu_mapping) from [<c011f23c>] (arm_iommu_release_mapping+0x4c/0x50)\n[<c011f23c>] (arm_iommu_release_mapping) from [<c0b061ac>] (s5p_mfc_probe+0x640/0x80c)\n[<c0b061ac>] (s5p_mfc_probe) from [<c07e6750>] (platform_drv_probe+0x70/0x148)\n[<c07e6750>] (platform_drv_probe) from [<c07e25c0>] (driver_probe_device+0x12c/0x6b0)\n[<c07e25c0>] (driver_probe_device) from [<c07e2c6c>] (__driver_attach+0x128/0x17c)\n[<c07e2c6c>] (__driver_attach) from [<c07df74c>] (bus_for_each_dev+0x88/0xc8)\n[<c07df74c>] (bus_for_each_dev) from [<c07e1b6c>] (driver_attach+0x34/0x58)\n[<c07e1b6c>] (driver_attach) from [<c07e1350>] (bus_add_driver+0x18c/0x32c)\n[<c07e1350>] (bus_add_driver) from [<c07e4198>] (driver_register+0x98/0x148)\n[<c07e4198>] (driver_register) from [<c07e5cb0>] (__platform_driver_register+0x58/0x74)\n[<c07e5cb0>] (__platform_driver_register) from [<c174cb30>] (s5p_mfc_driver_init+0x1c/0x20)\n[<c174cb30>] (s5p_mfc_driver_init) from [<c0102690>] (do_one_initcall+0x64/0x258)\n[<c0102690>] (do_one_initcall) from [<c17014c0>] (kernel_init_freeable+0x3d0/0x4d0)\n[<c17014c0>] (kernel_init_freeable) from [<c116eeb4>] (kernel_init+0x18/0x134)\n[<c116eeb4>] (kernel_init) from [<c010bbd8>] (ret_from_fork+0x14/0x3c)\n---[ end trace dc54c54bd3581296 ]---\n\nThis patch moves initialization of DMA-debug to core_initcall. This is\nsafe from the initialization perspective. dma_debug_do_init() internally calls\ndebugfs functions and debugfs also gets initialised at core_initcall(), and\nthat is earlier than arch code in the link order, so it will get initialized\njust before the DMA-debug.\n\nReported-by: Seung-Woo Kim <sw0312.kim@samsung.com>\nSigned-off-by: Marek Szyprowski <m.szyprowski@samsung.com>\nSigned-off-by: Russell King <rmk+kernel@arm.linux.org.uk>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/256ff1cf6b44cba9c9c2059f4516259e9319a808"},{"sha":"2a3811068fbc6bf09bb09d166b65394b091c1085","author":{"name":"Russell King","email":"8640768d851c67eb4c0e8bfcf2aabcc8010b9372@armlinux.org.uk"},"message":"ARM: Fix XIP kernels\n\nCommit 7619751f8c90 (\"ARM: 8595/2: apply more __ro_after_init\") caused\na regression with XIP kernels by moving the __ro_after_init data into\nthe read-only section.  With XIP kernels, the read-only section is\nlocated in read-only memory from the very beginning.\n\nWork around this by moving the __ro_after_init data back into the .data\nsection, which will be in RAM, and hence will be writable.\n\nIt should be noted that in doing so, this remains writable after init.\n\nFixes: 7619751f8c90 (\"ARM: 8595/2: apply more __ro_after_init\")\nReported-by: Andrea Merello <andrea.merello@gmail.com>\nTested-by: Andrea Merello <andrea.merello@gmail.com> [ XIP stm32 ]\nTested-by: Alexandre Torgue <alexandre.torgue@st.com>\nSigned-off-by: Russell King <rmk+kernel@armlinux.org.uk>","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/2a3811068fbc6bf09bb09d166b65394b091c1085"},{"sha":"697ed8d03909140d95484d46d277a4e46d89b0e5","author":{"name":"Linus Torvalds","email":"ead7104581934751970e9decb2db5deb20a9e407@linux-foundation.org"},"message":"Merge branch 'fixes' of git://git.armlinux.org.uk/~rmk/linux-arm\n\nPull ARM fixes from Russell King:\n \"A few more ARM fixes:\n\n   - the assembly backtrace code suffers problems with the new printk()\n     implementation which assumes that kernel messages without KERN_CONT\n     should have newlines inserted between them. Fix this.\n   - fix a section naming error - \".init.text\" rather than \".text.init\"\n   - preallocate DMA debug memory at core_initcall() time rather than\n     fs_initcall(), as we have some core drivers that need to use DMA\n     mapping - and that triggers a kernel warning from the DMA debug\n     code.\n   - fix XIP kernels after the ro_after_init changes made this data\n     permanently read-only\"\n\n* 'fixes' of git://git.armlinux.org.uk/~rmk/linux-arm:\n  ARM: Fix XIP kernels\n  ARM: 8628/1: dma-mapping: preallocate DMA-debug hash tables in core_initcall\n  ARM: 8624/1: proc-v7m.S: fix init section name\n  ARM: fix backtrace","distinct":true,"url":"https://api.github.com/repos/PKRoma/linux/commits/697ed8d03909140d95484d46d277a4e46d89b0e5"}]}
{"actor":{"display_login":"PKRoma"}}