{"push_id":2807212584,"size":131,"distinct_size":131,"ref":"refs/heads/rebase-4.9","head":"0d186f438ffd7f0bf3d9bfff9c1eb5c008c706a2","before":"ab4abb7feb06ad1ba2c0e0da8121a643230b6301","commits":[{"sha":"b13fcf8f929bdfef1dfadc6d97201a5e1d60e5b3","author":{"name":"Huacai Chen","email":"bddc6ef64099649954804bf58f2e4dee9b3b798f@lemote.com"},"message":"Sync code to Linux-4.9.120 from upstream\n\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/b13fcf8f929bdfef1dfadc6d97201a5e1d60e5b3"},{"sha":"f343184b1db1283c1b3290936a213152d4c5265f","author":{"name":"Sinan Kaya","email":"cf5979e03805ba1df04461f92c60e94cd80f875f@codeaurora.org"},"message":"MIPS: io: Prevent compiler reordering writeX()\n\nwriteX() has strong ordering semantics with respect to memory updates.\nIn the absence of a write barrier or a compiler barrier, the compiler\ncan reorder register and memory update instructions. This breaks the\nwriteX() API.\n\nSigned-off-by: Sinan Kaya <okaya@codeaurora.org>\nCc: Arnd Bergmann <arnd@arndb.de>\nCc: Ralf Baechle <ralf@linux-mips.org>\nCc: Paul Burton <paul.burton@mips.com>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/18997/\n[jhogan@kernel.org: Tidy commit message]\nSigned-off-by: James Hogan <jhogan@kernel.org>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/f343184b1db1283c1b3290936a213152d4c5265f"},{"sha":"d11eff6774671739e3895f425f545d378bb50bbf","author":{"name":"Sinan Kaya","email":"cf5979e03805ba1df04461f92c60e94cd80f875f@codeaurora.org"},"message":"MIPS: io: Add barrier after register read in readX()\n\nWhile a barrier is present in the writeX() functions before the register\nwrite, a similar barrier is missing in the readX() functions after the\nregister read. This could allow memory accesses following readX() to\nobserve stale data.\n\nSigned-off-by: Sinan Kaya <okaya@codeaurora.org>\nReported-by: Arnd Bergmann <arnd@arndb.de>\nCc: Ralf Baechle <ralf@linux-mips.org>\nCc: Paul Burton <paul.burton@mips.com>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/19069/\n[jhogan@kernel.org: Tidy commit message]\nSigned-off-by: James Hogan <jhogan@kernel.org>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/d11eff6774671739e3895f425f545d378bb50bbf"},{"sha":"0e522d202c19ca80f2dd235bc58fe77dbce704cc","author":{"name":"Petr Mladek","email":"9cbcfb1260d253e26a699647bd9cbee55818ea4a@suse.com"},"message":"printk: Use the main logbuf in NMI when logbuf_lock is available\n\nThe commit 42a0bb3f71383b457a7d (\"printk/nmi: generic solution for safe\nprintk in NMI\") caused that printk stores messages into a temporary\nbuffer in NMI context.\n\nThe buffer is per-CPU and therefore the size is rather limited.\nIt works quite well for NMI backtraces. But there are longer logs\nthat might get printed in NMI context, for example, lockdep\nwarnings, ftrace_dump_on_oops.\n\nThe temporary buffer is used to avoid deadlocks caused by\nlogbuf_lock. Also it is needed to avoid races with the other\ntemporary buffer that is used when PRINTK_SAFE_CONTEXT is entered.\nBut the main buffer can be used in NMI if the lock is available\nand we did not interrupt PRINTK_SAFE_CONTEXT.\n\nThe lock is checked using raw_spin_is_locked(). It might cause\nfalse negatives when the lock is taken on another CPU and\nthis CPU is in the safe context from other reasons. Note that\nthe safe context is used also to get console semaphore or when\ncalling console drivers. For this reason, we do the check in\nprintk_nmi_enter(). It makes the handling consistent for\nthe entire NMI handler and avoids reshuffling of the messages.\n\nThe patch also defines special printk context that allows\nto use printk_deferred() in NMI. Note that we could not flush\nthe messages to the consoles because console drivers might use\nmany other internal locks.\n\nThe newly created vprintk_deferred() disables the preemption\nonly around the irq work handling. It is needed there to keep\nthe consistency between the two per-CPU variables. But there\nis no reason to disable preemption around vprintk_emit().\n\nFinally, the patch puts back explicit serialization of the NMI\nbacktraces from different CPUs. It was removed by the\ncommit a9edc88093287183ac934b (\"x86/nmi: Perform a safe\nNMI stack trace on all CPUs\"). It was not needed because\nthe flushing of the temporary per-CPU buffers was serialized.\n\nLink: http://lkml.kernel.org/r/1493912763-24873-1-git-send-email-pmladek@suse.com\nCc: Steven Rostedt <rostedt@goodmis.org>\nCc: Andrew Morton <akpm@linux-foundation.org>\nCc: Peter Zijlstra <peterz@infradead.org>\nCc: Russell King <rack+kernel@arm.linux.org.uk>\nCc: Daniel Thompson <daniel.thompson@linaro.org>\nCc: Ingo Molnar <mingo@redhat.com>\nCc: Thomas Gleixner <tglx@linutronix.de>\nCc: Chris Metcalf <cmetcalf@ezchip.com>\nCc: x86@kernel.org\nCc: linux-arm-kernel@lists.infradead.org\nCc: linux-kernel@vger.kernel.org\nSuggested-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nAcked-by: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>\nSigned-off-by: Petr Mladek <pmladek@suse.com>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/0e522d202c19ca80f2dd235bc58fe77dbce704cc"},{"sha":"266f3dce29e32fa2f4647e08f9166098005e5735","author":{"name":"Huacai Chen","email":"bddc6ef64099649954804bf58f2e4dee9b3b798f@lemote.com"},"message":"MIPS: Change definition of cpu_relax() for Loongson-3\n\nLinux expects that if a CPU modifies a memory location, then that\nmodification will eventually become visible to other CPUs in the system.\n\nOn Loongson-3 processor with SFB (Store Fill Buffer), loads may be\nprioritised over stores so it is possible for a store operation to be\npostponed if a polling loop immediately follows it. If the variable\nbeing polled indirectly depends on the outstanding store [for example,\nanother CPU may be polling the variable that is pending modification]\nthen there is the potential for deadlock if interrupts are disabled.\nThis deadlock occurs in qspinlock code.\n\nThis patch changes the definition of cpu_relax() to smp_mb() for\nLoongson-3, forcing a flushing of the SFB on SMP systems before the\nnext load takes place. If the Kernel is not compiled for SMP support,\nthis will expand to a barrier() as before.\n\nReferences: 534be1d5a2da940 (ARM: 6194/1: change definition of cpu_relax() for ARM11MPCore)\nCc: stable@vger.kernel.org\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/266f3dce29e32fa2f4647e08f9166098005e5735"},{"sha":"fa174569d5830b7f431f263e651bcd5d41dc4c54","author":{"name":"Huacai Chen","email":"bddc6ef64099649954804bf58f2e4dee9b3b798f@lemote.com"},"message":"scsi: lpfc: Switch memcpy_fromio() to __read32_copy()\n\nIn commit bc73905abf770192 (\"[SCSI] lpfc 8.3.16: SLI Additions, updates,\nand code cleanup\"), lpfc_memcpy_to_slim() have switched memcpy_toio() to\n__write32_copy() in order to prevent unaligned 64 bit copy. Recently, we\nfound that lpfc_memcpy_from_slim() have similar issues, so let it switch\nmemcpy_fromio() to __read32_copy().\n\nCc: stable@vger.kernel.org\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/fa174569d5830b7f431f263e651bcd5d41dc4c54"},{"sha":"50709e54ac0500d04b92b5b2e4f02bffc8c2a9b1","author":{"name":"Huacai Chen","email":"bddc6ef64099649954804bf58f2e4dee9b3b798f@lemote.com"},"message":"hwmon: (w83795) temp4_type has writable permission\n\nSigned-off-by: Yao Wang <wangyao@lemote.com>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/50709e54ac0500d04b92b5b2e4f02bffc8c2a9b1"},{"sha":"3c67b88d33d5a6e175be5a6bdbe2742cd9026097","author":{"name":"Joshua Kinard","email":"a4a2167d2a45f355de156547e4a714ce8b4b7b2e@gentoo.org"},"message":"MIPS: Disable stack checks on MIPS kernels\n\nDisable stack checking on MIPS kernels.  Some distribution toolchains\nmight pass the -fstack-check option to gcc.  This results in a\nstore-doubleword instruction being emitted at the top of all\nfunctions that checks the available stack space.  E.g.,\n\n  a80000000001d740 <per_cpu_init>:\n  a80000000001d740:       ffa0bfc0        sd      zero,-16448(sp)\n  a80000000001d744:       2405ffc9        li      a1,-55\n  a80000000001d748:       67bdffc0        daddiu  sp,sp,-64\n\nGenerally, this is undesirable, and especially on the SGI IP27\nplatform, it will trigger a NULL pointer dereference in\n'_raw_spin_lock_irq' during early init.\n\nSigned-off-by: Joshua Kinard <kumba@gentoo.org>\nSuggested-by: James Hogan <james.hogan@imgtec.com>\nCc: Ralf Baechle <ralf@linux-mips.org>\nCc: \"Maciej W. Rozycki\" <macro@linux-mips.org>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/15132/\nSigned-off-by: James Hogan <james.hogan@imgtec.com>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/3c67b88d33d5a6e175be5a6bdbe2742cd9026097"},{"sha":"7b26b5204bbe9182fd70801b866168a07837acdd","author":{"name":"Robert Schiele","email":"9c17b044b1f25675bf65ff0e0a9ebb6d22eb8344@gmail.com"},"message":"MIPS: VDSO: Explicitly use -fno-asynchronous-unwind-tables\n\nNot every toolchain has -fno-asynchronous-unwind-tables per default on\nMIPS. This patch specifies the necessary option explicitly for VDSO\nlibrary build.\n\nThis prevents the following build failure:\nGENVDSO arch/mips/vdso/vdso-image.c\narch/mips/vdso/genvdso: 'arch/mips/vdso/vdso.so.dbg' contains relocation sections\n.../arch/mips/vdso/Makefile:84: recipe for target 'arch/mips/vdso/vdso-image.c' failed\n\nSigned-off-by: Robert Schiele <rschiele@gmail.com>\nSigned-off-by: Alexander Sverdlin <alexander.sverdlin@nokia.com>\nCc: Ralf Baechle <ralf@linux-mips.org>\nCc: \"Maciej W. Rozycki\" <macro@imgtec.com>\nCc: Alexander Sverdlin <alexander.sverdlin@nokia.com>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/15127/\nSigned-off-by: James Hogan <james.hogan@imgtec.com>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/7b26b5204bbe9182fd70801b866168a07837acdd"},{"sha":"aafea8d4763b22b6ec5b7ab2e3ef3747d694de9c","author":{"name":"James Hogan","email":"547fa85bb3888a0222eed8ec39e36708605c6d53@imgtec.com"},"message":"MIPS: Fix printk continuations in cpu-bugs64.c\n\n64-bit pre-r6 kernels output the following broken printk continuation\nlines during boot:\n\nChecking for the multiply/shift bug...\nno.\nChecking for the daddiu bug...\nno.\nChecking for the daddi bug...\nno.\n\nFix the printk continuations in cpu-bugs64.c to use pr_cont to restore\nthe correct output:\n\nChecking for the multiply/shift bug... no.\nChecking for the daddiu bug... no.\nChecking for the daddi bug... no.\n\nSigned-off-by: James Hogan <james.hogan@imgtec.com>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/14916/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/aafea8d4763b22b6ec5b7ab2e3ef3747d694de9c"},{"sha":"92965d36ee4314764796d3ab0a03e23843bb32a4","author":{"name":"Matt Redfearn","email":"ad5f48d7adcc76c7bd25c44a65841f2a4476216d@imgtec.com"},"message":"MIPS: sync-r4k: Fix KERN_CONT fallout\n\nSince commit 4bcc595ccd80 (\"printk: reinstate KERN_CONT for printing\ncontinuation lines\") the output of counter synchornisation has been\nsplit across lines:\n[ 0.665181] Synchronize counters for CPU 1:\n[ 0.678578] done.\n\nFix this by using pr_cont, and replace printk with pr_info.\n\nSigned-off-by: Matt Redfearn <matt.redfearn@imgtec.com>\nCc: Ralf Baechle <ralf@linux-mips.org>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/15195/\nSigned-off-by: James Hogan <james.hogan@imgtec.com>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/92965d36ee4314764796d3ab0a03e23843bb32a4"},{"sha":"e1a24790e19650370cd682b757de78f0b25d3af8","author":{"name":"Marcin Nowakowski","email":"119fb589fa7bd788622b56427a92c412eccb48ae@imgtec.com"},"message":"MIPS: kexec: remove SMP_DUMP\n\nSMP_DUMP has been added as a new IPI signal when kexec support was added\nfor Cavium Octeon CPUs ('commit 7aa1c8f47e7e (\"MIPS: kdump: Add support\")'.\nHowever, the new signal doesn't appear to ever have a proper handler\nadded (octeon_message_functions[] array has an empty handler for it),\nand generic IPI handlers now trigger a BUG() on unhandled signal.\n\nAs the method is unused remove it completely and replace its only\ninvocation with a smp_call_function().\n\n[ralf@linux-mips.org: Renumber SMP_ASK_C0COUNT to avoid numbering gaps.]\n\nSigned-off-by: Marcin Nowakowski <marcin.nowakowski@imgtec.com>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/14630/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/e1a24790e19650370cd682b757de78f0b25d3af8"},{"sha":"186483f664545def0d48a91a23efc387b16f8736","author":{"name":"Marcin Nowakowski","email":"119fb589fa7bd788622b56427a92c412eccb48ae@imgtec.com"},"message":"MIPS: Move register dump routines out of ptrace code\n\nCurrent register dump methods for MIPS are implemented inside ptrace\nmethods, but there will be other uses in the kernel for them, so keep\nthem separately in process.c and use those definitions for ptrace\ninstead.\n\nSigned-off-by: Marcin Nowakowski <marcin.nowakowski@imgtec.com>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/14587/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/186483f664545def0d48a91a23efc387b16f8736"},{"sha":"1f75ba89187ff04e3b420929899e7352a696953e","author":{"name":"Marcin Nowakowski","email":"119fb589fa7bd788622b56427a92c412eccb48ae@imgtec.com"},"message":"MIPS: elfcore: add correct copy_regs implementations\n\nMIPS does not currently define ELF_CORE_COPY_REGS macros and as a result\nthe generic implementation is used. The generic version attempts to do\ndirectly map (struct pt_regs) into (elf_gregset_t), which isn't correct\nfor MIPS platforms and also triggers a BUG() at runtime in\ninclude/linux/elfcore.h:16 (BUG_ON(sizeof(*elfregs) != sizeof(*regs)))\n\n[ralf@linux-mips.org: Add semicolons to the macro definitions as I do not\napply https://patchwork.linux-mips.org/patch/14588/ for now.]\n\nSigned-off-by: Marcin Nowakowski <marcin.nowakowski@imgtec.com>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/14586/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/1f75ba89187ff04e3b420929899e7352a696953e"},{"sha":"7dda2214dcd0cc58fb79b88155f352c91742dd97","author":{"name":"Marcin Nowakowski","email":"119fb589fa7bd788622b56427a92c412eccb48ae@imgtec.com"},"message":"MIPS: Do not request resources for crashkernel if one isn't defined\n\nWhen KEXEC is enabled but crashkernel details are not passed through the\nkernel commandline unnecessary resources are requested (start==end==0)\n\nSigned-off-by: Marcin Nowakowski <marcin.nowakowski@imgtec.com>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/14607/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/7dda2214dcd0cc58fb79b88155f352c91742dd97"},{"sha":"26d1e20a07f9ba5fc5797e3661bafe2d63111cde","author":{"name":"Marcin Nowakowski","email":"119fb589fa7bd788622b56427a92c412eccb48ae@imgtec.com"},"message":"MIPS: fix mem=X@Y commandline processing\n\nWhen a memory offset is specified through the commandline, add the\nmemory in range PHYS_OFFSET:Y as reserved memory area.\nOtherwise the bootmem allocator is initialised with low page equal to\nmin_low_pfn = PHYS_OFFSET, and in free_all_bootmem will process pages\nstarting from min_low_pfn instead of PFN(Y).\n\nSigned-off-by: Marcin Nowakowski <marcin.nowakowski@imgtec.com>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/14613/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/26d1e20a07f9ba5fc5797e3661bafe2d63111cde"},{"sha":"7b0131c2a118a07c98ce446fcf9f8d21574b31e2","author":{"name":"Marcin Nowakowski","email":"119fb589fa7bd788622b56427a92c412eccb48ae@imgtec.com"},"message":"MIPS: kexec: Do not reserve invalid crashkernel memory on boot\n\nDo not reserve memory for the crashkernel if the commandline argument\npoints to a wrong location. This can happen if the location is specified\nwrong or if the same commandline is reused when starting the crashkernel\n- in the latter case the reserved memory would point to the location\nfrom which the crashkernel is executing.\n\nSigned-off-by: Marcin Nowakowski <marcin.nowakowski@imgtec.com>\nCc: linux-mips@linux-mips.org\nPatchwork: https://patchwork.linux-mips.org/patch/14612/\nSigned-off-by: Ralf Baechle <ralf@linux-mips.org>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/7b0131c2a118a07c98ce446fcf9f8d21574b31e2"},{"sha":"6e94f41e16c1559511e36b23da30fa0aada9d095","author":{"name":"Marcin Nowakowski","email":"119fb589fa7bd788622b56427a92c412eccb48ae@mips.com"},"message":"MIPS: Fix incorrect mem=X@Y handling\n\nCommit 73fbc1eba7ff (\"MIPS: fix mem=X@Y commandline processing\") added a\nfix to ensure that the memory range between PHYS_OFFSET and low memory\naddress specified by mem= cmdline argument is not later processed by\nfree_all_bootmem.  This change was incorrect for systems where the\ncommandline specifies more than 1 mem argument, as it will cause all\nmemory between PHYS_OFFSET and each of the memory offsets to be marked\nas reserved, which results in parts of the RAM marked as reserved\n(Creator CI20's u-boot has a default commandline argument 'mem=256M@0x0\nmem=768M@0x30000000').\n\nChange the behaviour to ensure that only the range between PHYS_OFFSET\nand the lowest start address of the memories is marked as protected.\n\nThis change also ensures that the range is marked protected even if it's\nonly defined through the devicetree and not only via commandline\narguments.\n\nReported-by: Mathieu Malaterre <mathieu.malaterre@gmail.com>\nSigned-off-by: Marcin Nowakowski <marcin.nowakowski@mips.com>\nFixes: 73fbc1eba7ff (\"MIPS: fix mem=X@Y commandline processing\")\nCc: Ralf Baechle <ralf@linux-mips.org>\nCc: linux-mips@linux-mips.org\nCc: <stable@vger.kernel.org> # v4.11+\nTested-by: Mathieu Malaterre <malat@debian.org>\nPatchwork: https://patchwork.linux-mips.org/patch/18562/\nSigned-off-by: James Hogan <jhogan@kernel.org>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/6e94f41e16c1559511e36b23da30fa0aada9d095"},{"sha":"0d5079e6271dbeceebe3e2298600649248448a93","author":{"name":"Aneesh Kumar K.V","email":"f511f818e8a0748edef6b9ee378967da9ed0c78f@linux.vnet.ibm.com"},"message":"mm/autonuma: let architecture override how the write bit should be stashed in a protnone pte.\n\nPatch series \"Numabalancing preserve write fix\", v2.\n\nThis patch series address an issue w.r.t THP migration and autonuma\npreserve write feature.  migrate_misplaced_transhuge_page() cannot deal\nwith concurrent modification of the page.  It does a page copy without\nfollowing the migration pte sequence.  IIUC, this was done to keep the\nmigration simpler and at the time of implemenation we didn't had THP\npage cache which would have required a more elaborate migration scheme.\nThat means thp autonuma migration expect the protnone with saved write\nto be done such that both kernel and user cannot update the page\ncontent.  This patch series enables archs like ppc64 to do that.  We are\ngood with the hash translation mode with the current code, because we\nnever create a hardware page table entry for a protnone pte.\n\nThis patch (of 2):\n\nAutonuma preserves the write permission across numa fault to avoid\ntaking a writefault after a numa fault (Commit: b191f9b106ea \" mm: numa:\npreserve PTE write permissions across a NUMA hinting fault\").\nArchitecture can implement protnone in different ways and some may\nchoose to implement that by clearing Read/ Write/Exec bit of pte.\nSetting the write bit on such pte can result in wrong behaviour.  Fix\nthis up by allowing arch to override how to save the write bit on a\nprotnone pte.\n\n[aneesh.kumar@linux.vnet.ibm.com: don't mark pte saved write in case of dirty_accountable]\n  Link: http://lkml.kernel.org/r/1487942884-16517-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com\n[aneesh.kumar@linux.vnet.ibm.com: v3]\n  Link: http://lkml.kernel.org/r/1487498625-10891-2-git-send-email-aneesh.kumar@linux.vnet.ibm.com\nLink: http://lkml.kernel.org/r/1487050314-3892-2-git-send-email-aneesh.kumar@linux.vnet.ibm.com\nSigned-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>\nAcked-by: Michael Neuling <mikey@neuling.org>\nCc: Rik van Riel <riel@surriel.com>\nCc: Mel Gorman <mgorman@techsingularity.net>\nCc: Paul Mackerras <paulus@samba.org>\nCc: Benjamin Herrenschmidt <benh@kernel.crashing.org>\nCc: Michael Ellerman <michaele@au1.ibm.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/0d5079e6271dbeceebe3e2298600649248448a93"},{"sha":"cbf4d32575ec147228fcb1f0294b8502fe0db698","author":{"name":"Aneesh Kumar K.V","email":"f511f818e8a0748edef6b9ee378967da9ed0c78f@linux.vnet.ibm.com"},"message":"mm/ksm: handle protnone saved writes when making page write protect\n\nWithout this KSM will consider the page write protected, but a numa\nfault can later mark the page writable.  This can result in memory\ncorruption.\n\nLink: http://lkml.kernel.org/r/1487498625-10891-3-git-send-email-aneesh.kumar@linux.vnet.ibm.com\nSigned-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>\nSigned-off-by: Andrew Morton <akpm@linux-foundation.org>\nSigned-off-by: Linus Torvalds <torvalds@linux-foundation.org>\nSigned-off-by: Huacai Chen <chenhc@lemote.com>","distinct":true,"url":"https://api.github.com/repos/loongson-community/linux-stable/commits/cbf4d32575ec147228fcb1f0294b8502fe0db698"}]}
{"actor":{"display_login":"heiher"}}